CtrlK
BlogDocsLog inGet started
Tessl Logo

snyk-fix

Complete security remediation workflow. Scans code for vulnerabilities using Snyk, fixes them, validates the fix, and optionally creates a PR. Supports both single-issue and batch mode for multiple vulnerabilities. Use this skill when: - User asks to fix security vulnerabilities - User mentions "snyk fix", "security fix", or "remediate vulnerabilities" - User wants to fix a specific CVE, Snyk ID, or vulnerability type (XSS, SQL injection, path traversal, etc.) - User wants to upgrade a vulnerable dependency - User asks to "fix all" vulnerabilities or "fix all high/critical" issues (batch mode)

72

Quality

90%

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

85%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 highly actionable, clearly sequenced remediation workflow with strong validation and feedback loops. Its main weakness is structure: a long single-file document that keeps reference material inline instead of progressively disclosing it via bundle files.

Suggestions

Split the lengthy reference material — the snyk_send_feedback field schemas (Steps 6.2/6B.2), the Full Advisory template (Phase 4a), and the breakability decision tree (Step 4.2) — into a references/ file and link to it from SKILL.md to reduce the inline wall of text.

Dedupe the feedback field documentation shared between single (6.2) and batch (6B.2) modes into one reference, noting only the batch-specific differences inline.

Collapse the Constraints and Completion Checklist sections, which largely restate the phase steps, into a single concise checklist to trim redundancy.

DimensionReasoningScore

Conciseness

The body is dense procedural guidance without basic-concept over-explanation, but feedback field docs repeat across Steps 6.2/6B.2 and the Constraints/Completion Checklist sections restate earlier phases, leaving minor trimmable redundancy.

4 / 5

Actionability

It provides concrete MCP tool calls with parameter examples, copy-paste-ready git/gh commands, and exact feedback-call and report templates covering the common single and batch cases.

5 / 5

Workflow Clarity

Phases are explicitly sequenced with validation checkpoints (Phase 5 re-scan, Step 4.2 breakability gate before apply, tests/lint), feedback loops (max attempts, fix→revalidate), rollback triggers, and completion checklists — exactly what a destructive/batch skill requires.

5 / 5

Progressive Disclosure

The file has good internal phase structure, but it is a monolithic ~550-line document with no bundle files, and reference-style material (feedback schema, advisory template, breakability decision tree) is inlined rather than split into separate reference files.

3 / 5

Total

17

/

20

Passed

Description

96%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, well-structured description that names concrete actions, comprehensive natural trigger terms, and explicitly answers both what and when. Its only soft spot is a single broad trigger that could overlap with a generic security-remediation skill.

DimensionReasoningScore

Specificity

"Scans code for vulnerabilities using Snyk, fixes them, validates the fix, and optionally creates a PR" lists multiple concrete actions plus single/batch modes, giving comprehensive coverage of the workflow.

5 / 5

Completeness

It explicitly answers both what (scan, fix, validate, PR; single + batch) and when, via a "Use this skill when:" block with concrete trigger bullets.

5 / 5

Trigger Term Quality

Covers natural terms comprehensively, including synonyms ("snyk fix", "security fix", "remediate vulnerabilities"), ID prefixes (CVE, Snyk ID), vuln types (XSS, SQL injection, path traversal), and batch phrases ("fix all", "fix all high/critical").

5 / 5

Distinctiveness Conflict Risk

The Snyk-specific framing and CVE/Snyk-ID triggers carve a clear niche, but the generic trigger "User asks to fix security vulnerabilities" carries minor overlap risk with a non-Snyk security skill, keeping it just below 5.

4 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (556 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
snyk/studio-recipes
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.