CtrlK
BlogDocsLog inGet started
Tessl Logo

diagnosing-bugs

面向棘手缺陷和性能回退的诊断循环。适用于用户说 “diagnose” / “debug this”,或报告某些东西 broken、throwing、failing、slow 时。

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 content is a tightly disciplined debugging playbook with clear phased sequencing, explicit validation gates, and actionable concrete guidance. It is efficient with token use and properly offloads its one external artifact to a real, executable script.

DimensionReasoningScore

Conciseness

Efficient and assumes Claude's intelligence ("这就是这个 skill 的核心。其他所有内容都是机械步骤"), with minor emphatic/persuasive padding ("调试超能力", "盯着代码看多久都救不了你") that could be trimmed.

4 / 5

Actionability

Provides a concrete ranked 10-option list, specific instrumentation advice ("[DEBUG-a4f2]" prefixes), and a verified executable script reference (scripts/hitl-loop.template.sh); mostly actionable with minor gaps in literal copy-paste code.

4 / 5

Workflow Clarity

Clear six-phase sequence with per-phase completion checklists, explicit validation gates ("在没有 red-capable command,就没有 Phase 2"), feedback loops, and a final cleanup/post-mortem checklist.

5 / 5

Progressive Disclosure

Well-structured phased body with a single one-level-deep, clearly-signaled bundle reference (scripts/hitl-loop.template.sh, verified real); content is appropriately inline for a process-discipline skill.

4 / 5

Total

17

/

20

Passed

Description

82%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 well-formed: it clearly states the skill's purpose and provides explicit natural-language trigger phrases a user would actually say. It is concise, third-person, and clearly distinguishes the skill from neighbours.

DimensionReasoningScore

Specificity

Names the domain ("棘手缺陷和性能回退") and a concrete action ("诊断循环"), but does not enumerate multiple specific actions as the score-5 anchor requires.

3 / 5

Completeness

Explicitly states both what (诊断循环 for tricky defects and perf regressions) and when ("适用于用户说 ..." with concrete trigger phrases).

5 / 5

Trigger Term Quality

Includes natural user phrases ("diagnose", "debug this") plus symptom terms ("broken、throwing、failing、slow"); good coverage with a few synonyms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (diagnostic loop for tricky bugs/perf regressions) with distinct triggers, minimal overlap risk with other skills.

5 / 5

Total

17

/

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
vinvcn/mattpocock-skills-zh-CN
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.