Claude Skills cheat sheet

incident-summary/
  SKILL.md
  template.md
  reference/format.md
  examples/outage-example.md
  scripts/check_summary.py

---
name: incident-summary
description: Write a blameless incident summary from notes or a timeline. Use when the user asks for an incident summary, post-incident report or outage write-up.
---

Use template.md. Steps:
1. Collect start, end, impact, detection and mitigation.
2. Write "not stated" for anything the notes do not say.
3. Keep it under 300 words.
4. Run scripts/check_summary.py and fix what it reports.

Weak:   Helps with documents.
Better: Create and edit Word (.docx) files with headings, tables and tracked changes. Use when the user asks for a Word document or to edit a .docx.

Level 1: name and description (always)
Level 2: SKILL.md body (when triggered)
Level 3: linked files and scripts (when needed)

#!/usr/bin/env python3
"""Check a summary. Usage: python check_summary.py summary.md"""
import sys
text = open(sys.argv[1], encoding="utf-8").read()
problems = [] if len(text.split()) <= 300 else ["over 300 words"]
print("OK" if not problems else "\n".join(problems))
sys.exit(1 if problems else 0)

Should trigger:     "write up last night's outage from these notes"
Should not trigger: "what does a 502 mean?"

grep -rn "curl\|wget\|urlopen\|requests\.\|eval(\|exec(" skills/NAME/

ls -la .claude/skills/NAME/
head -6 .claude/skills/NAME/SKILL.md