CtrlK
BlogDocsLog inGet started
Tessl Logo

industry-deep-explainer

系统性'讲透'一个行业的深度分析技能。覆盖产业链分布、利润分布、代表企业、人货场、供需连接, 并推演不合理点、机会点、入局策略(产品/客群/商业模式/定价)、竞争对手与合作伙伴。触发场景: 讲透/分析XX行业、XX产业链、XX行业机会、如何进入XX行业、XX赛道分析、我想做XX怎么切入等。输出图文并茂的深度分析报告到当前项目 markdown/ 目录。

75

Quality

94%

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

92%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-engineered skill body: concrete search/output specs, a mandatory numeric self-consistency check with a worked example, and a validation-gated workflow. The only trimmable material is the list of well-known theory frameworks and a stray reference to a user memory.

DimensionReasoningScore

Conciseness

The body is largely lean — search templates, a worked CAGR check, and a checklist with no padding — but the 8-entry theory list (e.g., "迈克尔·波特《竞争战略》— 五力模型、价值链") explains frameworks Claude already knows, and the "见用户 [记忆: web 搜索验证财务事实]" line is leaky/unnecessary. These are minor trimmable spots, matching the anchor-4 'efficient; minor instances of over-explanation'.

4 / 5

Actionability

Fully executable guidance throughout: a literal 8-query search template code block, exact output path "markdown/{行业名}-行业深度分析.md" (with directory-creation rule), a length spec of 6000-12000 字, the concrete formula "首值 × (1 + r)^n = 末值" with a worked numeric example (970 × 1.38^5 = 5238 亿 vs 730), a 6-question entry-strategy checklist, and a pre-writing self-check list.

5 / 5

Workflow Clarity

A clearly numbered 5-step workflow with explicit validation and feedback loops: Step 2 mandates live search verification, the data-consistency check is labeled "硬性约束, 落地前必做" with "发现矛盾立即重查原始来源" (verify → fix → retry), and Step 5 is gated by a 10-item pre-output checklist.

5 / 5

Progressive Disclosure

SKILL.md stays an overview and pushes detail to four one-level-deep, real bundle files (framework.md, output-template.md, visualization-guide.md, data-sources.md — all present in references/), each linked at its point of use and summarized again in a "资源文件" section; nothing that belongs in a reference is inlined.

5 / 5

Total

19

/

20

Passed

Description

93%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: third-person, concrete about what it does, with an explicit and natural trigger list and a specified output location. The only weakness is that the generic "分析XX行业" trigger does not differentiate it from adjacent industry-analysis skills.

DimensionReasoningScore

Specificity

The description enumerates many concrete capabilities — "覆盖产业链分布、利润分布、代表企业、人货场、供需连接" and "推演不合理点、机会点、入局策略(产品/客群/商业模式/定价)、竞争对手与合作伙伴" — plus a concrete output artifact ("输出图文并茂的深度分析报告到当前项目 markdown/ 目录"), giving comprehensive, specific coverage with no vague filler.

5 / 5

Completeness

Both halves are explicit: 'what' is the systematic deep analysis chain ("系统性'讲透'一个行业的深度分析技能" plus the enumerated dimensions) and 'when' is a dedicated "触发场景:" clause listing concrete trigger phrases, matching the anchor-5 example structure.

5 / 5

Trigger Term Quality

The "触发场景" clause covers natural user phrasings with synonyms: "讲透/分析XX行业", "XX产业链", "XX行业机会", "如何进入XX行业", "XX赛道分析", "我想做XX怎么切入" — these mirror how a user would actually ask, spanning analysis and entry-strategy intents.

5 / 5

Distinctiveness Conflict Risk

The niche (industry analysis culminating in entry/入局 strategy) is distinct, but the broad trigger "分析XX行业" overlaps with closely related industry-analysis skills (the body itself lists industry-chain-analyst and industry-insight-writer as neighbors), so minor overlap risk remains.

4 / 5

Total

19

/

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.

Validation — 16 / 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.