agentleFS
itseffiitseffi/agentic-os/.agents/skills/atlassian-jira-sync/SKILL.md

atlassian-jira-sync

Skill114 starsChanged 10 months agoMITView on GitHub

Sync Jira issues with local tasks. Use during daily planning or when user asks about Jira issues.

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check Jira for assigned issues and sync with local task management.

    line 8
  2. Very specific:

    Call jira_search with JQL:

    line 14
  3. Very specific:

    Check Tasks/ for existing files with Jira references:

    line 21
  4. Very specific:

    Look for jira_key in YAML frontmatter

    line 22
  5. Very specific:

    Keep jira_key in frontmatter for bidirectional sync

    line 88
  6. Distinctive:

    Update Jira status when local task completes

    line 89
  7. Distinctive:

    Use this skill when the task directly matches the workflow described above.

    line 94
  8. Distinctive:

    Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Jira Issue Sync

Check Jira for assigned issues and sync with local task management.

Instructions

Step 1: Fetch Assigned Issues

Call jira_search with JQL:

assignee = currentUser() AND status != Done ORDER BY priority DESC

Step 2: Compare with Local Tasks

Check Tasks/ for existing files with Jira references:

  • Look for jira_key in YAML frontmatter
  • Identify new issues not yet in Tasks/

Step 3: Present Summary

Jira 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?

Step 4: Sync Options

OptionDescription
Create allAdd all new issues as local tasks
Select specificChoose which to sync
SkipContinue without syncing

Step 5: Create Local Tasks

For each issue to sync, create task file:

---
title: [Issue summary]
category: technical
priority: [Map from Jira priority]
status: n
jira_key: PROJ-XXX
---

Priority Mapping

JiraPersonal OS
BlockerP0
CriticalP0
HighP1
MediumP2
LowP3

Example Flow

User: "What should I work on today?"

Agent:

  1. Fetches Jira issues
  2. Compares with local tasks
  3. "You have 5 Jira tickets..."
  4. Offers to create local tasks
  5. Continues with planning

Notes

  • Keep jira_key in frontmatter for bidirectional sync
  • Update Jira status when local task completes
  • Include Jira link in task context section

When to Use

Use this skill when the task directly matches the workflow described above.

When Not to Use

Do not use this skill when the request is unrelated, low-stakes, or better handled by a simpler direct response.

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.