Skip to content
TrustedSkillsbeta
Back to all skills

The Jira Cloud Platform Rest Api

Checked
yuyz0112·vlatest·productivity

Helps with REST APIs, API as part of developing backend services and APIs workflows.

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 the-jira-cloud-platform-rest-api -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/public-api-skills at 5aa20d98ca.

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

Scanned
60 files, 2,982 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 allows AI agents to interact with the Jira Cloud Platform using its REST API. It can retrieve information about issues, projects, and users, as well as create and update issues based on provided data. The agent can automate tasks like creating bug reports or updating issue statuses within a Jira instance.

When to use it

  • Automated Bug Reporting: Automatically create Jira tickets from error logs generated by an application.
  • Project Status Updates: Retrieve project status and update stakeholders via automated reporting.
  • Issue Assignment: Assign new issues to team members based on predefined rules or criteria.
  • Workflow Automation: Trigger actions in other systems when a Jira issue transitions through specific workflow states.

Key capabilities

  • Retrieval of issue details (summary, description, status)
  • Creation of new Jira issues
  • Updating existing Jira issues
  • Accessing project information
  • User management within the Jira instance

Example prompts

  • "Create a new Jira ticket for 'Login failed' with severity 'High'."
  • "What is the current status of issue JIRA-123?"
  • "Assign issue JIRA-456 to John Doe."

Tips & gotchas

  • Requires authentication credentials (API token or username/password) for accessing the Jira Cloud instance.
  • Jira API rate limits may apply; design prompts accordingly to avoid errors.