CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 well-structured, actionable review workflow: clear phase sequencing, explicit verification and pre-conclusion audits, and a concrete output contract. The only improvements are trimming mild boilerplate (When to Use / Limitations) and giving Phase 4's verification steps concrete commands.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (it never explains what XSS, CSRF, or TOCTOU are), but the "When to Use" section largely repeats the frontmatter description and the "Limitations" section is generic boilerplate ("Use this skill only when the task clearly matches the scope described above"). These minor padded spots keep it below the 5 anchor.

4 / 5

Actionability

Concrete, executable guidance dominates: a copy-paste-ready diff command (`git diff $(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')...HEAD`), a specific per-file security checklist, and a structured output template with defined fields. Minor gaps remain — Phase 4's "Search for existing tests" and "Read surrounding context" are high-level directions without concrete commands or examples.

4 / 5

Workflow Clarity

Five clearly sequenced phases with explicit checkpoints ("If output is truncated, read each changed file individually until you have seen every changed line"; "Before finalizing, you MUST... Only then provide your final findings"), a verification feedback loop (check existing handling/tests before reporting), and a full checklist. The skill is explicitly read-only ("Do not make changes"), so no destructive-operation cap applies; this matches the 5 anchor's sequence, validation, and checklists.

5 / 5

Progressive Disclosure

Well-organized sections with no nested or dead references and no bundle files to mis-navigate. However, the body is ~75 lines (above the under-50-line simple-skill exception) and the Phase 3 security checklist is reference-shaped material kept inline, so structure is good rather than optimal.

4 / 5

Total

17

/

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: third-person, concrete about what the skill does, and with an explicit 'Use when...' clause containing natural trigger phrases. Its only weaknesses are modest — slightly thinner synonym coverage for triggers and some overlap potential with general code-review skills.

DimensionReasoningScore

Specificity

"Find bugs, security vulnerabilities, and code quality issues in local branch changes" lists several specific action types in a named domain (branch diff review). It falls short of the 5 anchor's comprehensive multi-action coverage and is clearly above the 1-2 concrete actions of the 3 anchor.

4 / 5

Completeness

Explicitly answers both what ("Find bugs, security vulnerabilities, and code quality issues in local 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, matching the 5 anchor; the 4 anchor's caveat about an insufficiently explicit 'when' does not apply.

5 / 5

Trigger Term Quality

"review changes, find bugs, security review, or audit code on the current branch" provides good natural-phrase coverage users would actually say. A few common variants are missing (e.g. "code review", "vulnerabilities", "PR review"), keeping it below the 5 anchor's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The branch-diff review/audit scope carves a clear niche, but triggers like "review changes" carry minor overlap risk with generic code-review skills, matching the 4 anchor rather than the 5 anchor's minimal-conflict niche.

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.

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/find-bugs/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.