create-jira-item

create-jira-item is a skill for Claude Code, Codex from paultyng/skill-issue. It costs 48 tokens per session (535 once invoked), scanned A, original, MIT.

A workflow for creating Jira work items such as stories, epics, initiatives, and tasks. Jira is a tool for tracking planned work, bugs, and larger projects.

In plain words
What is it for?
Use it to determine the project and item type, inspect custom fields, and create a correctly filled Jira issue.
Why use it?
It checks the selected Jira project's required fields and allowed values before creating an item. This avoids failed or incomplete tickets caused by organization-specific settings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to determine the project and item type, inspect custom fields, and create a correctly filled Jira issue.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/paultyng/skill-issue/create-jira-item
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add paultyng/skill-issue --skill create-jira-item
Clone the repo
git clone --depth 1 https://github.com/paultyng/skill-issue

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-jira-item

README.md
[![agentmods](https://agentmods.dev/badge/skills/paultyng/skill-issue/create-jira-item/github.svg)](https://agentmods.dev/skills/paultyng/skill-issue/create-jira-item)
Your own site
<a href="https://agentmods.dev/skills/paultyng/skill-issue/create-jira-item"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-jira-item/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-jira-item

Your own site · 80×15
<a href="https://agentmods.dev/skills/paultyng/skill-issue/create-jira-item"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/create-jira-item.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 535 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00535
Opus 5 $0.00024 $0.00267
Sonnet 5 $0.00010 $0.00107
Haiku 4.5 $0.00005 $0.00053

Measured 9d ago against content hash de414d49235d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

create-jira-item scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/create-jira-item/SKILL.md · 47 lines

What it actually says

Create Jira Item

Create Jira issues using the Atlassian MCP, with proper custom field handling.

1. Determine Target

  • Project: Use the project specified by the user. If not specified, infer by searching the user's recent issues (searchJiraIssuesUsingJql with (assignee = currentUser() OR reporter = currentUser()) ORDER BY updated DESC). If inference fails, ask.
  • Issue type: story, epic, task, initiative, etc. Infer from context or ask.

2. Introspect Custom Fields

Before creating the issue, discover the project's field requirements:

  1. Get available issue types via getJiraProjectIssueTypesMetadata(cloudId, projectIdOrKey).

  2. Get field metadata for the chosen issue type via getJiraIssueTypeMetaWithFields(cloudId, projectIdOrKey, issueTypeId).

  3. Pay attention to:

    • Required fields that are not standard (e.g., "Team", "Quarter", "Initiative Link", "Sprint")
    • Custom field IDs (customfield_NNNNN) -- use these in the create call
    • Allowed values for select/multi-select fields

For epics and initiatives especially, org-specific fields are common and must be populated. Do not rely on default field assumptions.

3. Create the Issue

Use createJiraIssue with:

  • Summary: terse, descriptive title
  • Description: terse. Bullet points preferred. No boilerplate.
  • Assignee: current user (use lookupJiraAccountId if needed)
  • Priority: Medium unless user specifies otherwise
  • All required custom fields populated from step 2

If the issue should be under an epic:

  • Use createIssueLink or set the epic link field (varies by Jira config)
  • If the user mentions an epic by name or key, search for it first via searchJiraIssuesUsingJql(cloudId, "project = X AND issuetype = Epic AND summary ~ 'name'").

5. Report

Return the issue key and URL. If any required fields were unknown or couldn't be populated, note them.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 47 lines · 48 tokens per session scan A de414d49235d

Subscribe to this mod's changes

create-jira-item is a skill published in the GitHub repository paultyng/skill-issue (9 stars, last pushed 29d ago), licensed MIT. It adds 48 tokens to every session and 535 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories