agentleFS
ulises-jeremiasulises-jeremias/agent-toolkit/skills/integrations/jira-assistant/SKILL.md

jira-assistant

Skill19 starsChanged 2 months agoMITView on GitHub

Jira Cloud, Jira Software and Jira Service Management automation through the jira-as CLI

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start every task with jira-as help: the surface map, groups, topics, auth and sandbox modes.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “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

Requires jira-as>=2,<3. This file is deliberately thin: the CLI's own help is the source of truth and this skill never restates it.

  1. Start every task with jira-as help: the surface map, groups, topics, auth and sandbox modes.
  2. Find an operation with jira-as api search WORDS, read it with jira-as api describe OPERATION [--full|--examples], run it with jira-as api call OPERATION ...; jira-as api topics lists the deep-dive topics.
  3. For a known group, jira-as help GROUP; for a gotcha (adf, paging, search, scope, risk, auth, migration, ...), jira-as help TOPIC. Old 1.x verbs: jira-as help migration.
  4. Discovery needs no credentials; calls need JIRA_SITE_URL, JIRA_EMAIL and JIRA_API_TOKEN or existing settings. Risk-tagged calls preview by default; --confirm sends. Add --format json for machine-readable output.

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.