docs-review
Reviews documentation for voice, style, and structure alignment with Outfitter standards. Use when reviewing docs, checking content quality, or when "review this doc", "voice check", "style review", or "is this ready?" are mentioned.
Datos de origen
- Repositorio
- outfitter-dev/agents-internal
- Última actividad en el origen
- 26 de enero de 2026 a las 22:25
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- docs-review
- description
- Reviews documentation for voice, style, and structure alignment with Outfitter standards. Use when reviewing docs, checking content quality, or when "review this doc", "voice check", "style review", or "is this ready?" are mentioned.
- context
- fork
- agent
- editor
- metadata
- {"version":"1.0.0","author":"outfitter"}
# Documentation Review
Review the current document against Outfitter standards for voice, style, and structure.
## Review Direction
$ARGUMENTS
If direction is provided above, focus on that specific aspect. Otherwise, perform a general review across all dimensions.
## Review Criteria
### Voice
Does it sound like Outfitter?
- Confident, opinionated stance
- Agents as first-class consumers
- Plain language over jargon
### Style
Is the craft right?
- Punch-and-flow rhythm (short + long sentences)
- Earned enthusiasm (backed by substance)
- Strong opening and closing
### Structure
Does it follow documentation patterns?
- Appropriate template usage
- Complete, runnable examples
- Correct heading hierarchy (h1 > h2 > h3)
## Output Format
Provide your review in this format:
**Status**: Ready | Needs Work
**Summary**: One sentence overall assessment.
**Issues** (if any):
- [Location] Issue description and suggested fix
**Strengths**:
- What works well
If the document is ready, say so briefly. If it needs work, be specific about locations and fixes.
Ver en GitHub