Run one factory triage run on the factory VM: settle the fixed batch of items in the watcher's message, triage, fold reports into fix branches already working on the same problem, start one Builder branch per new fix group without waiting for it, record each returned branch result, reply, and finish. Use whenever a message starts "Handle the new factory events", "Continue the current factory run", or "Review <PR url> for the agent-native factory".
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Critical
Do not install without reviewing
Detected a prompt injection in the skill instructions. The skill contains hidden or deceptive instructions that fall outside its stated purpose and attempt to override the agent’s safety guidelines or intended behavior.
The skill is a legitimate factory triage workflow, but its babysit-round reference tells the agent to override Builder's default safeguards on commits and to disregard "read-only" constraints in the message, which weakens a protection beyond what the advertised task needs.
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.
The required triage workflow reads Slack feedback-channel roots, replies, mentions, and reactions, plus GitHub issues and outside-contributor fork PRs, all of which outsiders can post into without the agent selecting a specific item first.
BuilderIO/agent-native
cf9ff10
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.