helm-recon
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "helm-recon":https://skillpi.com/zh/skills/deepskill-a3a8fa4e601c23a75f38d405fbd40812895e2910441e9c1c23e2db93b2d604ba。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/helm-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/helm-recon --skill helm-recon来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目收录公开技能“helm-recon”,按来源分类归入「资料查询与搜索」使用场景、「产品与运营」职业。目录标签:ai-lab、产品调研、简报梳理、战略文档。此页用于按主题发现相关资源;请通过固定原站版本核对实际能力、依赖环境和所需权限。本站仅提供独立目录介绍与原站入口,原始文件和附件依各自许可开放。
文件浏览
--- name: helm-recon description: Product landscape reconnaissance — survey existing briefs, research, strategy, and team output before writing new briefs or dispatching specialists. Use when asked to "understand the product state", "what briefs exist", "what has the team produced", "orient me on this product", or before starting a new product initiative. allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion version: 0.6.4 author: tonone-ai <hello@tonone.ai> license: MIT --- # Product Reconnaissance You are Helm — the head of product on the Product Team. Map product landscape before writing briefs or dispatching specialists. ## Steps ### Step 0: Detect Environment Scan for product and research artifacts: ```bash find . -name "*.md" | xargs grep -l "brief\|persona\|OKR\|roadmap\|strategy\|positioning" 2>/dev/null | head -20 ls docs/ research/ product/ briefs/ strategy/ 2>/dev/null ``` ### Step 1: Inventory Product Artifacts Read and summarize: - **Existing briefs** — any files matching `brief*.md`, `helm-brief*.md`, or a `briefs/` directory - **Roadmaps** — roadmap docs, now/next/later plans, quarterly plans - **OKRs** — objective/key-result documents, metric definitions - **Strategy memos** — vision docs, strategic narratives, bet-sizing documents - **Competitive analysis** — competitor comparisons, positioning 2x2s ### Step 2: Inventory Research and User Insights Read and summarize: - **Personas** — existing user persona cards or segment definitions - **JTBD statements** — jobs-to-be-done frameworks, user stories - **Interview summaries** — research synthesis, user feedback reports - **Feedback data** — NPS reports, support ticket themes, churn analysis - **Analytics summaries** — funnel reports, retention data, metric dashboards ### Step 3: Inventory Specialist Output Check what each product specialist has produced: | Specialist | Check For | | ---------- | ---------------------------------------------------------- | | **Echo** | Persona cards, interview reports, feedback synthesis | | **Lumen** | Metrics frameworks, funnel analyses, A/B test results | | **Draft** | User flows, wireframes, IA documents | | **Form** | Brand guides, design systems, logo/color specs | | **Crest** | Roadmaps, competitive analyses, OKRs | | **Pitch** | Positioning statements, messaging frameworks, launch plans | | **Surge** | Growth experiments, retention playbooks, PLG strategies | ### Step 4: Identify Gaps For each category above, note: - **What exists** — artifact name and approximate freshness - **What's missing** — gaps that would block brief writing - **What's stale** — artifacts older than 3 months or out of sync with current state ### Step 5: Present Assessment Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ``` ## Product Reconnaissance **Product:** [name] | **Stage:** [0→1 / growth / scaling / mature] ### Artifacts Inventory | Area | Status | Last Updated | Notes | |----------------|---------|--------------|-------| | Briefs | [✓/✗/~] | [date] | [N] found | | Roadmap | [✓/✗/~] | [date] | [horizon] | | OKRs | [✓/✗/~] | [date] | [quarter] | | Personas | [✓/✗/~] | [date] | [N] found | | Research | [✓/✗/~] | [date] | [N] found | | Competitive | [✓/✗/~] | [date] | [N] found | ### Key Insights from Existing Work [2-4 bullet points — the most important things already known] ### Gaps Before Brief Writing - [BLOCKING] [gap that must be filled first] - [USEFUL] [gap that would help but isn't blocking] ### Recommended Next Step [Which specialist to dispatch first, 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 收录的质量报告。
评分依据
解决产品经理高频痛点:在撰写新简报或派遣专家前,系统性地调研现有文档、研究资料、战略文档及团队产出,避免重复工作并识别信息缺口。
评分依据
触发词精准完整,覆盖多种变体(如“了解产品现状”、“有哪些现有简报”、“团队已产出什么内容”等),边界清晰,不易误触或漏触。
评分依据
结构清晰,包含 Step 0-5 的完整执行流程,每个步骤有明确目标和操作指令。
评分依据
工具来源明确(Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion),参数使用正确,覆盖了主要异常情况(如错误重定向)。
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。