jira-service-desk
Pass
Audited by Gen Agent Trust Hub on Apr 27, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: No malicious patterns, obfuscation, or prompt injection attempts were detected. The skill is purely instructional and documented clearly.
- [COMMAND_EXECUTION]: The skill provides example
curlcommands to demonstrate how to interact with the Jira Service Desk API via Apideck's Proxy service (unify.apideck.com). These are standard usage examples. - [DATA_EXPOSURE]: No hardcoded credentials or sensitive file paths were identified. The documentation correctly uses environment variable placeholders (e.g.,
${APIDECK_API_KEY},${CONSUMER_ID}) for authentication headers. - [INDIRECT_PROMPT_INJECTION]: The skill involves processing external data from the Jira Service Desk API.
- Ingestion points: Raw HTTP responses from Jira Service Desk endpoints via the Apideck Proxy (SKILL.md).
- Boundary markers: None specified in the documentation.
- Capability inventory: The skill facilitates network operations (HTTP requests) to external services (SKILL.md).
- Sanitization: No explicit sanitization or validation of the downstream API responses is mentioned in the instructions.
Audit Metadata