CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

industry-insight-writer

以第三方中立研究顾问身份,围绕某个行业近1个月内的最新动态,撰写适合公众号发布的简短深度文章(不超过4屏手机阅读)。触发条件:用户输入行业名称并希望生成行业洞察文章,提到"帮我写篇XX行业的文章"、"分析一下XX行业最近的动态"、"以顾问角度写XX"、"行业观察"、"行业跟踪"、"行业洞察"、"帮我写XX行业报告"、"XX行业近期发展"等。即使用户只说"帮我写一篇关于XX行业的文章",只要意图是行业评析,也应使用本 skill。输出为 Markdown 文件,保存到当前项目 markdown/ 目录,适合手机端阅读,第一人称,中立有据,无AI生成痕迹。

73

Quality

92%

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

88%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 tight, high-actionability instruction skill: quantified specs, literal search templates, a structure template with an explicit flexibility note ("结构是骨架,不是枷锁"), style exemplars, and a pre-output checklist give Claude everything needed to execute. The only refinements are minor redundancy between the spec table and style sections, and the option to externalize style examples if the skill grows.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — no filler explaining what公众号 or search are, and every section adds skill-specific constraints (spec table, style do/don'ts). Minor trims exist: the 禁忌 row in the spec table overlaps with the 要避免的 list, and "第一人称" appears in both the role section and the spec table. Not quite the every-token-earns-its-place ideal of the top anchor.

4 / 5

Actionability

Fully concrete, executable guidance throughout: literal search-query templates ("{行业名称} 最新动态 {当前年月}"), counts (3~5次搜索, 5条以上线索, 600~900字, 标题不超过20字), a fill-in article structure template, an output path pattern with a worked filename example (xinnengyuan-insight-202506.md), and concrete good/bad style examples. This matches the instruction-only equivalent of copy-paste-ready guidance.

5 / 5

Workflow Clarity

Clear 4-step sequence with explicit feedback loops and checkpoints: "信息不足时,追加搜索补充证据,直到有5条以上有价值线索" (search retry loop), and the 质量自检清单 run "输出前" with concrete checks (字数在600~900之间, 有无AI味表达, 文件已保存). This matches the anchor for clear sequence + explicit validation + checklists. The workflow is file-writing, not destructive/batch, so the validation cap does not apply.

5 / 5

Progressive Disclosure

Well-organized single-file skill: clear section hierarchy (角色定位 → 执行流程 → 写作风格指南 → 质量自检清单) with no buried references and no content that clearly demands a separate file at ~130 lines. It exceeds the under-50-lines simple-skill exemption, and the style-guide examples could live in a references file if the skill grows, so this is good structure with minor organization headroom rather than the ideal.

4 / 5

Total

18

/

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: it clearly states the task, output format, and destination, and provides an unusually rich set of natural trigger phrases plus an intent-based catch-all rule. The only weaknesses are minor — the search/research step is absent from the what-description, and the catch-all broadens overlap slightly with general writing skills.

DimensionReasoningScore

Specificity

Multiple concrete actions and output specifics are stated — "撰写适合公众号发布的简短深度文章(不超过4屏手机阅读)" and "输出为 Markdown 文件,保存到当前项目 markdown/ 目录" — with style constraints (第一人称、中立有据、无AI生成痕迹). Minor gaps: the news-search process that precedes writing is not mentioned, keeping it just short of comprehensive coverage.

4 / 5

Completeness

Explicitly answers both: what ("以第三方中立研究顾问身份…撰写…简短深度文章", "输出为 Markdown 文件,保存到 markdown/ 目录") and when ("触发条件:用户输入行业名称并希望生成行业洞察文章", with concrete trigger phrases and the "即使只说…只要意图是行业评析,也应使用本 skill" rule). Both are concrete and explicit.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a Chinese user would actually say: "帮我写篇XX行业的文章", "分析一下XX行业最近的动态", "以顾问角度写XX", "行业观察", "行业跟踪", "行业洞察", "帮我写XX行业报告", "XX行业近期发展", plus a catch-all variant. Coverage of synonyms and phrasing variations is thorough.

5 / 5

Distinctiveness Conflict Risk

A clear niche (industry-insight articles for 公众号, last-1-month dynamics, consultant persona) with distinct triggers. The catch-all rule ("即使用户只说'帮我写一篇关于XX行业的文章'…也应使用本 skill") slightly widens overlap with generic article-writing skills, but the "只要意图是行业评析" condition bounds it — minor overlap risk only.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

digoal/blog

Path

skills/skills_for_claude_web/industry-insight-writer/SKILL.md

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.