ship-and-monitor
Run the normal guarded ship flow, then do requested post-merge checks. Add independent beta behavior checks only when requested or a concrete deployment-specific risk makes local proof insufficient. Use when standard `/ship` needs post-merge beta/live, docs, release, or production verification.
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
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
The workflow instructs the agent to read merged PR feedback/comments and check GitHub Actions workflows, which ingest outsider contributions and feedback.
- Repository
BuilderIO/agent-native
- Revision
46ed84c
- 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.