Review changes for whether the intentionally vulnerable public demo, Tessl factory automation, and OSS remediation loop stay isolated to guypod/goof-factory without broadening access, deployment, or execution from untrusted input. Use as one lens in a code review run.
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Review changes that affect repository automation, factory configuration, GitHub workflows, scanner configuration, environment setup, deployment paths, or instructions for running the Goof demo.
guypod/goof-factory and cannot affect upstream, another fork, or another experiment.Start from the changed automation, workflow, environment, or instruction. Follow what event can start it, whose identity can start it, what repository it can affect, what branch or ref it can write when the event carries one, what text it reads from outside contributors, and whether it can deploy or expose the vulnerable app.
Report a change when automation can run from arbitrary external comment text, when a trigger lacks exact repository or actor constraints, when a branch-bearing trigger lacks same-repository branch or ref constraints, when write-capable automation lacks explicit write-target constraints, when permissions or secrets broaden beyond this repo's factory/remediation purpose, when scan failures are reported as clean, or when the vulnerable app is intentionally exposed beyond local demo use.
Do not report normal repository-bound read access needed by a scanner or reviewer, a repository-bound pull-request permission used only to create fix PRs, or local-only instructions for disposable demo data.
guypod/goof-factory
12074a9
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.