Skip to content
TrustedSkillsbeta
Back to all skills

Jira Assistant

Checked
tech-leads-club·vlatest·productivity

The Jira Assistant streamlines your workflow by automating common tasks like issue creation and updates, boosting team productivity and reducing manual effort.

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 tech-leads-club/agent-skills --skill jira-assistant -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

tech-leads-club

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 tech-leads-club/agent-skills at 6df68d5202.

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

Commit
6df68d5202
Manifest
packages/skills-catalog/skills/(development)/jira-assistant/SKILL.md
Scanned
2 files, 445 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 Assistant helps AI agents interact with Atlassian Jira using Model Context Protocol (MCP). It enables users to search for existing issues, create new ones (Tasks, Epics, and Subtasks), update issue details, transition issue statuses (e.g., To Do → In Progress → Done), add comments, manage assignees, and query issues based on specific criteria. This skill streamlines Jira workflows and reduces manual effort.

When to use it

  • Searching for existing Jira issues or tasks.
  • Creating new Jira issues of different types (Task, Epic, Subtask).
  • Updating the status of an issue (e.g., moving from "To Do" to "In Progress").
  • Adding comments and managing assignees on Jira issues.
  • Querying for issues that meet specific criteria, such as those assigned to you or with a high priority.

Key capabilities

  • Issue Search: Uses both natural language searches (via Rovo Search) and JQL queries to find Jira issues.
  • Issue Creation: Creates new Jira issues, guiding the user through necessary steps including viewing issue types and required fields.
  • Issue Updates: Allows for updating existing issue details and transitioning statuses.
  • Configuration Detection: Automatically detects Jira project configuration from workspace rules or by querying available projects if no rules are found. It prompts the user to specify a project key if needed.
  • JQL Support: Supports JQL queries for precise filtering, requiring inclusion of project = {PROJECT_KEY} in all queries.

Example prompts

  • "Search for issues assigned to me."
  • "Create a new Task issue in the KAN project with the summary 'Implement user authentication'."
  • "What are the available issue types for the PROJ project?"
  • “Find bugs in progress.”

Tips & gotchas

  • Configuration Required: To use this skill effectively, configure it by creating a .cursor/rules/jira-config.mdc file with your Jira project details (Project Key, Cloud ID, URL, Board URL).
  • JQL Requirement: When using JQL queries, always include project = {PROJECT_KEY} to ensure accurate results.
  • Natural Language First: Start with natural language searches for general queries; use JQL only when precise filtering is needed.