Skill Writer
Usage
Describe what the skill should do, and this will generate a complete skill YAML file.
Instructions
When the user describes a skill they want to create:
- Understand the Purpose: Clarify what the skill should analyze or check
- Design the Prompt: Write a clear, specific system prompt for the Claude agent
- Configure Tools: Select appropriate tool restrictions based on the skill's needs
- Define Output Expectations: Ensure the skill will produce valid SkillReport output
Skill Definition Schema
name: skill-name # kebab-case, unique identifier
description: Short description of what the skill does
More from getsentry/warden
architecture-review
Staff-level codebase health review. Finds monolithic modules, silent failures, type safety gaps, test coverage holes, and LLM-friendliness issues.
138warden
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.
113agent-prompt
Reference guide for writing effective agent prompts and skills. Use when creating new skills, reviewing prompt quality, or understanding Warden's prompt architecture.
96testing-guidelines
Guide for writing tests. Use when adding new functionality, fixing bugs, or when tests are needed. Emphasizes integration tests, real-world fixtures, and regression coverage.
93warden-sweep
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.
83find-warden-bugs
Warden-specific bug detection from historical patterns. Targets the architectural seams where bugs have repeatedly occurred: SDK IPC, dual report paths, config threading, concurrent execution, and output rendering.
68