Skip to content
TrustedSkillsbeta
Back to all skills

Jira Cli

Checked
code-and-sorts·vlatest·productivity·CC0-1.0

JiraCli allows you to interact with your Jira instance via command-line, streamlining automation and issue management workflows.

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 code-and-sorts/awesome-copilot-agents --skill jira-cli -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

code-and-sorts

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 code-and-sorts/awesome-copilot-agents at a26d912e4a.

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

Commit
a26d912e4a
Manifest
skills/jira-cli/SKILL.md
Scanned
1 file, 271 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

The jira-cli skill provides command-line interface (CLI) access to Jira instances. It allows users to interact with Jira, including creating issues, retrieving issue details, and managing workflows, directly from a terminal or script. This facilitates automation of Jira tasks and integration with other tools.

When to use it

  • Automated Issue Creation: Automatically create new Jira tickets based on data from external sources (e.g., monitoring alerts).
  • Issue Status Updates: Update the status of existing Jira issues programmatically, for example, in response to a CI/CD pipeline event.
  • Retrieving Issue Details: Quickly fetch specific information about Jira issues without navigating through the web interface.
  • Workflow Management: Trigger workflow transitions on Jira issues using command-line commands.

Key capabilities

  • Issue creation
  • Issue retrieval
  • Workflow management
  • CLI access to Jira instances

Example prompts

  • "Create a new Jira issue for 'Database connection error' with priority 'High'."
  • "Get the details of Jira issue JIRA-123."
  • "Transition Jira issue JIRA-456 to 'In Progress'."

Tips & gotchas

  • Requires proper authentication credentials (API token or username/password) for your Jira instance.
  • Jira project and issue keys must be correctly formatted for commands to succeed.