CtrlK
BlogDocsLog inGet started
Tessl Logo

bug-capture

Capture a user-reported defect as a durable GitHub issue written in the project's own domain language. Explores the codebase in parallel for context but never leaks file paths or line numbers into the issue. Use when the user reports a bug conversationally, runs a QA pass, or says "file an issue", "log this as a bug", "capture this".

72

Quality

88%

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

90%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 tight, highly actionable skill body that gives concrete commands and templates for an outward-facing operation, with sensible pre-filing validation. The only soft spot is the absence of an explicit post-file verification checkpoint.

Suggestions

Add a post-file verification step (e.g., confirm each created issue URL resolves and that child issues correctly reference their parent number) to turn the pre-flight validation into a full validate→fix→retry loop.

Reconsider step 5's 'File without asking the user to review the draft' — for a batch breakdown, a quick draft review checkpoint would strengthen workflow_clarity for an outward-facing, hard-to-reverse action.

If the issue templates grow, factor them into a references/ file with a one-level-deep link from SKILL.md to lift progressive_disclosure toward a 5.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — assumes Claude knows git, gh, and GitHub issues, with no concept-explaining padding; even its opinionated asides ('Over-interviewing is a tax the reporter pays for your uncertainty') are actionable guidance that earn their tokens.

5 / 5

Actionability

Provides fully executable, copy-paste-ready guidance: concrete gh commands with exact flags, plus complete single-issue and child-issue templates covering the common filing cases.

5 / 5

Workflow Clarity

A clearly sequenced 7-step flow with real pre-flight checkpoints (duplicate search in step 3, mandatory reproduction with a go-back-to-user feedback loop), but step 5 deliberately skips draft review and there is no post-file verification — minor validation gaps rather than missing validation.

4 / 5

Progressive Disclosure

Self-contained with no bundle files, well-organized under a numbered Flow with clear headers and inline templates, and no nested references; at ~108 lines it exceeds the under-50-line simple-skill exception, so it lands just below a 5.

4 / 5

Total

18

/

20

Passed

Description

87%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, specific description that clearly states both capability and trigger conditions in third person with natural user phrasing. It distinguishes itself well via the domain-language and no-leakage framing.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Capture a user-reported defect as a durable GitHub issue', 'Explores the codebase in parallel') plus a specificity constraint ('never leaks file paths or line numbers'), with only minor coverage gaps rather than comprehensive multi-action listing.

4 / 5

Completeness

Explicitly answers both what (capture a defect as a durable domain-language GitHub issue) and when, with concrete trigger phrases in the 'Use when...' clause.

5 / 5

Trigger Term Quality

Includes natural phrases a user would actually say ('file an issue', 'log this as a bug', 'capture this', 'reports a bug conversationally', 'runs a QA pass') — good keyword coverage, though not an exhaustive synonym set.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (user-reported bug → durable GitHub issue in domain language) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

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
rohitg00/pro-workflow
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.