Security audit
Security checks for vulnerabilities and agentic risk
This is a broad coding-workflow skill, but the inspected artifact is a plain Markdown guide that emphasizes planning and user confirmation rather than hidden or unsafe actions.
Before installing, understand that this skill may activate for many coding requests and can shape the agent into a slower, confirmation-heavy build process. It appears appropriate for guided greenfield coding work; continue reviewing generated code, dependencies, and commands before allowing them to run in your environment.
The skill description is extremely broad, covering almost any request to build software from a natural-language prompt. That can cause the skill to activate on common development-assistance requests and take over interactions beyond a narrowly scoped purpose, increasing the chance of unintended code generation or unsafe guidance in contexts that need stricter controls.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
4. After each phase, ask: "Does this look right? Anything to change before I move on?"
5. Incorporate feedback before proceeding
Never skip a phase. Never start the next phase without confirmation.
## Phase 4 — Error Handling
No suspicious patterns detected.