fix-issue

Use when working on a GitHub issue - fetches issue details, analyzes codebase, implements fix following project methodology

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/fix-issue/SKILL.md

Quality

Content

77%Weight 40%Scale 1-3

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

The skill body is highly actionable and workflow-clear, with concrete commands, file tables, validation checkpoints, and checklists. Its weaknesses are mild redundancy (duplicated quick-reference and diagram) and a monolithic single-file structure with no progressive split.

Suggestions

Remove the Quick Reference table (or the flow diagram) since both restate commands and steps already covered in the numbered sections, reducing token cost.

Move the large detail blocks (Key Files by Area, Contributor Credit, Community Communication) into reference files and link to them one level deep, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands and no concept-explaining fluff, but the Quick Reference table and flow diagram duplicate commands and steps already present in the sections, so it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready gh/terraform/git commands, file-path tables keyed by area, an exact commit-message template, and verifiable co-authorship trailer commands, matching the fully-executable anchor.	3 / 3
Workflow Clarity	An explicit 8-step sequence with a flow diagram, validation checkpoints (fmt/init/validate, plan must not destroy), test checklists, and dedicated destructive-op (teardown) guidance meets the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	No bundle files exist and the content is a large single-file monolith that holds both overview and detail inline; it is well-organized into sections but never splits detail out, matching the 'some structure but content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

77%Weight 40%Scale 1-3

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 strong on specificity and completeness, with concrete actions and an explicit 'Use when...' trigger. It is held back by limited trigger-term coverage and some overlap risk with adjacent issue/PR skills.

Suggestions

Broaden trigger terms to include natural variations users would say, e.g. 'Use when fixing a bug report or GitHub issue, or implementing a fix for a reported issue'.

Sharpen distinctiveness by scoping the trigger to the project context (e.g. 'for the terraform-hcloud-kube-hetzner module') to reduce overlap with generic issue/PR skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fetches issue details, analyzes codebase, implements fix following project methodology' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what it does (fetches/analyzes/implements) and when to use it via an explicit 'Use when...' trigger clause, satisfying the anchor for clearly answering both what AND when.	3 / 3
Trigger Term Quality	Includes one natural user term ('working on a GitHub issue') but lacks common variations like 'bug report' or 'fix an issue', so it lands at 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The 'GitHub issue' niche is somewhat specific but overlaps with neighboring PR/review skills (the body itself references a review-pr skill), so it could still trigger for similar skills rather than having a wholly distinct niche.	2 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: mysticaltech/terraform-hcloud-kube-hetzner
Path: .claude/skills/fix-issue/SKILL.md
Commit: a8b696d

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.