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) andgitto manage ticket creation and repository context. It executes commands such asacli auth status,acli jira project list,acli jira workitem search,acli jira workitem create, andgit branch --show-currentto perform its primary functions. - [DATA_EXFILTRATION]: The skill retrieves Atlassian authentication tokens using
acli auth tokenand transmits them within theAuthorizationheader ofcurlrequests 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
$ARGUMENTSvariable to generate the summary, type, and description of Jira tickets. - Ingestion points: User-provided instructions are ingested via the
$ARGUMENTSvariable inSKILL.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