Skillzwave Logo
Skillzwave

jira

1 stars 1 forks
82
B

Manages JIRA issues, projects, and workflows using Atlassian MCP. Use when asked to "create JIRA ticket", "search JIRA", "update JIRA issue", "transition issue", "sprint planning", or "epic management".

#claude-code-skill#agentic-skill#JQL#issue#JIRA Management#Project#Manages JIRA#JIRA issues

Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security

Installation for Agentic Skill

View all platforms →
skilz install SpillwaveSolutions/jira/jira
skilz install SpillwaveSolutions/jira/jira --agent opencode
skilz install SpillwaveSolutions/jira/jira --agent codex
skilz install SpillwaveSolutions/jira/jira --agent gemini

First time? Install Skilz: pip install skilz

Works with 22+ AI coding assistants

Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...

View All Agents
Download Agent Skill ZIP

Extract and copy to ~/.claude/skills/ then restart Claude Desktop

1. Clone the repository:
git clone https://github.com/SpillwaveSolutions/jira
2. Copy the agent skill directory:
cp -r jira ~/.claude/skills/
View on GitHub

Need detailed installation help? Check our platform-specific guides:

Claude Desktop Guide Claude Code Guide Troubleshooting

Related Agentic Skills

automating-mail

by SpillwaveSolutions

Automates Apple Mail via JXA with AppleScript dictionary discovery. Use when asked to "automate email", "send mail via script", "JXA Mail automatio...

100
Marketplace

automating-reminders

by SpillwaveSolutions

Automates Apple Reminders using JavaScript for Automation (JXA). Use when asked to "create reminders programmatically", "automate reminder lists", ...

100
Marketplace

mastering-postgresql

by SpillwaveSolutions

PostgreSQL development for Python with full-text search (tsvector, tsquery, BM25 via pg_search), vector similarity (pgvector with HNSW/IVFFlat), JS...

100
Marketplace

automating-contacts

by SpillwaveSolutions

Automates macOS Contacts via JXA with AppleScript dictionary discovery. Use when asked to "automate contacts", "JXA contacts automation", "macOS ad...

99
Marketplace

Agentic Skill Details

Owner
SpillwaveSolutions (GitHub)
Repository
jira
Stars
1
Forks
1
Type
Other
Meta-Domain
Primary Domain
Market Score
82
Agentic Skill Grades →

Agent Skill Grade

B
Score: 82/100 Click to see breakdown

Score Breakdown

Spec Compliance
13/15
PDA Architecture
22/30
Ease of Use
21/25
Writing Style
7/10
Utility
17/20
Modifiers: +2

Areas to Improve

  • Marketing language in overview
  • Missing TOC in custom_field_discovery.md
  • JQL guide is oversized

Recommendations

  • Add trigger phrases to description for discoverability
  • Add table of contents for files over 100 lines

Graded: 2026-01-19

Developer Feedback

I took a look at your jira skill and wanted to share some thoughts.

Links:

The TL;DR

You're at 82/100, solid B-grade territory. This is graded against Anthropic's skill best practices. Your strongest area is Spec Compliance (13/15) — the YAML frontmatter and trigger phrases are clean. Weakest pull is Writing Style (7/10) — some marketing speak creeping in where you need pure instruction, and a few voice consistency issues.

What's Working Well

  • Trigger phrase coverage is excellent. You've nailed the discovery side with specific phrases like "create JIRA ticket," "search JIRA," "sprint planning." That's exactly what makes skills discoverable.
  • Reference architecture is thoughtfully layered. The hub-and-spoke pattern (382-line SKILL.md + two references) is the right call. You're delegating weight appropriately instead of bloating the main file.
  • Custom field discovery methodology is genuinely useful. This isn't just JIRA documentation — it's solving a real problem that teams actually hit. The workflow-based approach to discovering custom fields is the kind of thing that makes a skill valuable beyond obvious use cases.
  • Issue templates in JSON are practical. Having 10 templated examples gives people concrete starting points instead of forcing them to figure out field structure from scratch.

The Big One: Architecture Inefficiency

Your jql_guide.md is oversized at 1323 lines — that's too much weight in a single reference file. This hurts your Progressive Disclosure score (22/30) because it forces users to parse a monolithic chunk instead of navigating focused sub-documents.

The fix: Split it into topic-specific guides:

  • jql_basics.md — Simple queries, AND/OR operators
  • jql_sprints_epics.md — Sprint/epic-specific qu...

AI-Detected Topics

Extracted using NLP analysis

claude-code-skill agentic-skill JQL issue JIRA Management Project Manages JIRA JIRA issues issues custom field

Report Security Issue

Found a security vulnerability in this agent skill?