agentleFS
Sign inStart free
Baba01hacker666Baba01hacker666/dummyskills/skills/meeting-notes-to-actions/SKILL.md

meeting-notes-to-actions

Skill0 starsChanged 2 months agoMITView on GitHub

Extracts verified decisions, explicit commitments, and assigned action items from meeting notes.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 14
  2. Very specific:

    Do not use to summarize public documentation.

    line 19
  3. Very specific:

    Do not use to specify detailed technical implementation tasks.

    line 20
  4. Very specific:

    If raw_notes is empty: stop and ask: "Please provide the meeting notes text."

    line 26
  5. Very specific:

    If an action has no named owner in the notes: label owner as [UNASSIGNED - Needs Owner].

    line 27
  6. Very specific:

    If an action has no deadline: label deadline as [Unspecified].

    line 28
  7. Distinctive:

    Follow these numbered actions:

    line 31
  8. Distinctive:

    If two participants disagreed and no consensus was noted: place under "Open Questions", not "Decisions".

    line 42
  9. Distinctive:

    If a task was suggested but not committed to: do not list as an Action Item.

    line 43
  10. Distinctive:

    Stop and ask the user when:

    line 76

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Meeting Notes to Actions

Parses raw meeting notes to extract concrete decisions, owner-assigned action items, deadlines, and unresolved questions. Eliminates vagueness and unowned tasks.

1. Purpose

Turn freeform discussions into accountable outcomes. A "Decision" is an agreed choice. An "Action Item" is a specific task assigned to a named owner with a deadline or clear deliverable.

2. When to Use

Use this skill when:

  • Converting raw transcript or scratch notes from a sync or planning session into structured records.
  • User asks: "Extract action items" or "What did we decide?".

3. When Not to Use

  • Do not use to summarize public documentation; use factual-summarizer.
  • Do not use to specify detailed technical implementation tasks; use task-brief.

4. Required Inputs

  • raw_notes: Unstructured text or bullet points from the meeting (string).

5. Missing-Input Behavior

  1. If raw_notes is empty: stop and ask: "Please provide the meeting notes text."
  2. If an action has no named owner in the notes: label owner as [UNASSIGNED - Needs Owner]. Never invent names.
  3. If an action has no deadline: label deadline as [Unspecified].

6. Procedure

Follow these numbered actions:

  1. Action 1: Extract Agreed Decisions
    • Identify sentences indicating consensus ("Agreed to...", "Decided that...", "Selected X over Y").
  2. Action 2: Extract Action Items
    • For every task, identify: Who (Owner), What (Deliverable), When (Deadline if stated).
  3. Action 3: Extract Open / Unresolved Questions
    • Identify topics explicitly left open or requiring follow-up.
  4. Action 4: Emit Structured Record
    • Format using Section 8.

7. Decision Rules

  • If two participants disagreed and no consensus was noted: place under "Open Questions", not "Decisions".
  • If a task was suggested but not committed to: do not list as an Action Item; list under "Open Questions".

8. Output Format

Emit the meeting outcome using this template:

### Meeting Summary: Decisions & Action Items

#### Key Decisions
- **Decision 1**: [Exact decision made]
- **Decision 2**: [Exact decision made]

#### Action Items
| Owner | Action Item / Deliverable | Due Date |
| :--- | :--- | :--- |
| [Name or UNASSIGNED] | [Specific task description] | [Date or Unspecified] |

#### Open Questions & Follow-ups
- [Question or unassigned topic requiring future discussion]

9. Verification Checklist

  • Every decision corresponds to explicit consensus in the notes.
  • No owner names were fabricated.
  • Action items are actionable deliverables, not vague topics.
  • Ambiguities are categorized as Open Questions.

10. Common Failures and Recovery

Failure SymptomCauseRecovery Action
Fabricating task ownersGuessing who should do itMark as [UNASSIGNED] to force team assignment.
Treating ideas as decisionsConfusing brainstorming with agreementMove speculative statements to Open Questions.

11. Stop or Escalation Conditions

Stop and ask the user when:

  • The supplied notes are completely blank or incomprehensible gibberish.

12. Examples

Example 1: Successful Execution

Input:

Sync notes:
- Dan and Sarah agreed to use PostgreSQL instead of MongoDB.
- Sarah will write the migration script by Friday.
- Need to check with legal if EU data can be stored in us-east. Dan will email legal today.
- Discussed GraphQL vs REST for v2, no conclusion yet.

Output:

### Meeting Summary: Decisions & Action Items

#### Key Decisions
- **Decision 1**: Adopt PostgreSQL as the primary database instead of MongoDB.

#### Action Items
| Owner | Action Item / Deliverable | Due Date |
| :--- | :--- | :--- |
| Sarah | Write database migration script to PostgreSQL | Friday |
| Dan | Email legal team regarding EU data storage in us-east | Today |

#### Open Questions & Follow-ups
- API architecture for v2 (GraphQL vs REST) remains undecided.

Example 2: Ambiguous or Missing Input

Input:

Meeting notes:
- Great discussion about project future.
- Someone should clean up the legacy repo.
- Let's do better next sprint.

Output:

### Meeting Summary: Decisions & Action Items

#### Key Decisions
- None recorded.

#### Action Items
| Owner | Action Item / Deliverable | Due Date |
| :--- | :--- | :--- |
| [UNASSIGNED - Needs Owner] | Clean up legacy repository | [Unspecified] |

#### Open Questions & Follow-ups
- Owner and deadline for legacy repository cleanup must be assigned.

Example 3: Expected Final Output

Output:

### Meeting Summary: Decisions & Action Items

#### Key Decisions
- **Decision 1**: Freeze release candidate v1.4 on Wednesday 5 PM.

#### Action Items
| Owner | Action Item / Deliverable | Due Date |
| :--- | :--- | :--- |
| Alex | Run staging smoke tests and tag release branch | Wednesday 4 PM |
| Maya | Prepare draft release notes | Wednesday noon |

#### Open Questions & Follow-ups
- Pending confirmation on status of PR #402 before code freeze.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free