use-jira-cli
Pass
Audited by Gen Agent Trust Hub on Sep 21, 2026
Risk Level: SAFECOMMAND_EXECUTIONINDIRECT_PROMPT_INJECTIONCREDENTIALS_UNSAFE
Full Analysis
- [COMMAND_EXECUTION]: The skill utilizes the
jiracommand-line tool (specificallyankitpokhrel/jira-cli) to interact with Jira. It includes safety checks to verify the tool's presence and version before execution. - [CREDENTIALS_UNSAFE]: The skill mentions handling
JIRA_API_TOKENbut provides robust safety guidelines. It explicitly forbids the agent from printing secrets, persisting them, or placing them in command arguments, recommending secure alternatives like environment variables or keychains. - [INDIRECT_PROMPT_INJECTION]: The skill processes external data when reading Jira issues and comments.
- Ingestion points: Commands such as
jira issue viewandjira issue list(inSKILL.mdandreferences/commands.md) ingest content from external Jira instances. - Boundary markers: The skill encourages using structured output flags like
--plain,--raw, or--csvto facilitate safer parsing. - Capability inventory: The agent has the ability to write to the Jira API (mutations) and read external content, but these are gated by authorization requirements.
- Sanitization: Instructions mandate quoting values and using stdin or templates for long content to prevent shell injection when handling external data.
- [SAFE]: The skill implements a strict authorization workflow for all destructive or additive operations, requiring the agent to show the proposed mutation and receive explicit user approval before execution.
Audit Metadata