CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting_notes

Structure raw meeting notes into actionable minutes with follow-ups.

Invalid
This skill can't be scored yet
Validation errors are blocking scoring. Review and fix them to unlock Quality, Impact and Security scores. See what needs fixing →
SKILL.md
Quality
Evals
Security

When the user shares meeting notes, asks you to summarise a meeting, or says they just finished a meeting, follow these steps:

  1. Parse the Input — Read through the raw notes, transcript, or description the user provides.
  2. Identify Participants — List everyone mentioned or involved.
  3. Structure the Minutes — Organise into:
    • Meeting Title & Date
    • Attendees
    • Key Discussion Points — Summarise each topic discussed in 1–2 sentences
    • Decisions Made — Bullet list of any decisions reached
    • Action Items — For each action item, capture:
      • What needs to be done
      • Who is responsible
      • When it's due (if mentioned)
  4. Save to Knowledge Graph — Store action items, decisions, and key facts to memory. Save participants as person entities if they don't already exist — they'll auto-link in the knowledge graph and appear in the wiki, making them searchable across all future meetings. Use descriptive subjects like Team Standup Actions — March 28. Link action items to the people responsible.
  5. Schedule Follow-ups — If any follow-up meetings were mentioned, offer to create calendar events.
  6. Present — Output the structured minutes in a clean, skimmable format.

Keep the language professional but concise. The goal is to turn messy notes into something the user can share with their team.

Repository
siddsachar/row-bot
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.