Document Summary Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: document-summary
description: Summarise a document the user provides into key points, decisions and actions. Use when the user asks to summarise, shorten or give the gist of a document, report or article.
---

Summarise the document the user shared.

1. If no document is shared, or the purpose and length of the summary
   are unclear, ask once, in one message, then continue.
2. Write the summary under these headings:
   - In brief: two or three sentences.
   - Key points: five to eight bullets, in the document's order.
   - Decisions or conclusions: what the document settles.
   - Actions: who must do what, by when, if stated.
   - Open questions: anything left unresolved.
3. Keep figures, names and dates exactly as written in the document.

Rules:
- Use only what is in the document. Do not add outside facts or opinions.
- If a section is missing from the document, write "not stated".
- For legal, medical or financial documents, say the summary is not
  professional advice and the original should be checked.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/document-summary
mv SKILL.md ~/.claude/skills/document-summary/

# then, inside Claude Code, either ask naturally:
#   summarise this report for me
# or run it by name:
#   /document-summary