CtrlK
BlogDocsLog inGet started
Tessl Logo

bug-hunter

根据用户给出的行业名称(或默认使用热点社会新闻),抓取最新新闻热点,用"找世界bug"的视角——找出那些打眼一看就不合理的地方——深度分析根因、利益链条、监管盲区,并给出多维度解决思路,输出图文并茂(含SVG/Mermaid/ASCII图形)的Markdown文件,保存到项目markdown/目录。 触发条件:用户提到"找bug"、"社会bug"、"不合理现象"、"帮我分析这个行业的问题"、"帮我找新闻里的bug"、"找热点新闻的漏洞"、"有什么不合理的地方"、"帮我分析为什么会这样"、"bug猎手"等。即使用户只说"帮我找找最近有什么奇怪的新闻"或"这个行业有哪些不合理",也应使用本 skill。

68

Quality

83%

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

70%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 delivers a clear, well-sequenced workflow with strong exception handling and concrete output specifications, and the actionability is high for an instruction-only skill. Its weaknesses are duplication of the workflow across the TL;DR decision tree and checkpoint table, and the absence of any bundle files despite ~245 lines whose template and SVG spec would fit naturally in reference files.

Suggestions

Move the full article structure template and the SVG four-quadrant matrix spec into a references/ file (e.g. references/output-template.md), keeping only a short summary inline, to improve progressive disclosure and cut SKILL.md length.

Remove the duplicated workflow restatement in the 决策树速查 and 检查点设计 sections — keep one (the checkpoint table) since the 异常处理 branches are already stated inline at Step 1 and Step 1.5.

Add one worked mini-example (a filled-in Bug analysis with a sample Mermaid 利益链条图 showing the actual node/edge syntax) to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is mostly operational instructions rather than padding, but it can be tightened: the "核心理念" quote, parts of "注意事项" restating earlier rules, and the "决策树速查(TL;DR)" plus "检查点设计" table both re-state the Step 1–4 flow and the inline "⚠️ 异常处理" branches. Not 2 because nothing explains concepts Claude already knows; not 4 because the duplication is noticeable rather than minor.

3 / 5

Actionability

Concrete, largely copy-paste-ready guidance: exact search keyword strings, an SVG spec (viewBox "0 0 800 600", quadrant hex colors), an output path pattern with a pinyin example, and a complete article template. Not 5 because there is no worked example of a finished analysis and the required Mermaid 利益链条图 never specifies the diagram type or node/edge structure.

4 / 5

Workflow Clarity

Steps are clearly sequenced (Step 1 → 1.5 → 2 → 3 → 4) with explicit error-recovery loops ("扩大关键词…最多重试2轮", fallback to 1 bug plus a cross-industry analogy, 5-minute user-response timeout with a documented default) and a dedicated checkpoint table. Feedback loops and checkpoints are explicitly designed in, matching the anchor-5 example.

5 / 5

Progressive Disclosure

The skill is a single ~245-line file with no references/, scripts/, or assets/ bundle; well-sectioned, but content that belongs in reference files — the full article output template and the SVG matrix spec — is inlined in SKILL.md. Structure exists and navigation is easy (better than anchor 2), but the inlined template content keeps it below anchor 4's 'most content appropriately placed'.

3 / 5

Total

15

/

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 covers the full workflow concretely, includes a rich set of natural Chinese trigger phrases, and explicitly states when to use the skill including implicit-trigger cases. The only weakness is one generic trigger phrase ("帮我分析为什么会这样") that risks overlap with debugging-type requests.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions spanning the entire workflow: "抓取最新新闻热点", "深度分析根因、利益链条、监管盲区", "给出多维度解决思路", and "输出图文并茂(含SVG/Mermaid/ASCII图形)的Markdown文件,保存到项目markdown/目录" — including the output format and destination. Comprehensive coverage, so anchor 4's 'minor gaps' does not apply.

5 / 5

Completeness

Explicitly answers both questions: 'what' (fetch news → analyze root causes/interest chains/regulatory blind spots → propose solutions → output illustrated markdown file) and 'when' via a dedicated "触发条件:用户提到…" clause with concrete trigger phrases. Matches the anchor-5 good example pattern exactly.

5 / 5

Trigger Term Quality

Extensive natural phrases a user would actually say: "找bug", "社会bug", "不合理现象", "有什么不合理的地方", "帮我分析为什么会这样", plus the implicit-trigger cases "帮我找找最近有什么奇怪的新闻" and "这个行业有哪些不合理". Coverage includes synonyms and shorthand variants, matching the comprehensive anchor.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers ("bug猎手", "社会bug", "找热点新闻的漏洞") that are unlikely to collide with other skills. However "帮我分析为什么会这样" is generic enough that it could also fire for code-debugging requests, giving minor overlap risk — the anchor-4 'mostly distinct; minor overlap risk' fit is better than 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.