SKILLEMALL.ai
GitHub ↗ RU Sign in

BC pmstudio-meeting-notes

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.

coco-research/coco Agent Skills author: coco-research 1 file body ≈ 2 757 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Generate structured meeting notes from transcripts or pasted text.

As a process C 55/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency

GeneratorPersonal productivitytype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
86
Run on models
none yet
Process rating
C
55/100
Has gaps
Inputs and preconditions w 11
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "domain"

    Process rating: all ten parameters 55/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 40Consistency. Frontmatter name (pmstudio-meeting-notes) differs from the folder (meeting-notes)
    • 55Failures and branches. 1 branches
    • 60Tools and files. Uses tools (bash, read, write) that frontmatter does not declare
    • 60Result and completion. Output format stated, no completion criterion
    • 100Steps. 49 steps
    • 100Execution cost. Instruction body is 2757 tokens
    • 100Running it twice. Mutating operations check current state

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • -5TODO / placeholder text left in the skill
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 459: enough signal without eating the budget
    • +4Structure: 17 headings
    • +3Step-by-step instructions: 49 items
    • +3Output format is stated explicitly
    • +4Has examples (2 code blocks)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.