Clawhub Jira Pat Skill

ReviewAudited by ClawScan on May 10, 2026.

Overview

This is a coherent Jira integration, but it uses a Jira Personal Access Token and can change Jira issues, so users should limit the token and review write actions.

Before installing, confirm you want the agent to use a Jira PAT for this instance. Use the narrowest PAT permissions available, set JIRA_URL only to your trusted Jira server, and review any command that creates, updates, comments on, or transitions Jira issues.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Medium

#ASI03: Identity and Privilege Abuse

What this means

The agent can access Jira as allowed by the PAT, including reading and changing issues if the token has those permissions.

Why it was flagged

The skill relies on a Jira Personal Access Token, so actions taken through the skill inherit the permissions granted to that token.

Skill content

Create a new token with appropriate permissions ... Store it in environment variable `JIRA_PAT`

Recommendation

Use a least-privilege PAT, keep it out of logs and shared shells, and revoke or rotate it if it is no longer needed.

Medium

#ASI02: Tool Misuse and Exploitation

What this means

If used incorrectly, the agent could comment on, transition, update, or create Jira issues in an enterprise project.

Why it was flagged

The skill documents Jira API write operations that can change issue state, fields, comments, or create new issues. This is aligned with the stated purpose but is higher impact than read-only access.

Skill content

### Transition (Change Status) ... curl -s -X POST ... ### Update Issue Fields ... curl -s -X PUT ... ### Create an Issue

Recommendation

Require user confirmation for write operations and verify the issue key, transition ID, and payload before running POST or PUT commands.

Low

#ASI04: Agentic Supply Chain Vulnerabilities

What this means

A user relying only on metadata may not realize the skill needs a Jira token and local command-line tools until they read the skill instructions.

Why it was flagged

The supplied metadata does not declare the actual runtime requirements and credential use that SKILL.md and scripts/jira-pat.sh disclose: JIRA_PAT, JIRA_URL, curl, and jq.

Skill content

Required binaries (all must exist): none ... Required env vars: none ... Primary credential: none

Recommendation

Update metadata to declare JIRA_PAT, JIRA_URL, curl, and jq so users and platforms can assess requirements before installation.