CtrlK
BlogDocsLog inGet started
Tessl Logo

issue-analysis

Deep analysis of a single GitHub issue with codebase exploration, implementation planning, and architectural assessment. Use when you need to analyze a GitHub issue, assess its complexity, plan implementation approaches, and post a structured analysis comment. Triggers on "analyze issue", "deep analysis", "/issue-analysis <number>".

68

Quality

84%

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

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.

A tight, actionable single-purpose skill with a clear multi-step workflow and an explicit human-confirmation checkpoint. The main gap is placeholder substitution in the label command and the absence of separate reference files, though the latter is acceptable for a skill this small.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence and avoids explaining basic concepts; the bot-disclaimer block and label table earn their tokens, with only minor trimmable phrasing.

4 / 5

Actionability

Provides concrete executable `gh` commands and a copy-paste heredoc comment template; the label-application command uses placeholders like '<classification>' that the agent must fill in, a minor gap from fully copy-paste ready.

4 / 5

Workflow Clarity

Steps are clearly sequenced (fetch -> research -> assess -> label -> draft -> apply/post) with an explicit human-confirmation checkpoint and a validation gate ('Wait for user confirmation before proceeding'); the research-before-concluding guidance functions as a feedback loop.

5 / 5

Progressive Disclosure

Well-organized into a single concise overview with clear section headers and no external references needed (under 50 lines, single-purpose), so it scores high by the simple-skill exception; not a 5 only because no separate reference files exist to demonstrate one-level-deep navigation.

4 / 5

Total

17

/

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 description that clearly states capabilities, includes explicit 'Use when' guidance with concrete trigger phrases, and is well-differentiated. It is slightly verbose relative to the most concise good examples but covers the required elements comprehensively.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('codebase exploration', 'implementation planning', 'architectural assessment', 'post a structured analysis comment') with only minor coverage gaps; not as exhaustive as a 5.

4 / 5

Completeness

Explicitly states what the skill does and provides a clear 'Use when...' clause with concrete trigger phrases, satisfying both 'what' and 'when'.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('analyze issue', 'deep analysis', '/issue-analysis <number>') plus the slash-command form, missing only a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

Scoped to deep GitHub-issue analysis with a specific slash command and trigger terms, occupying a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
homeassistant-ai/ha-mcp
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.