agentleFS
paultyngpaultyng/skill-issue/skills/create-jira-item/SKILL.md

create-jira-item

Skill8 starsChanged 3 months agoMITView on GitHub

Create Jira issues (stories, epics, initiatives) with custom field introspection to fill org-specific fields correctly. Use when the user asks to create a Jira ticket, story, epic, initiative, or task.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 8
  2. Very specific:

    Project: Use the project specified by the user.

    line 12
  3. Distinctive:

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

    line 17
  4. Distinctive:

    All required custom fields populated from step 2

    line 36
  5. Distinctive:

    If the issue should be under an epic:

    line 40
  6. Very specific:

    Use createIssueLink or set the epic link field (varies by Jira config)

    line 41
  7. Very specific:

    If the user mentions an epic by name or key, search for it first via searchJiraIssuesUsingJql(cloudId, "project = X AND issuetype = Epic …

    line 42

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

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

4. Link to Epic (if applicable)

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.

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.