Skip to content
TrustedSkillsbeta
Back to all skills

Jira Automation

Checked
davepoon·vlatest·productivity·MIT

Automatically create, update, and transition Jira issues based on natural language requests and external data.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add davepoon/buildwithclaude --skill jira-automation -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

davepoon

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned davepoon/buildwithclaude at fc03a95b41.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 192 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates tasks within Jira, a popular project management tool. It allows AI agents to create, update, and transition issues based on natural language instructions. The skill streamlines workflows by reducing manual interaction with Jira and improving overall efficiency.

When to use it

  • Automatically create new Jira tickets when customer support requests are received via email.
  • Update the status of existing Jira issues based on changes in related systems (e.g., code deployment).
  • Transition Jira issues through defined workflows, such as moving a ticket from "In Progress" to "Review."
  • Assign Jira tickets to specific team members or groups based on issue type and priority.

Key capabilities

  • Issue creation
  • Issue updating
  • Workflow transitions
  • Assignment of issues

Example prompts

  • “Create a new Jira ticket for ‘Website login failing’ with severity 'High' assigned to the DevOps team.”
  • "Move Jira issue ABC-123 from 'In Progress' to 'Testing'."
  • "Update the description of Jira ticket XYZ-456 to include details about the error message."

Tips & gotchas

The skill requires appropriate API credentials for accessing your Jira instance. Ensure these are securely provided and that the AI agent has sufficient permissions within Jira to perform the requested actions.