CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-review

Verify fix commits address audit findings without new bugs

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/fix-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 well-sectioned and appropriately scoped, but it is heavily redundant and operates entirely at the level of abstract directives — it never tells the reviewer how to concretely verify a fix (no commands, criteria, or examples). Consolidating the repeated framing into one section and replacing generic advice with specific, executable checks would substantially improve it.

Suggestions

Merge the Overview, When to Use, and Instructions sections, which restate the same sentence three to four times, into a single concise statement plus a trigger list.

Add concrete executable guidance, e.g., commands like `git show <fix-commit>` or `git diff <finding-commit>..<fix-commit>`, and specific criteria for judging root-cause vs. symptom fixes.

Turn the Review Process checkpoints into explicit pass/fail validation steps (e.g., 'If tests do not cover the fixed scenario, flag the fix as incomplete') with an error-recovery path.

DimensionReasoningScore

Conciseness

The core claim is restated roughly four times ("Verify that fix commits properly address audit findings" in Overview, "Use this skill when you need to verify fix commits address audit findings without new bugs", the Instructions intro, and the numbered list), and Best Practices duplicates Review Process items (e.g., test coverage appears in both). This is noticeably verbose with padded, redundant sections (anchor 2) rather than merely 'could be tightened' (anchor 3), since the body could be cut by more than half without losing information.

2 / 5

Actionability

Guidance consists of high-level directives like "Compare the fix against the original audit finding" and "Check for potential side effects" with no commands (e.g., git diff/show usage), no criteria distinguishing a root-cause fix from a symptom fix, and no examples. This matches anchor 2 ('Minimal concrete guidance; high-level hints but missing the specific steps to execute'); it does not reach 3 because nothing concrete or executable is provided beyond abstract directives.

2 / 5

Workflow Clarity

The Review Process presents a coherent five-step sequence and includes check-like steps ("Validate that tests cover the fixed scenario", "Ensure no similar vulnerabilities exist elsewhere"), but the checkpoints are implicit and lack explicit pass/fail criteria or error-recovery guidance. This fits anchor 3 ('Steps listed but validation gaps; sequence present but checkpoints missing or implicit') rather than 4, whose checkpoints would be concrete and mostly explicit.

3 / 5

Progressive Disclosure

The skill is short with clearly labeled sections and no nested or buried references, fitting the simple-skill pattern. It scores 4 rather than 5 because the redundant overlapping sections (Overview / When to Use / Instructions / Best Practices) create organization gaps that well-placed consolidation would fix.

4 / 5

Total

11

/

20

Passed

Description

53%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 clear and appropriately scoped to a distinct niche, with a concrete 'what' stated in third person. Its main weaknesses are the complete absence of a 'Use when...' trigger clause and limited keyword variation, which leave it at the middle of the scale on completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when reviewing commits that remediate security audit findings, patches, or regression fixes.'

Include natural synonyms users would say, such as 'remediation', 'patch review', or 'regression', to broaden trigger-term coverage.

Enumerate one or two more concrete actions (e.g., 'confirms root cause is fixed and no regressions introduced') to raise specificity.

DimensionReasoningScore

Specificity

The description names the domain ("fix commits", "audit findings") and one to two concrete actions ("Verify... address audit findings", "without new bugs" implying regression checking), but does not comprehensively cover the skill's actions. It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than anchor 4, which requires several specific listed actions.

3 / 5

Completeness

The 'what' is clear (verify fix commits address audit findings without new bugs) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"fix commits", "audit findings", and "bugs" are natural, relevant keywords, but common variations users would say — such as "remediation", "patch", "regression", or "security fix" — are missing. This fits anchor 3 ('Some relevant keywords but missing common variations or synonyms') better than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The audit-remediation verification niche is mostly distinct with clear triggers around fix commits and audit findings; the main overlap risk is with generic code-review skills. This matches anchor 4 ('Mostly distinct; minor overlap risk with closely related skills') rather than 5, since the triggers lack synonyms that would fully separate it from general review skills.

4 / 5

Total

13

/

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.

Validation — 15 / 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

BigSimmo/Communication

Path

.agents/skills/fix-review/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.