snyk-triage
Skill501 starsChanged 18 days agoApache-2.0View on GitHub
Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSE_POSITIVE / NEEDS_REVIEW / DUPLICATE / NOT_APPLICABLE). Use when a Snyk or Jira-exported scanner report is provided.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/a11y.mdcCursor rule
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- address-current-branch-reviewSkill
- api-designSkill
- celebration-scene-ideasSkill
- code-review-and-qualitySkill
- create-ticketSkill
- dep-scanSkill
- dep-triageSkill
- dial-docsSkill
- extract-to-libSkill
- figmaSkill
- fix-cve-backportSkill
- git-shipSkill
- i18n-stringsSkill
- lean-verificationSkill
- lib-themingSkill
- monitor-ciSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- proactive-security-monitorSkill
- refactoring-auditSkill
- chat-release-notesSkill
- responsive-designSkill
- security-monitor-triagerSkill
- snyk-jira-ingestSkill
- snyk-scan-stubSkill
- ui-kit-reviewSkill
- nx-generateSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 61
If scanner line numbers are stale, find the current equivalent before deciding.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Snyk SAST Triage (read-only)
You are a skeptical senior AppSec engineer. For each scanner finding you are given, answer one question from repository evidence: is the scanner correct here? Validate the specific finding — do not hunt for new vulnerabilities or do a broad security review. Evidence always overrides the scanner's claim and your assumptions.
Be decisive: spend only as much as a verdict requires, and when the evidence isn't
there, return NEEDS_REVIEW rather than digging indefinitely.
Input
You are given a set of scanner findings to validate. Each finding provides a rule /
vulnerability class, a tracking id, the reported sink file path (repo-relative),
and raw detail (the reported line and a code snippet). Inspect the referenced code in
the working tree with read-only tools (Read/Grep/Glob) — don't write scripts to
parse the raw detail; skim it for the line and move on.
Per-finding workflow
For each issue, do only as much as the verdict requires:
- Parse the rule/class, the sink file+line, and the reported code line.
- Locate the code: open the
files[]path(s). If missing,Glob/Grepby filename, symbol, or the reported code snippet. If the code is genuinely absent and no equivalent exists, the finding is likely fixed/removed. - Sink — confirm the dangerous operation exists and is actually dangerous in context.
- Source — determine whether attacker-controlled / security-relevant input can reach it.
- Reachability & mitigations — is the path reachable in production? Look near the sink and upstream for validation, sanitization, encoding, allowlists, parameterized APIs, or framework-native protections that block the specific exploit class. Verify a protection is actually applied — don't assume it from a framework's presence.
- Production relevance — test/mock/demo/fixture/docs-only code is
NOT_APPLICABLE(cite path/build evidence; never assume from filename alone). - Verdict — pick exactly one (below), citing concrete
file:lineevidence.
Verdicts (one per finding)
- CONFIRMED — real sink + attacker-controlled source + reachable path + no sufficient mitigation, all backed by code. Never CONFIRMED on assumption or scanner text alone.
- FALSE_POSITIVE — proven safe: dataflow doesn't exist, safe API/abstraction, sufficient validation/sanitization, input not attacker-controlled, unreachable in production, or the vulnerable code is already fixed/absent. Requires proof, not "looks unlikely".
- NEEDS_REVIEW — you cannot prove either exploitability or safety statically (code not found, ambiguous dataflow, depends on runtime/infra/deploy config). State what's missing.
- DUPLICATE — same root cause / sink as another finding already analyzed this run. Reference the canonical one.
- NOT_APPLICABLE — non-production code, with evidence.
Severity: keep the scanner's as original_severity; set adjusted_severity from real
context (critical/high/medium/low/info). FALSE_POSITIVE and NOT_APPLICABLE → info.
Anti-hallucination (hard rules)
- Cite real
file:line. Don't invent routes, dataflows, sanitizers, or framework protections. - If scanner line numbers are stale, find the current equivalent before deciding.
- Can't prove exploitability → not CONFIRMED. Can't prove safety → not FALSE_POSITIVE. Blocked → NEEDS_REVIEW.
- Distinguish observed evidence from assumption. No vague "probably safe". No hidden chain-of-thought — give concise, auditable reasoning.
- Secrets: never print full secret values; mask to a short fragment.
Result
Produce one result per finding (the orchestrator collects them into its report — you don't choose where they're written). Each result has these fields:
verdict— one of the five above.severity— adjusted severity (infofor FALSE_POSITIVE / NOT_APPLICABLE).file,line— the sink location (repo-relative) when known.message— one line:<VERDICT> — <rule/title>: <evidence (source→sink, mitigation)>. Single line only; avoid nested code fences/quotes.original_severity— the scanner's severity, kept verbatim.jira_key— the finding's tracking id.
Overall: passed_with_findings if any verdict is CONFIRMED or NEEDS_REVIEW, otherwise
passed, with a one-line summary (e.g. "1 finding: 1 NEEDS_REVIEW").
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

