data-cleanup
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns,…
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
$ npx -y skills add sgharlow/claude-code-recipes --skill meeting-notes-to-actions --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/meeting-notes-to-actionsContext preview
The summary Claude sees to decide when to auto-load this skill.
Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy
name: meeting-notes-to-actions description: Turn raw meeting notes into a shareable summary, an action-item table with owners and deadlines, and follow-up email drafts. Use when the user says "process my meeting notes", "extract action items", "who owns what from this meeting", or "draft the follow-ups" — or pastes messy notes right after a meeting.
Convert disorganized meeting notes into structured accountability: a clean summary, an action-item table, and a personalized follow-up draft per owner. Work only from what the notes actually say — never invent owners, deadlines, or decisions that are not in the notes.
1. Get the notes. Accept pasted text, a file path, or a transcript. If the notes name attendees ambiguously (initials, first names shared by two people), ask the user to resolve them before assigning ownership. 2. Extract, citing the notes:
no owner or deadline, mark it `UNASSIGNED` / `NO DATE` rather than guessing, and list those gaps for the user to fill.
3. Render three outputs in this order:
4. Verify before presenting: every action item in the table must trace to a line in the notes, and every owner must appear in the attendee list. Ask the user to confirm the `UNASSIGNED` / `NO DATE` gaps — do not send or save drafts until they have reviewed them.
from their own mail client.
offer a two-line summary instead.
Full walkthrough, examples, and variations: `recipes/Recipe-001-Meeting-Notes-to-Action-Items.md`.
Claude Code artifacts graded by Skill Crossroads — click the badge for the evidence-cited scorecard. Your Complete Guide to AI-Powered Productivity
Repo: sgharlow/claude-code-recipes
Clean and standardize messy tabular data (CSV, spreadsheet paste, system exports) into an analysis-ready dataset — consistent dates and names, typed columns,…
Turn a process description into an operational quality-control checklist — binary pass/fail checks, acceptance criteria, critical-vs-routine tiers, and failure…
Synthesize multiple sources — articles, reports, notes, transcripts — into one structured brief with themes, agreements, contradictions, and gaps. Use when the…
Summarize a long document into an executive summary, key points, and role-specific implications. Use when the user says "summarize this document", "give me the…
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers,…