Skip to content
TrustedSkillsbeta
Back to all skills

Jira

Checked
davila7·vlatest·productivity·MIT

This skill integrates Jira into your workflows, allowing you to manage and interact with Jira issues directly from your chat interface for streamlined project tracking.

Repository

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 davila7/claude-code-templates --skill jira -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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Commit
79182c51fb
Manifest
cli-tool/components/skills/ai-research/jira/SKILL.md
Scanned
4 files, 1,138 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

jira by davila7

What it does

This skill enables AI agents to interact directly with Jira, allowing them to create, update, and manage issues within your project management workflow. It bridges the gap between natural language commands and Jira's backend systems for streamlined task handling.

When to use it

  • Automating repetitive ticket creation based on meeting notes or code commit messages.
  • Updating issue statuses or adding comments when an AI agent completes a specific development task.
  • Querying existing tickets to provide agents with context about ongoing bugs or feature requests.
  • Generating and assigning new tasks to team members during sprint planning sessions.

Key capabilities

  • Create new Jira issues from natural language descriptions.
  • Update existing issue fields such as status, priority, and description.
  • Add comments and attachments to specific tickets.
  • Search and retrieve issue details using flexible query parameters.

Example prompts

  • "Create a high-priority bug ticket for the login page timeout error reported in yesterday's deployment."
  • "Update issue PROJ-123 to 'In Progress' and assign it to Sarah Jenkins."
  • "Search for all open tasks related to the Q4 marketing campaign and list their current statuses."

Tips & gotchas

Ensure your AI agent has valid API credentials with appropriate permissions before attempting to modify issues. Complex Jira workflows may require specific field mappings that aren't automatically inferred from generic descriptions, so be explicit about required data when creating tickets.