agentleFS
Sign inStart free
zazzcodezazzcode/zazz-skills/.agents/skills/jira/SKILL.md

jira

Skill4 starsChanged 4 months agoMITView on GitHub

Draft only, not yet implemented. Future companion utility skill for Jira-backed repos, intended to eventually fetch story details, acceptance criteria, links, and workflow metadata through an MCP or CLI interface.

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use meet, monday and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • kv0906Skill

    meet

    Process meeting notes into structured notes with extracted decisions, blockers, and action items. Use for "/meet project type title" then paste notes.

    Also in 3 projects that use this

  • er1chuSkill

    monday

    Full Monday morning setup. Creates week folder, pulls carry-forward, and generates briefing in one pass. Use on Monday mornings or when the user says "monday", "start my week", or "monday morning".

    Also in 3 projects that use this

  • refly-aiSkill

    hubspot

    Integrate with HubSpot for CRM management. Use when you need to: (1) manage contacts and deals, (2) track sales pipelines, or (3) automate marketing and CRM workflows.

    Also in 4 projects that use this

  • koderoverSkill

    jenkins

    Jenkins CI/CD 操作。用于：(1) 触发 Jenkins 任务构建 (2) 查询任务状态和构建历史 (3) 获取构建日志 (4) 操作 Jenkins 节点和配置

    Also in 3 projects that use this

  • SentrySkill

    datadog

    Query live Datadog telemetry (logs, metrics, traces, spans, monitors, incidents, dashboards, services, hosts) through Datadog's Pup CLI. Use when users ask to investigate production behavior in Datadog, including searching logs, checking monitor status, inspecting traces or spans, looking up incidents, finding services, or correlating metrics. Do not use it for Sentry issues, repository/source-code work, or ticketing.

    Also in 3 projects that use this

  • refly-aiSkill

    asana

    Integrate with Asana for task management. Use when you need to: (1) create and manage Asana tasks, (2) organize project work, or (3) automate team task tracking workflows.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 17 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 56 edited versions we read keep these.

  • 17

    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. Distinctive:

    Do not present this skill as live Jira connectivity.

    line 13
  2. Distinctive:

    Do not claim that Jira lookups, ticket sync, or issue validation have actually occurred through this skill.

    line 14
  3. Distinctive:

    If a task needs Jira context today:

    line 16
  4. Distinctive:

    Use AGENTS.md as the source of truth for repo-specific settings such as tracking system, project-code conventions, and Jira workflow rules.

    line 18
  5. Distinctive:

    Ask the user for the Jira issue key, URL, acceptance criteria, or related story details when they are not already available in repo docs.

    line 19
  6. Distinctive:

    Use the user-provided or repo-provided Jira information as context for specification, QA, PR drafting, or execution.

    line 20
  7. Distinctive:

    Treat this skill as a roadmap marker, not an executable integration.

    line 58
  8. Distinctive:

    Do not invent Jira endpoints, auth flows, or commands.

    line 59
  9. Distinctive:

    Do not imply that Jira data can be fetched automatically through this skill yet.

    line 60
  10. Distinctive:

    If a repo uses Jira, ask the user for the authoritative Jira reference when it is required and unavailable.

    line 61
  11. Very specific:

    If an automation-driven agent such as an agent running qa-testing needs Jira context, use repo guidance plus user-provided Jira details as …

    line 62
  12. Distinctive:

    If repo conventions later define a real Jira integration path, update this skill and any related skill extensions to match that …

    line 63
  13. Distinctive:

    When this skill is implemented, it should likely follow the same broad methodology pattern as other companion utility skills:

    line 67
  14. Distinctive:

    Use repo guidance first, with AGENTS.md as the source of truth for repo-specific settings.

    line 69
  15. Distinctive:

    Use a stable agent-facing interface rather than embedding ad hoc HTTP requests in every skill.

    line 71
  16. Distinctive:

    no live Jira behavior

    line 78
  17. Distinctive:

    no required environment variables yet

    line 81
  18. Distinctive:

    no guarantee of future field names or route shapes

    line 82

“Common” is measured: kept by at least 6 in 10 of the 56 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 Skill

Draft Status

This skill is a draft placeholder for the methodology. It is not implemented yet.

Do not present this skill as live Jira connectivity. Do not claim that Jira lookups, ticket sync, or issue validation have actually occurred through this skill.

If a task needs Jira context today:

  1. Use AGENTS.md as the source of truth for repo-specific settings such as tracking system, project-code conventions, and Jira workflow rules. Read it if that context is not already available, along with any skill extension that declares Jira conventions.
  2. Ask the user for the Jira issue key, URL, acceptance criteria, or related story details when they are not already available in repo docs.
  3. Use the user-provided or repo-provided Jira information as context for specification, QA, PR drafting, or execution.
  4. Clearly distinguish provided facts from anything still missing.

Operating Modes

This draft skill is intended for two future usage patterns:

  1. Interactive support for a human-in-the-loop agent that needs Jira context during specification, QA review, PR drafting, or execution.
  2. Companion utility support for automation-driven agents, including an agent running the qa-testing skill, that need authoritative Jira issue context to validate acceptance criteria, confirm scope, or anchor reviewer evidence.

Today, both modes still rely on repo guidance and user-provided Jira context because live integration is not implemented yet. The important distinction is that this skill is not only for conversational lookup. It is also meant to inform downstream agents such as an agent running qa-testing, pr-builder, spec-builder, or pr-review.

Intended Future Role

This skill is expected to become the Jira counterpart to zazz-board for repos that use Jira as the authoritative issue-management system.

Future responsibilities may include:

  • fetching Jira issue summaries, descriptions, and acceptance criteria
  • retrieving issue URLs, statuses, assignees, and workflow metadata
  • resolving related parent/child issue context when specification or review depends on it
  • providing authoritative PR-facing Jira references for skills such as pr-builder
  • helping spec-builder, pr-builder, pr-review, and an agent running qa-testing validate that work remains aligned with the governing Jira issue
  • informing automation-driven QA-agent flows with authoritative Jira acceptance criteria and issue metadata

Intended Interface Direction

The methodology expects this to be implemented later through one of these approaches:

  • an MCP-backed Jira integration
  • a CLI-first adapter that agents can call consistently

The final implementation path is not decided in this draft. Until that exists, this skill is documentation-only.

Usage Rules For Now

  • Treat this skill as a roadmap marker, not an executable integration.
  • Do not invent Jira endpoints, auth flows, or commands.
  • Do not imply that Jira data can be fetched automatically through this skill yet.
  • If a repo uses Jira, ask the user for the authoritative Jira reference when it is required and unavailable.
  • If an automation-driven agent such as an agent running qa-testing needs Jira context, use repo guidance plus user-provided Jira details as the current fallback input.
  • If repo conventions later define a real Jira integration path, update this skill and any related skill extensions to match that implementation.

Future Integration Contract

When this skill is implemented, it should likely follow the same broad methodology pattern as other companion utility skills:

  1. Use repo guidance first, with AGENTS.md as the source of truth for repo-specific settings.
  2. Resolve project-specific Jira conventions and authentication source.
  3. Use a stable agent-facing interface rather than embedding ad hoc HTTP requests in every skill.
  4. Return authoritative issue context for downstream skills.
  5. Make it easy for other skills to distinguish verified Jira data from user-supplied fallback context.
  6. Support both interactive agent use and automation-driven companion use without changing the source-of-truth model.

Non-Goals In This Draft

  • no live Jira behavior
  • no bundled scripts
  • no auth instructions
  • no required environment variables yet
  • no guarantee of future field names or route shapes

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.

Check your setup, free