New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Snyk Triage

by epam in epam/ai-dial-chat

Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSEPOSITIVE / NEEDSREVIEW / DUPLICATE / NOTAPPLICABLE).

Apache-2.0Auto-check passedSecurity

Install Snyk Triage

skills CLI
$ npx skills add epam/ai-dial-chat --skill snyk-triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install epam/ai-dial-chat snyk-triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/epam/ai-dial-chat.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/snyk-triage .claude/skills/snyk-triage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
snyk-triage
GitHub stars
504
Token cost
~1.2k tokens
SKILL.md length
560 words
Files
2
Skills in repo
18
Repo updated
First seen
Licence
Apache-2.0

At a glance

Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSEPOSITIVE / NEEDSREVIEW / DUPLICATE / NOTAPPLICABLE).

  • Works in 7 steps: Parse the rule/class, the sink… → Locate the code: open the files[]… → Sink — confirm the dangerous operation… → …
  • Jira-exported scanner report is provided
  • SKILL.md covers Input, Per-finding workflow, Verdicts (one per finding) and Anti-hallucination (hard rules), plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Snyk Triage is an agent skill from epam/ai-dial-chat. Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSEPOSITIVE / NEEDSREVIEW / DUPLICATE / NOTAPPLICABLE). Use when a Snyk or Jira-exported scanner report is provided.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `SKILL.full.md`).

It sits in Security, covering Static analysis and SAST. It works with Snyk and Jira. The repository describes itself as: A default UI for AI DIAL. The licence is Apache-2.0.

When your agent uses it

  • Jira-exported scanner report is provided
  • Tasks that involve Static analysis and SAST

Example prompts

  • “/snyk-triage”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Parse the rule/class, the sink file+line, and the reported code line.
  2. Locate the code: open the files[] path(s). If missing, Glob/Grep by
  3. Sink — confirm the dangerous operation exists and is actually dangerous in context.
  4. Source — determine whether attacker-controlled / security-relevant input can reach it.
  5. Reachability & mitigations — is the path reachable in production? Look near the
  6. Production relevance — test/mock/demo/fixture/docs-only code is NOT_APPLICABLE
  7. Verdict — pick exactly one (below), citing concrete file:line evidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 3455656. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Snyk Triage loads about 1.2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 560 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from epam/ai-dial-chat at commit 3455656, republished under its Apache-2.0 licence (© epam). 560 words, ~1,162 tokens.

Download SKILL.mdSave it as .claude/skills/snyk-triage/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
snyk-triage
description
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.

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:

  1. Parse the rule/class, the sink file+line, and the reported code line.
  2. Locate the code: open the files[] path(s). If missing, Glob/Grep by filename, symbol, or the reported code snippet. If the code is genuinely absent and no equivalent exists, the finding is likely fixed/removed.
  3. Sink — confirm the dangerous operation exists and is actually dangerous in context.
  4. Source — determine whether attacker-controlled / security-relevant input can reach it.
  5. 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.
  6. Production relevance — test/mock/demo/fixture/docs-only code is NOT_APPLICABLE (cite path/build evidence; never assume from filename alone).
  7. Verdict — pick exactly one (below), citing concrete file:line evidence.
