CtrlK
BlogDocsLog inGet started
Tessl Logo

implement-issue

Triage, plan, and implement a fix or feature for a GitHub issue end-to-end

64

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/implement-issue/SKILL.md
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.

The body is a highly actionable, well-sequenced workflow with strong validation checkpoints and clearly signaled references to companion skills and rules. The only minor weakness is a few explanatory sentences that assume Claude needs the "why" spelled out.

DimensionReasoningScore

Conciseness

The body is mostly directive and lean with concrete commands, but contains a few justifying sentences that could be trimmed (e.g. "This step prevents wasted effort on the wrong solution", "This is valuable when you cannot fully predict...").

4 / 5

Actionability

It provides copy-paste-ready commands (`gh issue view ... --json ...`, `make format && make lint`, `pwd`, branch-name format), concrete conventions (`Dict[str, Any]`, `def test_*() -> None:`, `@pytest.mark.parametrize`), and a full report template covering the common cases.

5 / 5

Workflow Clarity

Eight numbered steps with sub-steps are clearly sequenced, and verification (7a/7b/7c) includes explicit validation, feedback loops ("Stop and fix issues before proceeding"), human-approval gates (ExitPlanMode, confirm-before-commit), and a hard stop on cwd mismatch.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned with clear headers and one-level-deep, well-signaled cross-skill/rule references (`/worktree-from-issue`, `/review-pr`, `@CLAUDE.md`, `@.claude/rules/worktree.md`), with only minor inlining of the review checklist and report template.

4 / 5

Total

18

/

20

Passed

Description

66%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.

The description is concrete and domain-specific with natural trigger terms, but it omits an explicit "Use when..." trigger clause, which caps its completeness. Adding when-to-use guidance would lift the strongest remaining weakness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to implement, fix, or address a GitHub issue (by number or URL)."

Add natural synonyms to broaden trigger coverage, such as "ticket", "bug", or "enhancement".

Optionally name sub-actions (e.g. "with tests and verification") to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

"Triage, plan, and implement" lists three concrete verbs scoped to "a fix or feature for a GitHub issue end-to-end", giving several specific actions with only minor coverage gaps (no explicit testing/doc sub-actions named).

4 / 5

Completeness

The "what" is clear (triage/plan/implement a GitHub issue end-to-end), but there is no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Natural terms "GitHub issue", "fix", and "feature" are phrases a user would say, but common synonyms like "ticket", "bug", or "enhancement" are absent.

4 / 5

Distinctiveness Conflict Risk

The GitHub-issue end-to-end implementation framing is a distinct niche with minor overlap risk against generic implementation skills, but no synonyms further differentiate the trigger.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
dlt-hub/dlt
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.