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.

1.51x
Quality

77%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/cloud-profile/skills/variant-analysis/SKILL.md

The canonical home for this skill is variant-analysis in trailofbits/skills

SKILL.md
Quality
Evals
Security

Quality

Content

62%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 methodology core is excellent — a well-sequenced five-step process with explicit verification checkpoints and a revert-on-failure generalization loop — but it is undermined by redundant restatement sections, a complete absence of executable query examples in a skill about building CodeQL/Semgrep queries, and external references that point to files missing from the bundle.

Suggestions

Add the referenced files to the bundle (METHODOLOGY.md, resources/codeql/*.ql, resources/semgrep/*.yaml, resources/variant-report-template.md) or remove the references — currently every external pointer is a dead end.

Include at least one complete, executable CodeQL or Semgrep query example inline so the skill demonstrates real query syntax rather than only a placeholder rg command.

Cut the redundant "Key Principles" section and the "When to Use" list, which restate the description and Steps 1-5, to tighten token efficiency.

DimensionReasoningScore

Conciseness

The step-by-step content is dense and non-pedagogical, but two sections are redundant: "When to Use" repeats the frontmatter description, and "Key Principles" re-states Step 1 ("Root cause first"), Step 2 ("Start specific"), Step 4's stop rule ("Know when to stop: 50%+ FP rate"), and Pitfall 1 ("Search everywhere"). This duplication is more than the minor over-explanation of the 4 anchor, fitting the "mostly efficient but could be tightened" 3 anchor.

3 / 5

Actionability

The five-step process, abstraction decision table, and tool-selection matrix are concrete, but the only inline command is a placeholder (rg -n "exact_vulnerable_code_here") and no executable CodeQL or Semgrep query syntax appears anywhere — the "Ready-to-use templates" promised in resources/ are the missing key details for this query-building skill. More than minor gaps, so below the 4 anchor.

3 / 5

Workflow Clarity

The five-step process is clearly sequenced with explicit validation ("Verify: Does it match exactly ONE location (the original)?"), a feedback loop with revert rule ("If FP rate too high, revert and try different abstraction"), an explicit stop condition ("Stop when false positive rate exceeds ~50%"), and a triage checklist (Location/Confidence/Exploitability/Priority) — matching the 5 anchor's explicit validation and error-recovery loops. The workflow is read-only search, so no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The body's structure is good — clear sections with one-level, clearly signaled references to METHODOLOGY.md and the resources/ tree — but scored against the actual bundle, every referenced path is dangling: no METHODOLOGY.md, no resources/ directory, and the only bundle file (assets/trail-of-bits-mark.svg) is never referenced. The navigation structure exists on paper but delivers nothing, fitting the 3 anchor's "references present but" non-functional organization.

3 / 5

Total

14

/

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 explicitly covers both what the skill does and when to use it, with distinctive tool-name triggers (CodeQL/Semgrep) and a well-scoped post-initial-finding niche. The only weaknesses are the slightly generic "analyzing security vulnerabilities" trigger and a few missing natural synonyms such as "static analysis".

DimensionReasoningScore

Specificity

Lists several concrete actions — "Find similar vulnerabilities and bugs across codebases", "building CodeQL/Semgrep queries", "performing systematic code audits" — anchored by the concrete method "pattern-based analysis". Falls short of the 5 anchor because "analyzing security vulnerabilities" is generic and triage/reporting activities from the body are not covered.

4 / 5

Completeness

Clearly answers both parts: "what" via "Find similar vulnerabilities and bugs across codebases using pattern-based analysis" and "when" via an explicit "Use when hunting bug variants, building CodeQL/Semgrep queries, ... after finding an initial issue" clause with multiple concrete trigger phrases, matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "hunting bug variants", "CodeQL/Semgrep", "security vulnerabilities", "code audits", with the synonym pair "vulnerabilities and bugs". A few natural terms a user might say are missing (e.g., "static analysis", "SAST", "find similar issues"), so it does not reach the comprehensive-synonym coverage of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (post-discovery variant hunting) with distinct triggers like "bug variants" and "CodeQL/Semgrep". The clause "analyzing security vulnerabilities" is broad and could overlap with a general security-audit skill, which is a minor overlap risk keeping it at 4 rather than the minimal-conflict 5 anchor.

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

relative_links

Relative link issues: 1 possibly missing (METHODOLOGY.md)

Warning

Total

15

/

16

Passed

Repository

BigSimmo/PsychSift

Path

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