← Back to articlesSkills and MCP

How do you make a meeting-notes skill repeatable and testable?

Write reusable meeting-note rules, then test the same rules on different examples.

The short answer

The focus here is revising and retesting a procedure rather than making another set of minutes. Start with text instructions, without scripts.

Try it in three steps

  • Write practice notes containing an unresolved discussion.
  • Define three output sections with source locations.
  • Retest (checking again using the same steps) on different notes and inspect assigned responsibilities.

A practice prompt

Before you start

This exercise packages reusable rules rather than repeating meeting classification. Draft a text skill and test two inputs.

Practice material (fictional)

A: Monday checking agreed, owner Sample Chen. B: Monday checking suggested, owner undecided.

Replace placeholders in the prompt with this material, or append the material if there are no placeholders. Reading time excludes doing the exercise.

Write skill rules: only explicit decisions go in decisions, action items need source sentences, and unknown owners stay unknown.

What to look for (not a recorded test result)

The same skill should treat A as a decision and B as discussion. If B is promoted, fix the reusable rule and retest both, not just one answer.

If it goes wrong

If a suggestion becomes a decision, add that failure as a counterexample.

Check your result

Two different note sets retain unresolved issues without invented owners or deadlines.

References and scope

The links below support the concepts or product navigation. The steps and exercises are our teaching suggestions, not official certification or measured customer outcomes. Product interfaces and availability may change. References checked on 2026-10-17.

Start with one task

Describe the current process and its slowest step. The initial conversation is free.

Let’s talk ↗
Need help? See small-scale implementation services ↗

Keep reading