document-summary_skill

Overview

This skill summarizes technical documents into concise, structured Markdown. It converts long technical text into a short summary, a bulletized set of key points, and a risks section to surface concerns. The output is optimized for quick review by engineers, managers, or reviewers.

How this skill works

Provide the document text as the required input and the skill reads the content end-to-end. It returns valid Markdown with three sections: a short Summary, a Key Points bullet list, and a Risks section highlighting potential issues. The skill follows a professional technical analyst voice and keeps the summary to five lines or fewer.

When to use it

• Reading long technical reports, design docs, or RFCs to get a quick overview
• Preparing meeting briefs or executive summaries from detailed documentation
• Extracting action items and concerns before design reviews
• Archiving documents with searchable summaries and risk notes
• Validating third-party technical proposals quickly

Best practices

• Provide the full document text for best context; include diagrams as text descriptions where possible
• Specify the audience or focus if you want emphasis on security, performance, or architecture
• Keep source content coherent and minimally edited to avoid losing critical signals
• Request follow-up breakdowns (e.g., detailed risks, remediation steps) if deeper analysis is needed
• Use consistent naming and abbreviations in source material for clearer bullet extraction

Example use cases

• Summarize a 20-page API design doc into a one-paragraph summary plus key implementation points
• Extract security and compliance risks from vendor integration documentation
• Create a short executive briefing from a technical post-mortem
• Generate a compact archive entry for a large repository of technical files
• Prepare a pre-meeting one-pager highlighting decisions and open questions