serpapi-ci-integration
Pass
Audited by Gen Agent Trust Hub on Sep 11, 2026
Risk Level: SAFE
Full Analysis
- [SAFE]: The skill instructions emphasize critical security practices, such as preventing secrets (like
SERPAPI_KEY) from being exposed to fork pull requests and ensuring that live search operations are restricted to protected, manually-approved environments.\n- [SAFE]: The tool configuration is appropriately scoped; the use of theghCLI is restricted to repository operations, and instructions prioritize reading and verifying configurations over performing intrusive actions.\n- [SAFE]: All external references point to official and well-known documentation from GitHub and SerpAPI. The example workflows use pinned versions of official GitHub Actions (e.g.,actions/checkout@v4).\n- [INDIRECT_PROMPT_INJECTION]: The skill defines a process for handling external API responses and repository metadata. While this represents a data ingestion surface, the skill explicitly mitigates risks by requiring sanitized fixtures, secret redaction testing, and boundary checks for automated workflows. \n - Ingestion points:
WebFetchis used to verify client behavior, and repository CI files are read for inventory.\n - Boundary markers: The skill mandates the use of 'sanitized fixtures' and 'protected environments' for live lanes.\n
- Capability inventory: Tools include
Bash(gh:*),Write, andEditfor workflow configuration.\n - Sanitization: Instructions include explicit steps for secret redaction testing and inventorying secret scopes before enabling automation.
Audit Metadata