CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

variant-analysis

Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.

Quality

82%

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 variant-analysis in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 teaches a genuinely actionable, well-sequenced methodology with validation checkpoints and a feedback loop, and it is mostly token-efficient. Its one serious defect is progressive disclosure: it references METHODOLOGY.md and an entire resources/ tree of CodeQL/Semgrep templates that are absent from the bundle, leaving the skill's most concrete deliverables unreachable.

Suggestions

Add the referenced bundle files — METHODOLOGY.md and the resources/ templates (codeql/*.ql, semgrep/*.yaml, variant-report-template.md) — to the skill directory, or remove the references if those materials are not shipped.

Inline one small worked example of an exact-match pattern and its generalized Semgrep or CodeQL form, so the core generalize-and-verify loop is executable even when the template files are unavailable.

Tighten the 'Critical Pitfalls' section by collapsing the repeated Example/Mitigation boilerplate into a compact table, and drop the 'You are a variant analysis expert' role-play opener.

DimensionReasoningScore

Conciseness

The body is mostly dense and efficient — decision tables for abstraction points and tool selection, a numbered generalization loop, and concrete stop conditions ('Stop when false positive rate exceeds ~50%'). Minor trimming opportunities exist: the role-play opener ('You are a variant analysis expert. Your role is to...') and the four-fold repeated Example/Mitigation boilerplate in the pitfalls section add tokens without proportionate value. This matches anchor 4 ('efficient; minor instances of over-explanation') rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Provides mostly concrete, executable guidance: an exact-match ripgrep command, a verification criterion ('Does it match exactly ONE location (the original)?'), a specific FP-rate threshold, and an element-by-element abstraction decision table. The gap keeping it below anchor 5 is that the sole code block is a placeholder ('rg -n "exact_vulnerable_code_here"') and the real CodeQL/Semgrep query templates are deferred to external files, so the body itself lacks a copy-paste-ready worked example. It clearly exceeds anchor 3's pseudocode level.

4 / 5

Workflow Clarity

The five-step process is clearly sequenced with explicit validation checkpoints and a genuine feedback loop: verify the initial pattern matches exactly one location, review ALL new matches after each single-element generalization, classify true/false positives, and 'If FP rate too high, revert and try different abstraction' — an explicit error-recovery loop with a defined stop condition. This matches anchor 5 ('clear sequence with explicit validation steps; feedback loops for error recovery'). The destructive/batch-operation cap does not apply since pattern searches are read-only.

5 / 5

Progressive Disclosure

References are clearly signaled and one level deep ('For deeper strategic guidance, see METHODOLOGY.md'; 'resources/codeql/': python.ql, javascript.ql, etc.), but none of these files exist in the bundle — there is no METHODOLOGY.md and no resources/ directory, nor any references/, scripts/, or assets/ folders. Navigation to the deeper content fails entirely, which is a worse structural failure than the unclear signaling of anchor 3; it matches anchor 2's 'minimal structure' in effect, since the disclosure promise is unfulfilled and the listed templates (a key part of the skill's value) are inaccessible.

2 / 5

Total

15

/

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 and explicitly states both capability and trigger conditions in third person, with specific, natural trigger terms including tool names. Its only weaknesses are minor: slightly incomplete action coverage and some broad trigger phrases that could overlap with general security-audit skills.

DimensionReasoningScore

Specificity

Names several concrete actions in third person — 'Find similar vulnerabilities and bugs across codebases using pattern-based analysis', 'building CodeQL/Semgrep queries', 'performing systematic code audits' — with only minor coverage gaps (e.g., no mention of triage or reporting outputs). It lists several specific actions but is not fully comprehensive, matching anchor 4 rather than 5, and clearly exceeds the 1-2 actions of anchor 3.

4 / 5

Completeness

Explicitly answers both: what it does ('Find similar vulnerabilities and bugs across codebases using pattern-based analysis') and when to use it ('Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue') with concrete trigger phrases. This matches the anchor 5 example pattern exactly; anchor 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Includes natural phrases users would say when needing this skill: 'hunting bug variants', 'building CodeQL/Semgrep queries', 'systematic code audits', 'after finding an initial issue'. A few natural synonyms are missing (e.g., 'find similar issues', 'find other instances of this bug'), which matches anchor 4's 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche — variant analysis after an initial finding is discovered — with distinct tool-specific triggers (CodeQL/Semgrep, bug variants). However, the broader phrases 'analyzing security vulnerabilities' and 'systematic code audits' create minor overlap risk with general security-audit skills, matching anchor 4 ('mostly distinct; minor overlap risk') rather than anchor 5's minimal conflict risk.

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/variant-analysis/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.