CtrlK
BlogDocsLog inGet started
Tessl Logo

world-bug-opportunity-finder

Search current hot social or industry news, identify visible "world bugs" such as incentive failures, regulatory gaps, information asymmetry, safety risks, and unreasonable value-chain behavior, then propose root-cause fixes and business opportunities in a sourced, diagram-rich Chinese Markdown report saved under the current project's markdown directory. Use when the user gives an industry name and asks to find bugs/opportunities from industry news, or gives no industry and wants hot social-news bug analysis.

72

Quality

87%

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.

A well-structured, highly actionable instruction skill with clear sequencing and decision gates. The main improvement area is conciseness — trimming overlap between the workflow and the report template, and possibly externalizing long catalogs.

Suggestions

Reduce overlap between Workflow step 5 (layered fixes) and the Report Structure fix table so each is stated once.

Consider externalizing the long Chinese/English search-term catalogs and the 13-pattern bug taxonomy into a references/ file to shorten SKILL.md and improve progressive_disclosure.

Add an explicit verify-before-save checkpoint (e.g., confirm all cited sources resolve and visuals render) in the workflow to strengthen feedback-loop clarity.

DimensionReasoningScore

Conciseness

Mostly efficient domain-specific guidance (bug patterns, layered fix timeframes, search-term lists) rather than generic concept explanation, but the workflow's step 5 and the Report Structure table overlap somewhat and a few long enumerated lists could be tightened.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete search-term sets, a 13-item bug-pattern taxonomy, layered fix timeframes, a copy-paste report template with required Mermaid/SVG/table visuals, and an exact filename format (markdown/<YYYYMMDD>-<scope-slug>-world-bug-opportunity.md).

5 / 5

Workflow Clarity

Six clearly numbered steps with explicit decision gates ("if browsing or network access is unavailable, say the report cannot be responsibly produced"; "If no candidate has enough evidence, report that the evidence is too weak"), but these are decision gates rather than full validate-fix-retry feedback loops.

4 / 5

Progressive Disclosure

Single self-contained file with well-organized sections (Overview, Inputs And Defaults, Workflow, Report Structure, Quality Bar) and no nested references; at ~130 lines some content (the report template, search-term catalogs) could optionally be split into reference files, but inline placement is reasonable for this skill type.

4 / 5

Total

17

/

20

Passed

Description

92%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: third-person voice, concrete actions, explicit what-and-when triggers, and a distinct niche. The only minor gap is trigger-term synonym coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — "Search current hot social or industry news", "identify visible world bugs such as incentive failures, regulatory gaps...", "propose root-cause fixes and business opportunities", and "saved under the current project's markdown directory" — with comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (search, identify world bugs, propose fixes and opportunities, produce a sourced diagram-rich Chinese Markdown report) and when ("Use when the user gives an industry name and asks to find bugs/opportunities... or gives no industry and wants hot social-news bug analysis") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ("gives an industry name and asks to find bugs/opportunities from industry news", "hot social-news bug analysis") with good coverage, though a few common phrasings like synonyms or casual variants are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (news-driven world-bug/opportunity analysis with a specific output artifact) with distinct triggers and minimal overlap risk against generic analysis or writing 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.