CtrlK
BlogDocsLog inGet started
Tessl Logo

bug-hunter

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

69

Quality

85%

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.

A well-structured, actionable multi-step workflow with strong sequencing and validation checkpoints, undermined slightly by redundancy between the steps and the TL;DR/checkpoint sections, and by a monolithic inline structure that could benefit from reference files.

Suggestions

Collapse or remove the 决策树速查 and 检查点设计 sections where they duplicate the numbered steps, keeping them only if they add genuinely new information.

Move the full article structure template and SVG quadrant spec into a reference file (e.g. references/template.md) and link to it from SKILL.md to improve progressive disclosure.

Replace open-ended placeholder analysis sections with one concrete worked example so the expected output depth is unambiguous.

DimensionReasoningScore

Conciseness

The body is mostly actionable and does not explain concepts Claude already knows, but the 决策树速查 TL;DR and 检查点设计 table restate content already covered in the numbered steps, so it could be tightened.

3 / 5

Actionability

Provides concrete search strings, an exact output path, exact SVG viewBox/colors, and a full copy-paste markdown template, but the analysis sections themselves rely on placeholders and open-ended generation leaving minor gaps.

4 / 5

Workflow Clarity

A clearly sequenced Step 1→1.5→2→3→4 flow with explicit feedback loops (异常处理 keyword-expansion retries, user confirmation before deep analysis) and a 检查点设计 checklist for error recovery.

5 / 5

Progressive Disclosure

The file is well-sectioned but ~245 lines are entirely inlined with no bundle files; the large article template and SVG spec are content that could live in separate reference files, and there are no one-level-deep references to signal.

3 / 5

Total

15

/

20

Passed

Description

100%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 comprehensive, concrete, and trigger-rich, clearly stating both what the skill does and when to invoke it with natural user phrases. Voice is appropriately third-person/infinitive with no first- or second-person drift.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 抓取最新新闻热点, 深度分析根因/利益链条/监管盲区, 给出多维度解决思路, 输出含SVG/Mermaid/ASCII的Markdown — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (抓取新闻/深度分析/给解决思路/输出markdown) and 'when' via a dedicated 触发条件 clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers many natural phrases a user would actually say — 找bug, 社会bug, 不合理现象, 帮我分析这个行业的问题, 找热点新闻的漏洞, 帮我分析为什么会这样, bug猎手 — including synonyms and casual variants.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (社会bug猎手) with distinctive triggers (找bug, 社会bug, bug猎手) that are unlikely to fire for unrelated skills.

5 / 5

Total

20

/

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.