CtrlK
BlogDocsLog inGet started
Tessl Logo

industry-news-insight

Generate a concise Chinese WeChat-ready Markdown article from an industry name by searching current news from the last month, verifying evidence across production, demand, inputs, ecosystem, policy, financing, and technology signals, and writing first-person neutral third-party industry insight without visible author identity or AI traces. Use when the user asks for 行业新闻追踪, 行业洞察, 近一个月行业分析, 公众号短文, industry trend notes, or a source-backed short article saved to the current project's markdown directory.

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

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 well-crafted, highly actionable single-file skill: the workflow is clearly sequenced with an explicit evidence-validation gate and retry loop, and the writing guidance is unusually concrete (search terms, angles, length budget, file naming, article template). The two soft spots are mild redundancy between the Overview and later style rules, and a body slightly longer than the minimal case for a no-bundle skill.

Suggestions

Trim the tone restatement in the Overview ('not a formal report, pitch, consultant bio, or AI-generated summary') since Workflow step 5 and the Quality Bar already enforce these rules — keeping the Overview to a single purpose statement would earn top conciseness marks.

If the skill grows further, move the forbidden-phrase and article-shape exemplars into a references/ file (e.g. references/article-template.md) so SKILL.md stays a lean overview, improving progressive disclosure headroom.

Sharpen the English trigger terms in the description (e.g. replace 'industry trend notes' with something like 'WeChat industry news digest (行业洞察)') to reduce overlap with generic research/writing skills.

DimensionReasoningScore

Conciseness

The body is largely lean — search-term lists, angle lists, character budgets, and forbidden-phrase examples all earn their tokens — but the Overview ('not a formal report, pitch, consultant bio, or AI-generated summary') restates tone rules that Workflow step 5 and the Quality Bar repeat ('remove bureaucratic framing, consultant disclaimers, and AI-style transitions'). Minor instances of over-explanation that could be trimmed place it at anchor 4, not the every-token-earns-its-place anchor 5.

4 / 5

Actionability

For an instruction-only skill the guidance is fully executable: concrete search terms (新闻, 政策, 投融资, price, capacity), enumerated evidence angles, a 900-1500 character budget, the exact save path pattern 'markdown/<YYYYMMDD>-<industry-slug>-industry-news-insight.md', and a complete copy-paste-ready article template with section-by-section content guidance. It is not a 4 because there are no minor gaps in the common-case path.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with an explicit validation checkpoint ('Do not write if the last-month evidence is too thin, stale, promotional, or one-sided. Tell the user what is missing') and a feedback loop ('Add supplemental searches when a key causal link depends on missing evidence'). The validate-then-write gating matches the anchor-5 exemplar, so not a 4.

5 / 5

Progressive Disclosure

No bundle files exist and the skill is a single well-sectioned file (Overview / Workflow / Article Shape / Quality Bar) with all content appropriately inline for a writing task. Good structure with no buried references, but at ~85 lines it exceeds the under-50-line simple-skill case that would justify a 5 on organization alone — anchor 4, not 5, and not 3 since nothing that belongs in a separate file is inlined.

4 / 5

Total

18

/

20

Passed

Description

96%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 states what the skill does with concrete, enumerated actions and gives an explicit 'Use when' clause with natural bilingual trigger phrases. The only weakness is that its English trigger terms are slightly generic, creating minor overlap risk with general research/writing skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — 'searching current news from the last month, verifying evidence across production, demand, inputs, ecosystem, policy, financing, and technology signals', writing in a defined first-person style, and saving to the markdown directory — with comprehensive coverage of what the skill does. It is not a 4 because there are no minor gaps: search, multi-dimension verification, writing constraints, and output location are all explicitly named.

5 / 5

Completeness

It explicitly answers both 'what' (generate a concise Chinese WeChat-ready Markdown article by searching, verifying, and writing in a defined voice) and 'when' via a concrete 'Use when the user asks for...' clause listing real trigger phrases. This matches the anchor-5 exemplar pattern exactly, so not a 4.

5 / 5

Trigger Term Quality

Natural trigger phrases in both languages — '行业新闻追踪, 行业洞察, 近一个月行业分析, 公众号短文, industry trend notes, or a source-backed short article' — cover synonyms a real user of this skill would say, including the platform-specific 公众号短文. Coverage is comprehensive rather than leaving only 'a few natural terms missing', so not a 4.

5 / 5

Distinctiveness Conflict Risk

The Chinese triggers (行业洞察, 公众号短文) carve a clear niche with minimal conflict risk, but the English triggers 'industry trend notes' and 'source-backed short article' are generic and could overlap with general research or writing skills. Minor overlap risk places it at anchor 4 rather than the fully distinct anchor 5.

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.