agentleFS
epamepam/ai-dial-chat/.claude/skills/snyk-jira-ingest/SKILL.md

snyk-jira-ingest

Skill501 starsChanged 18 days agoApache-2.0View on GitHub

Pull REAL Snyk SAST findings from EPAM Jira (Data Center) via the search-export API using a Personal Access Token, and emit them as a stage-output.json artifact for a downstream triage stage. Use when you want the actual Jira-tracked Snyk findings (the same set a human gets by clicking Export on the security filter) rather than a synthetic fixture.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is 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.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read stage-output.json to confirm it exists.

    line 22
  2. Distinctive:

    Only: if the script is denied or errors before that file exists: write a failed result naming what went wrong.

    line 25

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Snyk → Jira Ingest

Pull the real Snyk SAST findings tracked in EPAM Jira for the downstream triage stage. All the work — fetch, filter to this repo, cap, and writing a schema-valid stage-output.json — is done by the committed script fetch.sh; you only run it and confirm the result. (Config and behaviour are documented in that script.)

Procedure

  1. Run the script:

    bash .claude/skills/snyk-jira-ingest/fetch.sh
  2. Read stage-output.json to confirm it exists. The script already wrote a valid envelope — do not overwrite it. Then finish.
  3. Only if the script is denied or errors before that file exists: write a failed result naming what went wrong. Never fabricate findings or a synthetic export.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.