pmstudio-meeting-notes SKILL.md skillA
pmstudio-meeting-notes from coco-research/coco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coco-research/coco/pmstudio-meeting-notes@git:20260802.1479e32Pins git:20260802.1479e32 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coco-research/coco
- Path
skills/meeting-notes/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260802.1479e32, committed Aug 2, 2026
- First version recorded
- Apr 26, 2026
- Size
- 11,612 bytes
- Repository stars
- 797
- License
- a license file GitHub does not identify
Generate structured meeting notes from transcripts or pasted text. Use when someone says "meeting notes", "process this transcript", "summarize this call", "notes from today's meeting", or pastes/references a meeting transcript. Auto-enriches attendees from stakeholder directory, routes output to correct project subfolder, flags downstream artifact impacts (PRD, deck, architecture), and proposes CLAUDE.local.md updates. Produces date-first Markdown files.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Meeting Notes — Transcript-to-Artifact Generator ## Purpose Transforms raw meeting transcripts (pasted text, audio transcription output, or file references) into structured, stakeholder-enriched meeting notes. Not generic summaries — these cross-reference project context, known stakeholders, and existing artifacts to produce notes that integrate into the project's documentation ecosystem. ## Process ### Step 1: Determine Input Source From user request: | Input | How to Handle | |-------|---------------| | Transcript pasted in chat | Process directly | | File path provided | Read the file | | `/pmstudio-meeting-notes <path>` | Read file at path | | `/pmstudio-meeting-notes <path> <output-dir>` | Read file, write to specified directory | | No transcript provided | Ask: "Paste the transcript or provide a file path" | ### Step 2: Read Project Context **Always read (skip any that don't exist):** 1. **`CLAUDE.local.md`** — critical for: - Folder structure & routing guide (determines where to save notes) - Recent Changes (avoid duplicating known information) - Key Decisions (cross-reference decisions mentioned in transcript) …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/pmstudio-meeting-notes@sha256:1de13502f6a68ad1The line at the top of this page pins the label git:20260802.1479e32, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_27xts7ynxjkwfbrv)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 26, 2026 and Aug 2, 2026, about one every 99 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260802.1479e32 latest | 2026-08-02 | 1479e32 | 11,612 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 11,601 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11612 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
coco-research/coco · 797 stars · license a license file GitHub does not identify · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_27xts7ynxjkwfbrv GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/pmstudio-meeting-notes GET https://markdownregistry.com/api/v1/blob/1de13502f6a68ad1d1ed79e22f2de81dd6aea7be18419855f8fe20ae3e19a831
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.