CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

codacy

Fetch Codacy findings and autonomously fix them. Works in two modes — pr (findings on the current open PR) and backlog (all open repository findings). Usage: /codacy [pr|backlog] [--categories all|quality|security-and-error-prone]

Quality

80%

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/codacy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 lean, command-driven workflow that is fully executable through the validation stage and appropriately compact for a skill whose job is delegation. Its main gap is the missing verification loop after the batch fixing is delegated — nothing tells Claude to confirm that the fixes actually succeeded before finishing.

Suggestions

Add post-fix verification steps: after the codacy-handler agent finishes, re-fetch Codacy findings to confirm they are resolved and run relevant tests before reporting completion.

Include a concrete example of the delegation prompt with real values (e.g., mode: 'backlog', categories: 'quality') and specify how the handler agent is spawned.

DimensionReasoningScore

Conciseness

At roughly 40 lines with a compact argument table, exact commands, and no background explanation of concepts Claude already knows — 'Check each of the following. On failure, print a clear error and stop' instructs without padding — the body matches anchor 5's 'lean and efficient; every token earns its place'. Not 4 because there are no instances of over-explanation that could be trimmed.

5 / 5

Actionability

Every validation step gives an exact, copy-paste-ready command ('gh pr view --json number', 'op --version', 'git branch --show-current', 'git rev-parse --is-inside-work-tree'), matching anchor 4's 'concrete code or commands with minor gaps'. Not 5 because the delegation step is a placeholder template ('Run the codacy-handler workflow with: mode: `<resolved mode>`') with no concrete example prompt, and 'print a clear error' specifies no error content; not 3 because nothing is pseudocode and the commands are fully executable.

4 / 5

Workflow Clarity

The sequence (parse arguments → validate preconditions → delegate) is clearly ordered with an explicit stop-on-failure checkpoint ('On failure, print a clear error and stop — do not spawn the agent'), but the skill's purpose is autonomously fixing findings — a batch code-change operation — and there is no verification after the agent runs (no re-check of findings, no tests, no diff review), so per the batch-operation cap it cannot exceed anchor 3 ('sequence present but checkpoints missing'). Not 4 precisely because the missing outcome-verification is more than a minor gap for batch fixes.

3 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files and no external references to organize, and its three well-labeled sections ('## Parse arguments', '## Validate preconditions', '## Delegate to agent') organize the content cleanly, so the simple-skill exception applies and anchor 5 is warranted. Not 4 because there is no content that should have been split out and no organization gaps.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific and highly distinctive thanks to the Codacy brand name, clearly stating what the skill does in both of its modes with exact usage syntax. Its weakness is completeness: with no 'Use when...' trigger clause, Claude receives no explicit guidance on when to activate the skill, and common synonyms such as 'Codacy issues' or 'code quality' are missing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Codacy, Codacy findings/issues, or asks to fix code-quality or static-analysis findings.'

Include common synonyms such as 'Codacy issues', 'code quality violations', or 'static analysis findings' so the description matches natural user phrasing.

Briefly state what fixing involves (e.g., 'edits code to resolve each finding and opens a PR') to strengthen specificity.

DimensionReasoningScore

Specificity

Concrete actions are named — 'Fetch Codacy findings and autonomously fix them' — plus two precisely defined modes ('pr (findings on the current open PR)' and 'backlog (all open repository findings)') and exact usage syntax, matching anchor 4's 'several specific actions; minor gaps in coverage'. Not 5 because only two actions are listed and 'autonomously fix them' never specifies what fixing involves; not 3 because the mode semantics and full invocation string go well beyond naming the domain with one or two bare actions.

4 / 5

Completeness

The 'what' is explicit ('Fetch Codacy findings and autonomously fix them', elaborated by both modes), but there is no 'Use when...' clause or equivalent trigger guidance — the 'Usage: /codacy [pr|backlog]...' string documents invocation syntax, not activation conditions — which matches anchor 3 ('clear what but when missing') and is capped there by the guideline. Not 4 because the 'when' is entirely absent rather than present but under-specified.

3 / 5

Trigger Term Quality

Natural terms a user would say include 'Codacy', 'findings', 'fix', 'pr', 'backlog', and the category names ('quality', 'security-and-error-prone'), matching anchor 4's 'good keyword coverage; a few natural terms missing'. Not 5 because common variations and synonyms such as 'Codacy issues', 'violations', 'code quality', or 'static analysis findings' are absent; not 3 because coverage exceeds 'some relevant keywords' by pairing the distinctive product name with natural mode and category vocabulary.

4 / 5

Distinctiveness Conflict Risk

'Codacy' is a distinctive brand name that cleanly separates this skill from any other, and the mode/finding vocabulary reinforces the niche, matching anchor 5's 'clear niche with distinct triggers; minimal conflict risk'. Not 4 because the branded tool name leaves virtually no overlap window with generic code-quality or lint skills.

5 / 5

Total

16

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

koenighotze/wheel-of-meeting

Path

.claude/skills/codacy/SKILL.md

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.