Skip to content
TrustedSkillsbeta
Back to all skills

Design Jira State Analyzer

Checked
dawiddutoit·vlatest·productivity

Analyzes Jira state transitions to identify bottlenecks, inefficiencies, and potential workflow improvements using AI.

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 dawiddutoit/custom-claude --skill design-jira-state-analyzer -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

dawiddutoit

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 dawiddutoit/custom-claude at 17b45a90a6.

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

Commit
17b45a90a6
Manifest
skills/design-jira-state-analyzer/SKILL.md
Scanned
1 file, 541 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 design-jira-state-analyzer skill analyzes Jira ticket states and provides insights based on that data. It can determine the current status of tickets, identify trends in ticket resolution times, and summarize overall project health by analyzing the distribution of tickets across different statuses. This allows for a deeper understanding of workflow bottlenecks and potential areas for improvement.

When to use it

  • Project Health Check: Quickly assess the current state of a Jira project and identify any immediate concerns regarding ticket backlog or resolution progress.
  • Workflow Optimization: Analyze ticket movement patterns to pinpoint inefficiencies in your team's workflow.
  • Performance Reporting: Generate reports on key metrics like average time spent in each status, allowing for better performance tracking and communication with stakeholders.
  • Root Cause Analysis: Investigate why tickets are getting stuck in certain statuses or taking longer than expected to resolve.

Key capabilities

  • Jira ticket state analysis
  • Trend identification within Jira data
  • Project health summarization
  • Workflow bottleneck detection

Example prompts

  • "Analyze the current status distribution of all open tickets in project 'XYZ'."
  • "What is the average time a ticket spends in the 'In Progress' status?"
  • "Summarize the overall health of the 'ABC' Jira project based on ticket states."

Tips & gotchas

  • Requires access to a Jira instance and appropriate permissions.
  • The accuracy of the analysis depends on the completeness and consistency of data within your Jira system.