What you get with Skills
Repeatable workflows
Turn common engineering tasks into reusable playbooks instead of rewriting prompts every time.
Team consistency
Keep execution style, coding standards, and decision criteria aligned across contributors.
Faster execution
Reduce context-switch cost with structured steps and built-in task boundaries.
Easier onboarding
New teammates can start with proven flows instead of inventing process from scratch.
Rewrite Skills repository
RewriteToday/skills
Official skill library with practical templates and workflows you can adapt to your stack.
Install and use Skills
Use the command below to add a skill source:After adding, follow your agent environment docs to list, activate, and run installed skills.
Where Skills fit in your stack
Planning
Break down large goals into clear, actionable steps.
Implementation
Execute changes with stable patterns for edits, tests, and validation.
Operations
Handle triage, CI fixes, and documentation workflows with less variance.
Typical skill structure
1. Scope and intent
1. Scope and intent
Define exactly what the skill owns and when it should be triggered.
2. Execution workflow
2. Execution workflow
List the sequence of actions: discovery, implementation, validation, and handoff.
3. Guardrails
3. Guardrails
Add non-negotiables such as safety checks, style constraints, and prohibited operations.
4. Reusable assets
4. Reusable assets
Include scripts, templates, and references to reduce manual repetition.
Best practices
- Keep each skill narrowly scoped to one outcome.
- Prefer concrete steps over broad generic instructions.
- Add validation criteria so success is measurable.
- Version and evolve skills as your codebase and tooling change.
- Link each skill to real workflows used by your team.
Related docs
API Introduction
Reference for endpoints, auth, and operational constraints used by AI workflows.
Ecosystem
See how Rewrite packages can support agent-driven implementations.