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.

1.28x
Quality

90%

Does it follow best practices?

Impact

100%

1.28x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent instruction-only skill body: a tightly scoped, phased review workflow with explicit verification and audit checkpoints, a prioritized output format, and no wasted tokens. The only minor gap is the absence of concrete commands for the verification steps in Phase 4.

DimensionReasoningScore

Conciseness

The body is lean and instructional throughout: checklists, one concrete git command, and an output spec, with zero padding or explanations of concepts Claude already knows (e.g., it never explains what XSS or CSRF are). Every token earns its place, matching the top anchor.

5 / 5

Actionability

Provides a copy-paste git diff command and checklists naming specific vulnerability classes with a structured output format, which is mostly executable guidance. Not a 5 because verification steps like 'Search for existing tests covering the scenario' lack concrete commands or examples.

4 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints: Phase 4 verifies each potential issue against existing handling and tests, and Phase 5 is a pre-conclusion audit checklist (files read, checklist items resolved, unverifiable areas listed). The skill is explicitly read-only ('Do not make changes'), so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

A compact (~46 non-blank line) single-purpose skill with no external references needed and well-organized section headers per phase. Per the simple-skill guideline, well-organized sections alone merit the top score; there are no bundle files to structure.

5 / 5

Total

19

/

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 third person with natural user phrasing. The main improvement opportunity is broader trigger synonym coverage (e.g., 'code review', 'security audit').

Suggestions

Add common trigger synonyms such as 'code review', 'security audit', or 'review my diff/PR' to the 'Use when' clause to improve trigger term coverage.

Consider naming one or two more specific analysis actions (e.g., 'analyzes diffs for injection flaws, race conditions, and insecure crypto') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Find bugs, security vulnerabilities, and code quality issues') scoped to 'local branch changes', matching the several-specific-actions anchor with minor coverage gaps. Not a 5 because the actions are broad categories rather than an exhaustive set of distinct concrete operations.

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 top anchor. A 4 would require the 'when' clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

'review changes, find bugs, security review, audit code' are phrases users would naturally say, giving good keyword coverage. Not a 5 because common synonyms like 'code review', 'security audit', or 'PR review' are missing.

4 / 5

Distinctiveness Conflict Risk

Scoping to 'local branch changes' and security/bug finding gives it a clear niche with distinct triggers, but it could overlap with general code-review skills. Mostly distinct with minor overlap risk, matching the 4 anchor.

4 / 5

Total

17

/

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

BigSimmo/PsychSift

Path

.claude/cloud-profile/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.