CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-security-hotfix

Handle security bugs — data exposure, auth or payment bypass, SSRF, XSS, CSRF, open redirects, secrets, missing rate limits — with contain-first steps, server-side fixes using shared guards, bypass-variant sweeps, exploitation log review, and minimal disclosure. Use for any P0/P1 security finding.

75

Quality

94%

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

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.

A tight, well-sequenced runbook for security hotfixes: contain, fix with named shared guards, sweep bypass variants, review logs, manage secrets and disclosure, and hold containment until verified. Its only weakness is the absence of even a one-line code example for the shared guards it names.

DimensionReasoningScore

Conciseness

The 19-line body is lean and assumes Claude's competence: no concepts are explained, no filler, and every line instructs an action or a checkpoint. It matches the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete, specific guidance throughout — named shared guards ('safePath', 'parsePublicUrl' + DNS re-check at fetch time, CSRF tokens or SameSite, rate limiter on public and AI-cost endpoints, secure cookie flags) — but no executable snippet showing guard usage, leaving minor gaps for a code-adjacent workflow.

4 / 5

Workflow Clarity

A clear 7-step sequence with explicit validation checkpoints ('keep containment until VERIFIED and deployed', 'the fix VERIFIED with bypass variants', log review with counts) plus an Exit criteria checklist that serves as a completion gate.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references; well-organized sections (Procedure, Exit criteria) and clearly signaled skill cross-references ('fix-class-sweep', 'qa-security-web') satisfy the simple-skill exception for a full score.

5 / 5

Total

19

/

20

Passed

Description

92%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 combines a comprehensive enumeration of security bug classes with the concrete remediation workflow (contain, fix, sweep, log review, disclosure) and an explicit 'Use for any P0/P1 security finding' trigger. Third-person voice is used throughout and there is no padding.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('contain-first steps, server-side fixes using shared guards, bypass-variant sweeps, exploitation log review, and minimal disclosure') plus a comprehensive enumeration of bug classes (data exposure, auth/payment bypass, SSRF, XSS, CSRF, open redirects, secrets, missing rate limits).

5 / 5

Completeness

It explicitly answers both what ('Handle security bugs — ... with contain-first steps, server-side fixes ... minimal disclosure') and when ('Use for any P0/P1 security finding') with concrete trigger phrasing, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural trigger terms like 'SSRF', 'XSS', 'CSRF', 'open redirects', 'secrets', and 'P0/P1 security finding' are present, but common synonyms users would say such as 'vulnerability', 'breach', or 'leaked credentials' are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (security hotfix handling) with distinct triggers (named vulnerability classes, P0/P1 framing) makes it unlikely to fire for the wrong skill.

5 / 5

Total

19

/

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

itsablabla/qa-bug-agent-skills

Path

skills/fix-security-hotfix/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.