Show full SKILL.md (268 more words)Show less

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 (info for 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").

© epam, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .claude/skills/snyk-triage of epam/ai-dial-chat.

  • SKILL.md
  • SKILL.full.md

Open the folder on GitHubat commit 3455656

Compare with similar skills

Snyk Triage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Snyk Triage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Snyk Triage this skillepam/ai-dial-chat504—~1.2kAutomated safety check: PassApache-2.0
Managing Vulnerabilitiesancoleman/ai-design-components525—~3.8kAutomated safety check: PassMIT
Triaging Security Findingsbitwarden/ai-plugins155—~2.2kAutomated safety check: PassCustom licence
Security Scanbagofwords1/bagofwords459—~1.7kAutomated safety check: PassCustom licence
Semgrepvigolium/piolium1401 repos~2.4kAutomated safety check: NotesMIT
C To AstNarwhal-Lab/MagicSkills316—~1.1kAutomated safety check: PassMIT

Similar skills

  • Managing Vulnerabilities

    ancoleman/ai-design-components

    Implementing multi-layer security scanning (container, SAST, DAST, SCA, secrets), SBOM generation, and risk-based vulnerability prioritization in CI/CD pipelines.

    525 GitHub stars~3.8k tokensUpdated 10 mo ago
    SecurityAuto-check passed

  • Triaging Security Findings

    bitwarden/ai-plugins

    Official

    This skill should be used when the user asks to "triage security findings", "fix an Aikido finding", "review Aikido issues", "dismiss a false positive", "check SAST/IaC alerts", or needs to work…

    155 GitHub stars~2.2k tokensUpdated yesterday
    SecurityAuto-check passed

  • Security Scan

    bagofwords1/bagofwords

    Run a Snyk security scan of the repo (frontend npm deps, backend pip deps, Dockerfile/base image, and Snyk Code SAST), triage findings, and remediate the real ones with verified fixes.

    459 GitHub stars~1.7k tokensUpdated today
    SecurityAuto-check passed

  • Semgrep

    vigolium/piolium

    Run Semgrep static analysis scan on a codebase using parallel subagents.

    140 GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check: notes

  • C To Ast

    Narwhal-Lab/MagicSkills

    Parse C source code into an Abstract Syntax Tree (AST). An agent skill from Narwhal-Lab/MagicSkills.

    316 GitHub stars~1.1k tokensUpdated 6 mo ago
    SecurityAuto-check passed

  • Semgrep Security Scan

    trailofbits/skills

    Official

    Detects languages, proposes rulesets for approval, then runs the approved Semgrep scan across a codebase and merges the output into one SARIF file.

    7.5k GitHub stars~3.7k tokensUpdated yesterday
    SecurityAuto-check: notes

More from epam/ai-dial-chat

All 18 skills in this repo

  • Refactoring Audit

    epam/ai-dial-chat

    Deep codebase refactoring audit for AI DIAL Chat. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Address Current Branch Review

    epam/ai-dial-chat

    Read unresolved GitHub code review threads for the pull request associated with the current branch, classify each comment, and implement and verify required code fixes.

    504 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

  • Create Ticket

    epam/ai-dial-chat

    Interactively create OR update GitHub issues (Bug, Feature, Task) for the current repository.

    504 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Dep Scan

    epam/ai-dial-chat

    Runs Trivy filesystem scan against the repo root and emits structured vulnerability findings (CVE, package, versions) in the SDLC reviewer schema.

    504 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Figma

    epam/ai-dial-chat

    Design-to-code workflow for Figma designs. An agent skill from epam/ai-dial-chat.

    504 GitHub stars~997 tokensUpdated today
    Auto-check passed

  • Git Ship

    epam/ai-dial-chat

    A skill your agent uses whenever the user wants to commit, push, or ship changes in a git repository.

    504 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Snyk Triage

What does Snyk Triage do?

Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSEPOSITIVE / NEEDSREVIEW / DUPLICATE / NOTAPPLICABLE). Snyk Triage is an agent skill from epam/ai-dial-chat. Validate Snyk SAST / Code findings against repo evidence; emits per-finding verdicts (CONFIRMED / FALSEPOSITIVE / NEEDSREVIEW / DUPLICATE / NOTAPPLICABLE).

When should I use Snyk Triage?

Snyk Triage fits situations like: jira-exported scanner report is provided; tasks that involve Static analysis and SAST.

How do I install Snyk Triage in Claude Code?

Run `npx skills add epam/ai-dial-chat --skill snyk-triage -a claude-code`. Or copy the skill folder (.claude/skills/snyk-triage in epam/ai-dial-chat) into .claude/skills/snyk-triage in your project. Claude Code loads it when a task matches its description.

How do I install Snyk Triage in Codex?

Run `npx skills add epam/ai-dial-chat --skill snyk-triage -a codex`. Or copy the skill folder (.claude/skills/snyk-triage in epam/ai-dial-chat) into .agents/skills/snyk-triage in your project. Codex loads it when a task matches its description.

Can I use Snyk Triage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/ai-dial-chat --skill snyk-triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/snyk-triage, .gemini/skills/snyk-triage, .github/skills/snyk-triage and .opencode/skills/snyk-triage in your project.

What does Snyk Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Snyk Triage is instructions for the agent only.

Does Snyk Triage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Snyk Triage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Snyk Triage use?

Snyk Triage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Snyk Triage use?

About 1.2k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Snyk Triage?

Skills that share tags, products or a category with Snyk Triage: Managing Vulnerabilities (ancoleman/ai-design-components, 525 stars), Triaging Security Findings (bitwarden/ai-plugins, 155 stars), Security Scan (bagofwords1/bagofwords, 459 stars) and Semgrep (vigolium/piolium, 140 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Snyk Triage?

epam (a GitHub organization) maintains it in epam/ai-dial-chat, which has 504 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 9, 2026.

Source: epam/ai-dial-chat on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.