Skip to content
cccskills
FreePublished on GitHub

meeting-notes

Turn rough meeting notes or a transcript into a structured recap with decisions, assigned tasks, stated deadlines, and open questions. Include a brief summary and flag missing or uncertain details so readers can identify the next steps.

OriginalShow the original description

Turn raw notes or a transcript into a clean summary with decisions and action items.

See how to install

Good for

  • Turn rough meeting notes into a shareable recap
  • Extract tasks with owners and stated deadlines
  • Track unresolved questions after a discussion
  • Share decisions with people who missed the meeting

Files included (1)

  • SKILL.md2.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Meeting Notes

Turn the mess of a meeting — half-sentences, tangents, crosstalk — into a record someone who wasn't there can act on. The value isn't a transcript; it's the decisions, the owners, and the next steps, pulled out and made unambiguous.

When to use this skill

Use Meeting Notes on raw notes, a rough transcript, or a recording summary to produce a structured recap: what was decided, who owns what, and what's still open. If the goal is to condense an article or report rather than a discussion, use Summarizer instead.

What a good recap captures

  • Decisions — what the group actually agreed, stated plainly. Distinguish a decision from a suggestion that went nowhere.
  • Action items — each with an owner and, where stated, a due date. An action with no owner is a wish; assign it or flag it as unassigned.
  • Open questions — things raised but not resolved, so they don't quietly vanish.
  • Context — just enough of the "why" that a decision doesn't read as arbitrary later.

Principles

  • Signal over transcript. Don't replay the conversation — extract what matters and drop the rest.
  • Attribute carefully. Only assign an owner or a decision if the input actually supports it. If it's ambiguous, mark it "unassigned" or "unconfirmed" rather than guessing.
  • Never invent. If a date, owner, or decision wasn't stated, say so. Fabricated specifics are worse than an honest gap.
  • Neutral voice. Record what was said, not your opinion of it.

How to work

  1. Read the full input and separate discussion from outcomes.
  2. Pull out decisions, then action items (owner + due date where given), then open questions.
  3. Write a two-to-three sentence summary at the top so a skimmer gets the gist.
  4. Re-check every owner, date, and decision against the source; flag anything you had to infer.

Output format

Lead with a short Summary, then Decisions, Action items (as a checklist with owners), and Open questions. Omit any section that genuinely has nothing in it rather than padding it.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

app-builder-sdk

FreeSummary

Build holaOS apps for connecting external services or managing work through a dashboard. The skill uses shared SDK building blocks for stored records, actions, and synchronization, with the dashboard and agent tools working on the same data.

  • Building an external service integration
  • Creating a CRM dashboard
  • Building a content planning workspace
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

audience-analyst

FreeSummary

Analyze audience demographics and engagement to identify distinct groups, understand what they want, and prioritize valuable segments. Turn those findings into recommendations for content topics, formats, posting times, and tone, while explaining limits in the data.

  • Identify distinct groups within an audience
  • Prioritize groups that engage or convert
  • Plan topics and formats for each audience group
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

Guide an agent through efficient use of an embedded browser by choosing targeted actions, searches, and waits. Reduce repeated tool calls and unnecessary page snapshots, while using more detailed inspection when the target or result remains unclear.

  • Act on known buttons or fields with fewer browser calls
  • Locate a known target on a large page
  • Wait for navigation or downloads to finish
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

browser-qa

FreeSummary

Validate workflows and reproduce issues in an embedded browser. Distinguish application problems from incorrect targets, missing waits, or session state, then report the shortest reliable reproduction steps with only the evidence needed to support the finding.

  • Reproducing a browser workflow failure
  • Checking for regressions after a fix
  • Distinguishing timing issues from application failures
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

build-dashboard

FreeSummary

Build the user interface for a holaOS app whose data resources are already connected through the SDK. Choose a feed, table, kanban board, form, or calendar layout using shared components and workspace styling.

  • Display scheduled items in a chronological feed
  • Show CRM contacts or tickets in a table
  • Organize issues by status on a kanban board
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

Package workspace skills and their required service integrations into one named, installable capability. Create a manifest that references existing skills, install the capability, and report which integrations still need to be connected.

  • Bundle multiple skills for a shared outcome
  • Declare required external service integrations
  • Create a manifest that references existing skills
holaboss-ai/holaOS11.5KUpdated Aug 21, 2026

See all skills by holaboss-ai

Report a problem with this skill