atlassian-jira-sync — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited atlassian-jira-sync (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.
Check Jira for assigned issues and sync with local task management.
Call jira_search with JQL:
assignee = currentUser() AND status != Done ORDER BY priority DESCCheck Tasks/ for existing files with Jira references:
jira_key in YAML frontmatterJira Issues (8 active):
**Blockers/Critical**
- PROJ-123: Production bug in auth [In Progress]
**High Priority**
- PROJ-124: API rate limiting [To Do]
- PROJ-125: Update deployment docs [In Review]
**Normal**
- PROJ-126: Refactor logging [Backlog]
3 issues not yet in local Tasks. Create them?| Option | Description |
|---|---|
| Create all | Add all new issues as local tasks |
| Select specific | Choose which to sync |
| Skip | Continue without syncing |
For each issue to sync, create task file:
---
title: [Issue summary]
category: technical
priority: [Map from Jira priority]
status: n
jira_key: PROJ-XXX
---| Jira | Personal OS |
|---|---|
| Blocker | P0 |
| Critical | P0 |
| High | P1 |
| Medium | P2 |
| Low | P3 |
User: "What should I work on today?"
Agent:
jira_key in frontmatter for bidirectional syncUse this skill when the task directly matches the workflow described above.
Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.