jira-communication-ec57ab — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited jira-communication-ec57ab (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
CLI scripts via uv run, all supporting --help, --json, --quiet, --debug.
On Jira URL or issue key (PROJ-123), pick by intent — each is one call:
| Intent | Tool |
|---|---|
| triage / work on ticket | jira-issue.py work KEY |
| start QA review | jira-issue.py qa KEY |
| QA-fail follow-up | jira-issue.py qa-fail KEY |
| field-only lookup | jira-issue.py get KEY --fields ... |
| change status | jira-issue.py act KEY → jira-transition.py do |
| audit / sibling discovery | jira-qa-gather.py KEY |
Auth issues → jira-setup.py. Anti-pattern: get + comment list on one key — use the matching verb. See references/intent-verbs.md.
Under ${CLAUDE_SKILL_DIR}/scripts/{core,workflow,utility}/.
Core: jira-issue.py, jira-search.py, jira-worklog.py, jira-attachment.py, jira-setup.py, jira-validate.py Workflow: jira-create.py, jira-transition.py, jira-comment.py, jira-move.py, jira-sprint.py, jira-board.py, jira-version.py Utility: jira-user.py, jira-fields.py, jira-link.py, jira-weblink.py, jira-worklog-query.py, jira-watchers.py, jira-qa-gather.py
Run directly. Scripts report ✓/✗. Destructive ops: --dry-run. Global flags before subcommand: jira-issue.py --json get PROJ-123.
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py get PROJ-123
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-search.py query "assignee = currentUser() AND status != Closed" -n 5 -f key,summary,status
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-issue.py update PROJ-123 --assignee me --priority Critical
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-comment.py add PROJ-123 "Comment text"
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-transition.py do PROJ-123 "In Progress"
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-worklog.py add PROJ-123 2h --comment "Work done"
uv run ${CLAUDE_SKILL_DIR}/scripts/workflow/jira-create.py issue PROJ "Summary" --type Task
uv run ${CLAUDE_SKILL_DIR}/scripts/core/jira-attachment.py add PROJ-123 screenshot.pngTerminal transitions: always pass--resolution <value>(e.g.Done,Won't do,Duplicate) or the resolution field stays empty and the ticket appears unresolved. Seereferences/intent-verbs.md.
jira-syntax: For descriptions/comments. Jira uses wiki markup, not Markdown.
references/jql-quick-reference.md, references/jql-cookbook.md — JQL beyond simple filtersreferences/multi-profile.md — multiple Jira instances, --profilereferences/troubleshooting.md — auth, SSL, 401, 403, connectionreferences/issue-editing.md — --description, --fields-json, reporter, deletes, movesreferences/creation.md — --parent, components, custom fieldsreferences/comments.md — edit, delete, list, markup lint / --forcereferences/worklog.md — --started, date ranges, jira-worklog-query.pyreferences/attachments.md — upload, download (cwd-only), inspectreferences/links.md — issue/web links, instance-specific link typesreferences/agile.md — sprints, boards, board --namereferences/fields-and-users.md — custom field IDs, users, issue typesreferences/watchers.md — watch, subscribe, list watchersreferences/versions.md — fix/affects versions, releases, version CRUDreferences/qa-gather.md — comprehensive audit bundle (siblings, prose URLs)references/intent-verbs.md — work / qa / qa-fail / act, exact transition namesCloud: JIRA_URL + JIRA_USERNAME + JIRA_API_TOKEN. Server/DC: JIRA_URL + JIRA_PERSONAL_TOKEN. Config via ~/.env.jira or ~/.jira/profiles.json.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.