Meeting Notes Skill for Muse
Turn meeting transcripts into clear, actionable notes.
- What
- Turn meeting transcripts into clear, actionable notes.
- Cost
- Free
- Needs
- none beyond standard skill tooling — no external services, APIs, or accounts. You bring the raw notes or transcript.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Turns raw notes and transcripts into structured meeting documentation: 4 templates (standard, standup, client, project review), extraction guidelines that catch action items, decisions, owners, and deadlines instead of just summarizing, plus format and detail-level options and a fully worked example showing the before-and-after. Discovered via skills.sh. Honest note: its metadata mentions an optional `create_docx` office integration that is not required — the skill works fully as plain text. Content is in English. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @claude-office-skills.
Version:
Install
Prerequisites: none beyond standard skill tooling — no external services, APIs, or accounts. You bring the raw notes or transcript. Install "Meeting Notes Skill for Muse" for me. Turn my raw meeting notes or transcripts into structured documentation — 4 templates, extracted action items, decisions, owners, and deadlines. Repository: https://github.com/claude-office-skills/skills/blob/main/meeting-notes/SKILL.md 1. Fetch the SKILL.md file from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code; credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "meeting-notes". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. come with raw notes or a transcript plus the meeting type). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.