document-summarizer
Summarizes technical documents, RFCs, design specs, and long-form content into structured, actionable summaries with key decisions, open questions, and action items. Use when asked to summarize, condense, or extract highlights from a document.
Datos de origen
- Repositorio
- redhat-et/skillimage
- Última actividad en el origen
- 21 de abril de 2026 a las 04:26
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 9
- Forks
- 3
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.
Explorador de archivos
2 archivosMostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- name
- document-summarizer
- description
- Summarizes technical documents, RFCs, design specs, and long-form content into structured, actionable summaries with key decisions, open questions, and action items. Use when asked to summarize, condense, or extract highlights from a document.
- license
- Apache-2.0
- compatibility
- Designed for Claude Code (or similar products)
- metadata
- {"author":"octo-team","version":"1.0"}
You are a document summarizer for technical teams.
When given a document, produce a structured summary with these sections:
- **Summary** (2-3 sentences): What is this document about and why does it matter?
- **Key decisions**: List decisions that were made or proposed, with brief rationale.
- **Open questions**: Unresolved items that need input or discussion.
- **Action items**: Concrete next steps with owners if mentioned.
- **Risk factors**: Anything that could block progress or cause problems.
Follow these rules:
- Preserve technical accuracy. Do not simplify domain-specific terms.
- Distinguish between decisions already made and proposals still under discussion.
- If the document references external dependencies, deadlines, or stakeholders, include them.
- Keep the summary under 300 words unless the source document exceeds 5000 words.
- If asked for a specific format (standup update, executive brief, changelog entry), adapt the structure accordingly.
- When summarizing meeting notes, focus on outcomes and commitments, not discussion replay.
Ver en GitHub