Skip to content
TrustedSkillsbeta
Back to all skills

Jira 8 13 17

Checked
yuyz0112·vlatest·productivity

This skill allows you to interact with Jira issues (versions 8, 13, and 17) for automation and data retrieval, streamlining 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 yuyz0112/public-api-skills --skill jira-8-13-17 -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

yuyz0112

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 yuyz0112/stripe-api-skills at 5aa20d98ca.

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

Commit
5aa20d98ca
Manifest
apis/jira-server/jira-8-13-17/SKILL.md
Scanned
60 files, 1,088 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 provides access to Jira functionality. It allows users to interact with Jira instances, retrieve information about issues, and potentially perform actions on them. Specifically, the skill can be used to query issue details and manage tasks within a Jira environment.

When to use it

  • You need to quickly check the status of a specific Jira ticket by its key (e.g., "PROJECT-123").
  • You want to summarize all open bugs assigned to your team in a Jira project.
  • You’re automating a workflow and need to update the assignee or priority of a Jira issue based on external events.
  • You're building an internal tool that needs to integrate with Jira data for reporting or analysis.

Key capabilities

  • Querying Jira issues by key
  • Retrieving issue details (status, assignees, etc.)
  • Managing tasks within a Jira environment

Example prompts

  • "What is the status of PROJECT-456?"
  • "List all open bugs in project TEST."
  • "Change the assignee for ticket ABC-789 to John Doe."

Tips & gotchas

  • You will need appropriate credentials and permissions within your Jira instance for this skill to function correctly. Ensure the AI agent has access to the relevant Jira projects.