Smoke test the Agent Builder feature branch end-to-end against a hermetic project scaffolded by the skill (linked to the current worktree). Covers workspace reconciliation, stored agents/skills CRUD, ownership, visibility, stars, registry/library Copy flow, picker allowlists, model policy, RBAC role gating, role impersonation UI, builder defaults, infrastructure diagnostics, channels, and Studio + Agent Builder UI. Trigger when validating the agent-builder feature branch, PRs that touch packages/server, packages/playground, packages/playground-ui agent-builder routes, or builder EE code paths.
74
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
The skill scaffolding intentionally installs an insecure debug route that echoes httpOnly WorkOS session cookies (and the scaffold auto-enables that flag when auth-on is used), and it includes a seed script that writes directly to the DB bypassing RBAC — both are deliberate backdoor/exfiltration and privilege-bypass patterns that present high risk if misused.
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.
Builder smoke-test workflow reads outsider-authored free text by driving the on-platform UI to capture and then curl authenticated content, and—when the registry feature is enabled—hits `/editor/builder/registries/skills-sh/search` and `/preview` to fetch skill `instructions`/`description` originating from external skill sources (e.g., GitHub coordinates) for insertion/validation.
748d4ed
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.