CtrlK
BlogDocsLog inGet started
Tessl Logo

implement-issue

Use when given a GitHub issue number and base branch to implement end-to-end

72

3.20x
Quality

59%

Does it follow best practices?

Impact

93%

3.20x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/implement-issue/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

79%

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-structured, concise skill that provides clear invocation commands, monitoring techniques, and reference tables for stages, exit codes, and agent selection. Its main weakness is the lack of explicit error recovery guidance—when a stage fails or max iterations are exceeded, there's no feedback loop or troubleshooting steps for Claude to follow. The progressive disclosure is adequate but unverifiable without bundle files.

Suggestions

Add error recovery guidance: what should Claude do when exit code 1 or 2 is returned? Include a troubleshooting section with specific steps (e.g., check stage logs, retry with different agent).

Add a validation checkpoint after invocation—e.g., 'Verify status.json shows state: complete and exit code 0 before reporting success to the user.'

DimensionReasoningScore

Conciseness

The content is lean and well-structured. Every section serves a purpose—invocation, monitoring, stages, exit codes, agent selection—without explaining concepts Claude already knows. No filler or unnecessary context.

3 / 3

Actionability

Provides exact bash commands for invocation and monitoring, a complete stage table, exit code reference, and agent selection guide. The commands are copy-paste ready with clear argument placeholders.

3 / 3

Workflow Clarity

The stages table clearly lists the pipeline sequence, but the skill delegates all workflow logic to the orchestrator script. There are no explicit validation checkpoints or error recovery steps described—if a stage fails, there's no guidance on what Claude should do beyond checking exit codes.

2 / 3

Progressive Disclosure

References schemas in `.claude/scripts/schemas/` and logs directory, but no bundle files are provided to verify these exist. The content is well-sectioned but could benefit from clearer links to the orchestrator script details and agent configuration files rather than just mentioning their locations.

2 / 3

Total

10

/

12

Passed

Description

40%

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 provides a trigger condition ('Use when given a GitHub issue number and base branch') but completely fails to describe what the skill actually does beyond the vague phrase 'implement end-to-end.' It lacks specific actions, concrete capabilities, and sufficient trigger term coverage to reliably distinguish it from other development-related skills.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Reads a GitHub issue, creates a feature branch, implements the required code changes, runs tests, and opens a pull request.'

Expand trigger terms to include natural variations like 'implement issue', 'fix issue', 'GH issue', 'pull request', 'feature implementation', 'bug fix'.

Clarify the scope of 'end-to-end' — does it include code generation, testing, PR creation, or all of the above?

DimensionReasoningScore

Specificity

The description says 'implement end-to-end' but never specifies what concrete actions are performed. There are no specific capabilities listed — no mention of what 'end-to-end' implementation entails (e.g., reading issues, creating branches, writing code, opening PRs).

1 / 3

Completeness

It has a 'Use when' clause specifying the trigger condition (given a GitHub issue number and base branch), but the 'what does this do' part is extremely vague — 'implement end-to-end' doesn't explain what actions the skill performs.

2 / 3

Trigger Term Quality

It includes 'GitHub issue number' and 'base branch' which are natural terms a user might use, but it's missing common variations like 'issue', 'PR', 'pull request', 'implement feature', 'fix bug', or 'GH issue'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'GitHub issue number' and 'base branch' provides some distinctiveness, but 'implement end-to-end' is so vague it could overlap with any coding, development, or GitHub-related skill.

2 / 3

Total

7

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
aaddrick/claude-desktop-debian
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.