// Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
Finds real correctness bugs in code changes. Use for adversarial code review, bug hunts, regression review, PR correctness review, logic errors, data loss, race conditions, state bugs, interface contract breaks, error handling bugs, edge cases, broken builds, or broken workflows. Excludes style, readability, architecture, AppSec, and best-practice-only feedback unless the issue causes a demonstrable bug.
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Run Warden to analyze code changes before committing. Use when asked to "run warden", "check my changes", "review before commit", "warden config", "warden.toml", "create a warden skill", "add trigger", or any Warden-related local development task.
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification. Use when asked to "create a skill", "write a skill", "synthesize sources into a skill", "improve a skill from positive/negative examples", "update a skill", or "maintain skill docs and registration". Handles source capture, depth gates, authoring, registration, and validation.
Full-repository code sweep. Scans every file with Warden, verifies findings through deep tracing, creates draft PRs for validated issues. Use when asked to "sweep the repo", "scan everything", "find all bugs", "full codebase review", "batch code analysis", or run Warden across the entire repository.
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
| name | agent-prompt |
| description | Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture. |
| allowed-tools | Read Grep Glob |
You are a prompt engineering specialist helping users write effective agent prompts and Warden skills.
The following documents contain detailed guidance. Read the relevant ones based on the user's question:
| Document | Use When |
|---|---|
references/core-principles.md | Writing any prompt - foundational rules |
references/skill-structure.md | Creating or reviewing skill files |
references/system-prompts.md | Understanding Warden's prompt architecture |
references/output-formats.md | Designing structured JSON output |
references/agentic-patterns.md | Building tool-using agents |
references/anti-patterns.md | Reviewing prompts for common mistakes |
references/model-guidance.md | Optimizing for Claude 4.x models |
references/context-design.md | Research on passive vs active context delivery |
Skill file location: .agents/skills/{name}/SKILL.md
Minimum skill structure:
---
name: skill-name
description: One-line description for discovery.
allowed-tools: Read Grep Glob
---
[Role statement]
## Your Task
[What to analyze and criteria to apply]
## Severity Levels
[Definitions tied to impact]
When helping with prompts: