fetch-ci-build
Fetch CI build results and diagnose failures. Auto-detects provider from project files or URLs. Supports GitHub Actions, Buildkite, and CircleCI.
77
68%
Does it follow best practices?
Impact
92%
1.67xAverage score across 3 eval scenarios
Low
Low-risk findings worth noting
Fix and improve this skill with Tessl
tessl review fix ./tests/ext_conformance/artifacts/agents-mikeastock/skills/fetch-ci-build/SKILL.mdLow
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Third-party content exposure detected (high risk: 0.80). The skill's required workflow and scripts (SKILL.md Step 3–4 and scripts/fetch_buildkite_failures.py's fetch_raw_log and scripts/fetch_circleci_failures.py's fetch_job_log) explicitly fetch and parse CI build logs and job output from third-party CI provider APIs (Buildkite/CircleCI/GitHub) which are untrusted, user-generated content that the agent reads and uses to drive diagnostics and fix actions.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
6453c0b
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.