AugmentClaude

Meeting Notes to Actions

Extract action items, owners, and decisions from meeting notes.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/meeting-notes-to-actions-shopee-eng/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Convert meeting notes into owners, action items, decisions, and follow-up messages.

What this skill does

meeting-notes-to-actions

Goal

Convert raw meeting notes into a structured follow-up plan. This example demonstrates a functional skill that is not tied to any specific agent runtime or business domain.

Principles

  • Orchestration stays in SKILL.md.
  • Function behavior lives in functions/*.md.
  • Do not fabricate owners, due dates, or decisions that are missing from the meeting notes.
  • Only use trace logs when the caller enables reporting.
  • Deterministic input normalization belongs in scripts/, not in prompt judgment.

References

ResourceLoad TimingPurpose
shared_glossaryOn demandShared terminology for this example.

External Inputs

FieldSourceDescription
meeting_notesuserRaw meeting notes text.
default_due_dateuserOptional fallback due date label.
report_modeuseroff, local, or remote; defaults to off.

Execution Pipeline

StepFunctionPurposeInputOutput
1load_meeting_notesNormalize raw notes and source metadata.meeting_notesnotes_context
2extract_action_itemsExtract owners, actions, decisions, and open questions.notes_context<br>default_due_dateaction_items<br>decisions<br>open_questions
3draft_follow_upDraft a concise follow-up message.action_items<br>decisions<br>open_questionsfollow_up_message

Output Scope

This example returns structured data and does not write project files.

Related skills