create-jira-ticket

Pass

Audited by Gen Agent Trust Hub on Sep 25, 2026

Risk Level: SAFECOMMAND_EXECUTIONDATA_EXFILTRATIONINDIRECT_PROMPT_INJECTION
Full Analysis
  • [COMMAND_EXECUTION]: The skill utilizes the Atlassian CLI (acli) and git to manage ticket creation and repository context. It executes commands such as acli auth status, acli jira project list, acli jira workitem search, acli jira workitem create, and git branch --show-current to perform its primary functions.
  • [DATA_EXFILTRATION]: The skill retrieves Atlassian authentication tokens using acli auth token and transmits them within the Authorization header of curl requests sent to Jira Cloud endpoints (atlassian.net). This is a functional requirement for interacting with the Jira API but involves the transmission of sensitive bearer tokens over the network.
  • [INDIRECT_PROMPT_INJECTION]: The skill is designed to process untrusted user input from the $ARGUMENTS variable to generate the summary, type, and description of Jira tickets.
  • Ingestion points: User-provided instructions are ingested via the $ARGUMENTS variable in SKILL.md (Step 3).
  • Boundary markers: No explicit delimiters or boundary markers are employed to isolate user-provided text from the operational instructions of the skill.
  • Capability inventory: The skill possesses the ability to execute shell commands (acli, git, curl), perform network requests to external Atlassian services, and write temporary JSON files to the local file system.
  • Sanitization: The risk is partially mitigated by a mandatory confirmation preview (Step 6), which requires the user to review and approve the inferred ticket content before any creation command is executed.
Audit Metadata
Risk Level
SAFE
Analyzed
Sep 25, 2026, 03:19 PM