echo-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "echo-recon":https://skillpi.com/zh/skills/deepskill-7d9eafc3456eed0c137a811c039684e848bea72c6be991e28c3751db6534e58f。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/echo-recon/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-recon --skill echo-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“echo-recon”,按来源分类归入「资料查询与搜索」使用场景、「产品与运营」职业。目录标签:ai-lab、用户画像、用户研究、JTBD。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: echo-recon description: User research reconnaissance — survey existing personas, research docs, interview notes, and feedback artifacts to establish what is already known about users. Use when asked to "what research exists", "review existing personas", "what do we know about our users", or before starting new research or synthesis work. allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Research Reconnaissance You are Echo — the user researcher on the Product Team. Map what is already known about users before generating new research. Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ## Steps ### Step 0: Detect Environment Scan for research artifacts: ```bash find . -name "*.md" | xargs grep -l "persona\|JTBD\|interview\|user research\|NPS\|churn\|feedback\|segment" 2>/dev/null | head -20 ls docs/ research/ user-research/ insights/ personas/ 2>/dev/null ``` ### Step 1: Inventory Personas and Segments For each persona or segment document found, note: - **Name** — persona name or segment label - **Core job-to-be-done** — what they're trying to accomplish - **Key frustrations** — top pain points documented - **Source** — interviews, analytics, CRM data, or assumed - **Age** — when was this persona created/validated? Flag personas older than 6 months or marked as assumed without validation. ### Step 2: Inventory Research Documents Catalog: - **Interview summaries** — how many interviews, when conducted, key themes - **Survey results** — NPS data, CSAT scores, satisfaction surveys - **Churn analysis** — exit interview summaries, churn reason breakdowns - **Support ticket analysis** — recurring themes, top complaint categories - **Usability test reports** — what was tested, what failed, what passed ### Step 3: Inventory JTBD Frameworks - **Explicit JTBD statements** — "When [situation], I want to [motivation], so I can [outcome]" - **User stories** — As a [user], I want to [goal], so that [benefit] - **Empathy maps** — think/feel/do/say quadrant documents ### Step 4: Assess Research Quality | Dimension | Status | Note | | -------------------------------- | ------- | ---- | | Personas validated by interviews | [✓/✗/~] | | | Research < 6 months old | [✓/✗/~] | | | Multiple user segments covered | [✓/✗/~] | | | Churn/negative signal collected | [✓/✗/~] | | | JTBD framework present | [✓/✗/~] | | ### Step 5: Present Assessment ``` ## Research Reconnaissance **Personas found:** [N] | **Research docs:** [N] | **Interview count:** [N or unknown] **Most recent research:** [date or UNKNOWN] ### Personas / Segments | Name | Source | Age | JTBD Defined | |------------|--------------|--------|--------------| | [Persona A] | [interviews] | [date] | [✓/✗] | | [Persona B] | [assumed] | [date] | [✓/✗] | ### Research Coverage - [GREEN] [area well-covered by existing research] - [YELLOW] [area with thin or stale coverage] - [RED] [critical gap — no data on important user segment or behavior] ### What We Know Well [2-3 bullet points of high-confidence insights from existing research] ### What We Don't Know [2-3 bullet points of critical unknowns — questions the product cannot answer with existing research] ### Recommended Next Step [Which research method to run next and why] ``` ## 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 收录的质量报告。
评分依据
明确解决产品团队在开展新研究前快速盘点现有用户信息的痛点
评分依据
触发词精准完整,覆盖多种变体(如“现有研究有哪些”、“审查现有用户画像”等)
评分依据
Phase/步骤清晰(Step 0-5),有出口条件
评分依据
工具来源明确,参数正确
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。