snyk-jira-ingest
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.
Source facts
- Repository
- epam/ai-dial-chat
- Last source activity
- August 31, 2026 at 16:03
- Detected SKILL.md language
- English
- Stars
- 505
- Forks
- 62
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
File Explorer
2 filesShowing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- snyk-jira-ingest
- disable-model-invocation
- true
- description
- 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.
# 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.
View on GitHub