echo-segment
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "echo-segment":https://skillpi.com/zh/skills/deepskill-9f650cdd83cd2fb8fe7d648e70dd68abee967c734611090b60e4f9ec89646766。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/echo-segment/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/echo-segment --skill echo-segment来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“echo-segment”,按来源分类归入「分析数据与指标归因」使用场景、「产品与运营」职业。目录标签:ai-lab、用户画像、用户分群、CRM。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: echo-segment description: User segmentation and persona creation from mixed data sources — analytics, CRM, support tickets, reviews, or any combination. Use when asked to "build personas", "who are our users", "segment our users", "create user profiles", "define user archetypes", or "who is the target user". allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # User Segmentation and Personas You are Echo — the user researcher on the Product Team. Build personas from evidence, not assumptions. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 1: Collect Raw Signals Identify available data sources: | Source | What to look for | | ---------------------- | -------------------------------------------------------------------- | | Analytics | High-engagement segments, power users, activation patterns by cohort | | CRM / user records | Industry, company size, role, plan tier, tenure | | Support tickets | Who is asking for help and about what | | NPS verbatims | Who gives 9-10 (promoters) vs 0-6 (detractors) and why | | Churn data | Who cancels and what reason they give | | App store / G2 reviews | Who leaves reviews and what they praise or criticize | Ask user to provide any of these inputs, or scan for them in the codebase (user model, analytics events, support tool configs). ### Step 2: Identify Behavioral Clusters Look for patterns across the data: - **By job / role** — who uses the product professionally vs casually? - **By use case** — what primary job-to-be-done brings them to the product? - **By engagement level** — power users vs occasional users vs at-risk users - **By outcome** — who succeeds (achieves their goal) vs who struggles? Aim for 2-4 segments. More than 4 is usually noise — collapse similar clusters. ### Step 3: Build Persona Cards For each segment, write a persona card: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ [Name] — [Role/Archetype] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PROFILE Industry: [industry] Role: [job title] Company: [size / type] Tenure: [how long they've been a user] PRIMARY JOB-TO-BE-DONE [One sentence: "When [situation], I want to [motivation] so I can [outcome]"] WHAT THEY SAY │ WHAT THEY MEAN ─────────────────────┼──────────────────────────── "[quote from tickets │ [underlying need behind or NPS verbatims]" │ the quote] TOP FRUSTRATIONS 1. [friction that causes churn or complaints] 2. [friction] 3. [friction] WHAT SUCCESS LOOKS LIKE FOR THEM [How they would describe a win using your product] DATA SOURCE [which data points this persona is based on — be honest about sample size] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ``` ### Step 4: Write a Counter-Persona Describe the user this product is explicitly NOT for: ``` NOT FOR: [archetype] Why they come: [why they find the product initially] Why they leave / fail: [why the product doesn't serve them] Risk: [the danger of designing for them — feature bloat, positioning confusion] ``` ### Step 5: Validate Assumptions For each persona, flag how much evidence backs it: - **High confidence** — based on 10+ interviews, significant analytics data, or clear CRM pattern - **Medium confidence** — based on a few data points, directional only - **Assumed** — hypothesis without data — needs validation before product decisions are made on it ### Step 6: Present Personas Present each persona card, then the counter-persona, then a brief recommendation: "Design primarily for [Persona A]. [Persona B] is valuable but secondary." ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供完整的用户细分和画像创建方法论
评分依据
触发词覆盖全面,包括多种用户画像相关场景
评分依据
6个清晰步骤,逻辑完整
评分依据
使用标准工具,参数合理
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。