Skip to main content
Agent skill

Meeting Notes

Meeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Meeting Notes when an AI agent needs a reusable SKILL.md workflow for this job: Meeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".

When not to use it

Skip Meeting Notes when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/meeting-notes
# Save SKILL.md to ~/.claude/skills/meeting-notes/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/meeting-notes/SKILL.md. For a shared project, commit the folder at .claude/skills/meeting-notes/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Meeting Notes skill for this task: Read DESIGN.md. Confirm any required inputs or files before making changes.

What supports this recommendation?

74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
80/100
Practical detail
74/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Meeting Notes Skill

Produce a single-screen meeting notes page.

## Workflow

1. Read DESIGN.md. 2. Layout: - Header: meeting title, date, time, location/Zoom, attendees row. - Agenda checklist (4–6 items). - Decisions panel — bulleted list with strong styling. - Action items table with owner, due date, status. - "Open questions" + "next meeting" footer. 3. Subdued colour palette, clear hierarchy.

## Output contract

``` <artifact identifier="notes-name" type="text/html" title="Meeting Notes"> <!doctype html>...</artifact> ```

Intended uses

  • Read DESIGN.md.
  • Layout:
  • Header: meeting title, date, time, location/Zoom, attendees row.
  • Agenda checklist (4–6 items).
  • Decisions panel — bulleted list with strong styling.
  • Action items table with owner, due date, status.
  • "Open questions" + "next meeting" footer.
  • Subdued colour palette, clear hierarchy.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.