CtrlK
BlogDocsLog inGet started
Tessl Logo

industry-insight-writer

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

72

Quality

88%

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

82%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.

The body is a well-structured, actionable writing brief with concrete templates, quantitative thresholds, and a validation checklist. It stays lean and assumes competence; the main improvement area is tighter conciseness and slightly more explicit error-recovery guidance in the workflow.

Suggestions

Tighten the '好的开篇' and '好的洞察句式' example blocks to 1–2 lines each to reduce tokens further.

Add a brief error-recovery step in Step 1 (e.g., what to do if searches return <5 useful leads after the补充 round).

Consider moving the style-guide examples and 要避免的 list into a references/style-guide.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Lean, instructional body with templates, a specs table, and a checklist that assume Claude's competence; a few example sections could be trimmed, so it is efficient rather than maximally lean.

4 / 5

Actionability

Provides concrete, copy-ready guidance: search-query templates, output path pattern with filename example, structure template, word-count range, style do/don't pairs, and a self-check checklist covering common cases.

5 / 5

Workflow Clarity

Clear 4-step sequence (搜集→提炼→撰写→保存) with quantitative checkpoints (3–5 searches, 5条以上线索, 600–900字) and a self-check checklist as validation; minor gaps in explicit error-recovery feedback keep it below 5.

4 / 5

Progressive Disclosure

Well-organized sections with clear headers and no nested references; the skill is self-contained with no bundle files, so content is appropriately inline, though the style-guide/示例 material could be externalized for cleaner separation.

4 / 5

Total

17

/

20

Passed

Description

95%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.

The description is strong: it states a clear purpose, output format, and placement, and provides comprehensive, natural trigger phrases including a fallback case. Minor specificity gap (the list of concrete writing actions could be more enumerated) keeps it just short of a clean sweep.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete actions ('撰写…简短深度文章', '保存到…markdown/ 目录', '第一人称,中立有据', '不超过4屏') with minor coverage gaps; not a comprehensive 5-level list of distinct actions.

4 / 5

Completeness

Explicitly answers both what (write an industry-insight WeChat article saved as Markdown to markdown/) and when (触发条件 clause with concrete trigger phrases), matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases ('帮我写篇XX行业的文章', '行业观察', '行业跟踪', '行业洞察', '帮我写XX行业报告', 'XX行业近期发展') plus an explicit fallback case, covering synonyms users would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear niche (公众号行业洞察, 第三方中立顾问口吻, ≤4屏, 无AI痕迹) with distinct triggers and minimal overlap risk with other skills.

5 / 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.

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.