CtrlK
BlogDocsLog inGet started
Tessl Logo

find-bugs

Find bugs, security vulnerabilities, and code quality issues in local branch changes. Use when asked to review changes, find bugs, security review, or audit code on the current branch.

70

Quality

86%

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

The canonical home for this skill is find-bugs in roman01la/skills-agents

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.

A tight, well-sequenced review workflow with strong validation checkpoints and an actionable output format. The skill is self-contained and appropriately concise; the only structural weakness is the absence of a brief overview pointing into the phases.

Suggestions

Add a one-line overview at the top of the body (e.g. 'Five-phase review: gather diff -> map attack surface -> security checklist -> verify -> audit -> report') so the structure is navigable at a glance.

For each security checklist item, add a concrete detection hint or example pattern so the 'how' is as actionable as the 'what'.

Consider moving the per-issue output format template into a short code block to make it copy-paste ready alongside the git diff command.

DimensionReasoningScore

Conciseness

Lean procedural checklist with no padding or explanation of concepts Claude already knows; every section earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides a copy-paste-ready git diff command and a concrete output format (File:Line, Severity, Problem, Evidence, Fix, References), but the security checklist items describe what to check rather than how, leaving minor gaps.

4 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints (Phase 4 Verification, Phase 5 Pre-Conclusion Audit with a MUST gate) and a checklist for a complex review process.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and self-contained content; scores just under 5 because it is a single monolithic file slightly over the 50-line simple-skill threshold with no overview/summary at the top.

4 / 5

Total

18

/

20

Passed

Description

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

A strong description that clearly states both capability and trigger conditions in concise third-person voice. The main weakness is breadth of verbs/synonyms rather than structure.

DimensionReasoningScore

Specificity

Lists several specific target areas ('bugs, security vulnerabilities, and code quality issues in local branch changes') but the verbs are a single generic 'Find' applied to broad categories, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (find bugs/security/quality issues in branch changes) and 'when' ('Use when asked to review changes, find bugs, security review, or audit code on the current branch') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users say ('review changes, find bugs, security review, or audit code') with good coverage, though it omits common synonyms like 'code review' or 'vulnerabilities'.

4 / 5

Distinctiveness Conflict Risk

The 'local branch changes' / 'current branch' scoping gives it a clear niche, but it retains minor overlap risk with general code-review and security-review skills.

4 / 5

Total

17

/

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.