crontap-debug-failed-runs
Pass
Audited by Gen Agent Trust Hub on Sep 15, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: No malicious patterns, obfuscation, or unauthorized access attempts were identified in the skill instructions or examples.
- [CREDENTIALS_SAFE]: The skill demonstrates safe credential management by using shell environment variables (
$CRONTAP_CLIENT_ID,$CRONTAP_API_KEY) in its REST fallback examples instead of hardcoded secrets. - [DATA_EXPOSURE]: The instructions include specific safety guardrails, explicitly telling the agent never to reveal hidden headers or ask the user to provide secret tokens, which helps prevent accidental credential exposure.
- [EXTERNAL_DOWNLOADS]: All external URLs point to official
crontap.comandapi.crontap.comresources, which are the legitimate infrastructure of the skill's author, posing no external supply chain risk. - [INDIRECT_PROMPT_INJECTION]: The skill processes external data via API tools, creating a theoretical injection surface.
- Ingestion points: Data returned from
get_scheduleandget_schedule_historytools inSKILL.md. - Boundary markers: The instructions mandate verifying timestamps and signatures and explicitly state that read operations do not authorize configuration changes.
- Capability inventory: The skill is restricted to read-only diagnostic tools with no file-write or subprocess execution capabilities.
- Sanitization: Relies on the agent's internal safety filters and defined MCP tool constraints.
Audit Metadata