CtrlK
BlogDocsLog inGet started
Tessl Logo

detail-bugs

Interact with Detail bugs for a repository via the CLI — list and filter bugs, inspect reports, close as resolved or dismissed, and reopen previously closed bugs.

85

3.33x
Quality

77%

Does it follow best practices?

Impact

100%

3.33x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/detail-bugs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-crafted reference skill that efficiently documents four CLI subcommands with precise flag syntax, defaults, and accepted values. It respects Claude's intelligence by avoiding unnecessary explanation and provides fully actionable command invocations. The only notable gap is the lack of verification steps after state-changing operations (close/reopen), which would strengthen workflow clarity.

Suggestions

Add a brief verification step after close/reopen operations (e.g., 'Verify with `detail bugs show <BUG_ID>` to confirm the status change took effect').

DimensionReasoningScore

Conciseness

The content is lean and efficient. It avoids explaining what bugs are or how CLIs work, assumes Claude's competence, and every section delivers only the flags and behavior Claude needs to know. The brief prerequisites and repo inference sections are appropriately short.

3 / 3

Actionability

Every subcommand is documented with its exact invocation syntax, specific flags, accepted values, and defaults. The install command and auth fallback are concrete and copy-paste ready. No pseudocode or vague descriptions.

3 / 3

Workflow Clarity

The skill is primarily a reference for four independent subcommands rather than a multi-step workflow, so sequencing is less critical. However, the close command involves a non-interactive flag requirement that could benefit from an explicit validation step (e.g., confirming the bug was actually closed), and there's no guidance on verifying outcomes after close/reopen operations.

2 / 3

Progressive Disclosure

For a skill with no bundle files and a focused scope (four subcommands), the content is well-organized with clear section headers per subcommand. The structure is flat and easy to navigate, and the content length is appropriate for inline presentation without needing external references.

3 / 3

Total

11

/

12

Passed

Description

67%

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 does well at listing specific concrete actions and identifying a clear niche around 'Detail bugs' via CLI. Its main weakness is the lack of an explicit 'Use when...' clause, which caps completeness. Adding trigger guidance and a few more natural keyword variations would strengthen it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Detail bugs, wants to view bug reports, close or reopen bugs, or manage bug status via CLI.'

Include natural keyword variations such as 'bug tracker', 'issues', 'defects', or 'bug reports' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: list and filter bugs, inspect reports, close as resolved or dismissed, and reopen previously closed bugs. These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the description of capabilities.

2 / 3

Trigger Term Quality

Includes relevant terms like 'bugs', 'CLI', 'close', 'reopen', 'filter', but 'Detail' is a specific product name that users may or may not naturally reference. Missing common variations like 'bug tracker', 'issues', or 'defects'.

2 / 3

Distinctiveness Conflict Risk

The mention of 'Detail bugs' as a specific product/tool combined with 'CLI' creates a clear niche. The specific actions (close as resolved/dismissed, reopen) further distinguish it from generic bug tracking or issue management skills.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
usedetail/cli
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.