CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

detail-bugs

Interact with Detail bugs for a repository via the CLI — list and filter bugs, inspect reports, close as resolved or dismissed, reopen previously closed bugs, and override a bug's priority. Also covers security scan findings (`detail vulns`): list, show, close, and reopen.

1.00x
Quality

85%

Does it follow best practices?

Impact

100%

1.00x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 CLI reference: every command is copy-paste executable with flags, defaults, edge behaviors, and auth-error recovery, and disambiguation between bugs and vulns surfaces is handled explicitly. The only minor weaknesses are a couple of trimmable meta-sentences and the fact that all reference material lives inline in one ~107-line file.

DimensionReasoningScore

Conciseness

The body is a dense CLI reference with no explanation of concepts Claude already knows — every flag, default, and ID format is Detail-specific and non-obvious. Not 5: a few meta-sentences could be trimmed, e.g. 'This skill describes both surfaces so you can pick the right command for whatever the user is trying to do.'; not 3: the padding is minor and there are no unnecessary explanations.

4 / 5

Actionability

Every command is fully executable with exact flag syntax, defaults, example combinations (e.g. '--status resolved,dismissed'), ID formats ('wr_…', 'ssf_…'), an install one-liner, and an auth-error fallback ('detail auth login'). Copy-paste ready and covering the common cases; no gaps that would warrant 4.

5 / 5

Workflow Clarity

Sequencing is clear (prerequisites, auth, repo inference, then commands) with a real feedback loop for auth failures and explicit disambiguation guidance ('--vulns' vs 'detail vulns list', '--priority p1,p2,p3' vs 'p1', reopen as the inverse of close, prioritize no-op behavior). The state-changing operations are documented as reversible, so the destructive/batch cap does not apply. Not 4: checkpoints and error-recovery guidance are present, not merely implied.

5 / 5

Progressive Disclosure

Well-organized single file with clear per-command sections and consistent flag formatting, and no bundle files exist so nothing is mis-filed. Not 5: the body is ~107 lines of inline reference material with no external files, exceeding the under-50-lines exception; not 3: the structure is clean and navigable with no content that clearly belongs in a separate file.

4 / 5

Total

18

/

20

Passed

Description

75%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 specific, comprehensive, and product-scoped description that clearly states what the skill does across both the bugs and vulns surfaces. Its main weakness is the missing 'Use when...' trigger clause, which caps completeness, and a few absent natural synonyms like 'vulnerabilities'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Detail, asks to list/close/reopen bugs or security findings, or wants to change a bug's priority.'

Include natural synonyms such as 'vulnerabilities' or 'security issues' alongside 'security scan findings' so the description matches how users commonly phrase those requests.

Mention that workflow/scan IDs come from 'detail scans list' or 'detail vulns scans' implicitly via 'scan' terminology to catch 'scan results' queries.

DimensionReasoningScore

Specificity

The description enumerates concrete actions for both surfaces — 'list and filter bugs, inspect reports, close as resolved or dismissed, reopen previously closed bugs, and override a bug's priority' plus 'list, show, close, and reopen' for security scan findings — comprehensively matching every subcommand documented in the body. Not 4: there are no meaningful coverage gaps relative to the skill's actual capabilities.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4: 'when' is entirely absent rather than merely implicit or under-specified.

3 / 5

Trigger Term Quality

Good natural keyword coverage — 'bugs', 'close', 'resolved or dismissed', 'reopen', 'priority', 'security scan findings' — but common synonyms like 'vulnerabilities', 'security issues', or 'triage' are absent. Not 5: anchor 5 requires comprehensive synonym coverage, which this lacks; not 3: the included terms are natural phrases users would say, not jargon.

4 / 5

Distinctiveness Conflict Risk

The description is scoped to the Detail CLI by name for both bugs and security scan findings, giving it a clear niche with distinct triggers and minimal conflict risk against generic bug-tracking skills. Not 4: the product-specific framing leaves little overlap risk with closely related 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

usedetail/cli

Path

.claude/skills/detail-bugs/SKILL.md

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.