CtrlK
BlogDocsLog inGet started
Tessl Logo

product-multi-role-analysis

输入某个产品的文档、URL 或简要描述,自动抓取关键信息,分别扮演「用户、投资人、产品经理、市场运营、品牌运营、友商、合作伙伴」7 个角色对该产品进行深度分析,中间结果分角色保存,最终整合为一篇图文并茂(SVG/Mermaid/ASCII)的综合分析报告,结论明确、有权威数据支撑、逻辑清晰、小白可读,并附有结论边界、前提假设及假设变动时的结论调整说明。 触发条件:用户提到"产品分析"、"多角色分析"、"7个角色"、"投资人视角"、"用户视角"、"产品竞争分析"、"全面分析这个产品"、"帮我分析一下 XX 产品"、"从多个角度看这个产品"、"product analysis"、"multi-role analysis",或提供产品文档/链接并希望获得深度产品分析报告时,必须使用本 skill。即使用户只说"帮我全面分析一下这个产品",也应立即使用本 skill。

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable multi-phase workflow with clean progressive disclosure to three real reference files. Main weaknesses are minor redundancy in the file layout and the absence of explicit inter-phase validation and feedback loops.

Suggestions

Add an explicit feedback loop after the 质量检查清单 (e.g., 'if any checklist item fails, return to the relevant phase and re-run it before presenting files').

Remove the duplicated file-naming block — keep the Phase 4 tree as the single source of truth and have Phase 1 reference it.

Insert a brief validation checkpoint between phases (e.g., confirm 00_raw_intel.md has real numbers before starting Phase 1).

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanations of SVG/Mermaid/TAM-SAM-SOM), but the file naming appears twice (Phase 1 list and Phase 4 tree) and the quality checklist reiterates phase requirements, giving minor trim opportunities.

4 / 5

Actionability

Provides concrete, copy-paste-ready guidance — exact search queries ('[产品名] review site:g2.com OR site:producthunt.com'), exact filenames, and KPA/boundary templates — but the core per-role analysis guidance is delegated to references rather than specified inline, leaving minor gaps.

4 / 5

Workflow Clarity

A clear Phase 0→4 sequence with a terminal 质量检查清单 providing verification (so the batch-operation cap does not apply), but there are no inter-phase validation checkpoints and no explicit validate→fix→retry feedback loop when a checklist item fails.

4 / 5

Progressive Disclosure

The body is a clear overview with three one-level-deep references (role-templates.md, report-structure.md, chart-guide.md), all real files, well-signaled via a dedicated 参考文件索引 section plus inline mentions, with content appropriately split.

5 / 5

Total

17

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states capabilities and provides rich, bilingual trigger phrases in third person. It is slightly held back by quality-adjective padding and a few overly broad trigger terms that could overlap a generic analysis skill.

Suggestions

Trim vague quality claims ('结论明确、有权威数据支撑、逻辑清晰、小白可读') from the capability statement to keep only concrete actions.

Narrow the broadest triggers ('帮我分析一下 XX 产品', '全面分析这个产品') by tying them to the multi-role framing to reduce overlap with a generic product-analysis skill.

DimensionReasoningScore

Specificity

Lists several concrete actions (抓取关键信息, 分角色深度分析, 中间结果分角色保存, 整合图文报告, 附结论边界/前提假设/调整说明) but pads them with vague quality adjectives like '结论明确、有权威数据支撑、逻辑清晰、小白可读' that are not concrete capabilities.

4 / 5

Completeness

Explicitly answers both 'what' (input→fetch→7-role analysis→save→integrate report with charts, boundaries, assumptions) and 'when' via a dedicated 触发条件 clause with concrete trigger phrases and a '必须使用本 skill' directive, in third person.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural user phrases including synonyms and both languages ('产品分析', '多角色分析', '7个角色', '帮我分析一下 XX 产品', 'product analysis', 'multi-role analysis'), matching the anchor for comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

The 7-role framing and terms like '投资人视角' are distinctive, but broad triggers such as '帮我分析一下 XX 产品' and '全面分析这个产品' carry minor overlap risk with a generic product-analysis skill.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
digoal/blog
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.