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.

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 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/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-cloud/the-jira-cloud-platform-rest-api/SKILL.md
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 enables automated tasks such as creating issues, retrieving issue details, updating fields, and managing workflows within a Jira instance. The agent can be used for streamlining development processes and improving team collaboration by automating repetitive actions.

When to use it

  • Automated Issue Creation: Automatically create new Jira tickets based on events in other systems (e.g., error logs from an application).
  • Status Updates: Update the status of existing Jira issues based on changes in a connected workflow or external system.
  • Issue Retrieval & Reporting: Retrieve specific issue details and generate reports for project management purposes.
  • Field Population: Automatically populate custom fields within Jira issues with data from other sources.

Key capabilities

  • REST API interaction
  • Jira Cloud Platform integration
  • Issue creation
  • Issue retrieval
  • Workflow management
  • Field updates

Example prompts

  • "Create a new Jira issue in project 'DevOps' with summary 'Broken build pipeline' and priority 'High'."
  • "Retrieve the details of Jira issue JIRA-123."
  • "Update the status of Jira issue JIRA-456 to 'In Progress'."

Tips & gotchas

  • Requires proper authentication credentials (API token or username/password) for accessing the Jira Cloud instance.
  • Jira API rate limits may apply, so design prompts and workflows accordingly to avoid exceeding them.