jira-communication-2d4eef — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited jira-communication-2d4eef (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 support --help, --json, --quiet, --debug.
On Jira URL or issue key (PROJ-123) → run jira-issue.py get. Auth issues → jira-setup.py.
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
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.pngjira-syntax: For descriptions/comments. Jira uses wiki markup, not Markdown.
references/jql-quick-reference.md — when JQL goes beyond simple filtersreferences/jql-cookbook.md — when translating natural-language requests into JQLreferences/multi-profile.md — when using multiple Jira instances or --profilereferences/troubleshooting.md — when hitting auth, SSL, 401, 403, or connection failuresreferences/issue-editing.md — when using --fields-json, reporter changes, deletes, or movesreferences/creation.md — when creating with --parent, reporter, components, or custom fieldsreferences/comments.md — when editing, deleting, or listing commentsreferences/worklog.md — when using --started, date ranges, or jira-worklog-query.pyreferences/attachments.md — when uploading, downloading, or inspecting attachmentsreferences/links.md — when working with issue or web linksreferences/agile.md — when working with sprints, boards, or board --namereferences/fields-and-users.md — when looking up custom field IDs, users, or issue typesreferences/watchers.md — when the user asks to watch, subscribe, notify on, or list watchers of an issuereferences/versions.md — when the user asks about fix/affects versions, releases, or version CRUDCloud: 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.