meeting-to-actions
Skill0 starsChanged 51 days agoMITView on GitHub
Extract decisions and owner-tagged actions from a supplied transcript without inventing deadlines or sending assignments.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Sach1ng/PM-operating-OStheir own version, first seen Nov 1, 2026
- donnybacondigital-debug/claude-code-business-kittheir own version, first seen Oct 13, 2026
- tmusser/context-to-action-skillstheir own version, first seen Sep 16, 2026
- benngarnish/sage-free-skillstheir own version, first seen Jul 25, 2026
- moses607/skillforgetheir own version, first seen Jul 14, 2026
- ianklassen/ai-pm-systemtheir own version, first seen Apr 12, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Sach1ng/PM-operating-OS★ 3same name
- tmusser/context-to-action-skills★ 2same name
- ianklassen/ai-pm-system★ 1same name
- benngarnish/sage-free-skills★ 0same name
- donnybacondigital-debug/claude-code-business-kit★ 0same name
- moses607/skillforge★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- content-qaSkill
- eval-engineering-liteSkill
- evidence-contentSkill
- failure-analyzerSkill
- faq-builderSkill
- project-handoffSkill
- requirement-clarifierSkill
- research-synthesizerSkill
- workflow-plannerSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Create a reviewable meeting follow-up from transcript evidence.
- Distinctive: line 14
Use when the user supplies a transcript or notes and wants action items, not an automatic outbound message.
- Very specific: line 28
Keep owner and due date unknown unless stated or clearly resolved in the transcript.
- Very specific: line 34
If attribution is ambiguous, mark the owner unknown.
- Very specific: line 42
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting to Actions
Purpose
Create a reviewable meeting follow-up from transcript evidence.
When to Use
Use when the user supplies a transcript or notes and wants action items, not an automatic outbound message.
Inputs
transcript, participants[], meeting_date, optional language.
Outputs
summary, decisions[], actions: [{task,owner,due,evidence_quote,confidence}], unknowns[].
Workflow
- Mark inaudible or contradictory transcript spans instead of smoothing them away.
- Extract only commitments or requests tied to a quoted span.
- Keep owner and due date
unknownunless stated or clearly resolved in the transcript. - Separate decisions from proposals and disagreements.
- Return a draft for human confirmation before any assignment is sent.
Failure Handling
If attribution is ambiguous, mark the owner unknown; if the transcript is incomplete, flag missing context. Never send or schedule automatically.
Example
synthetic_unverified: “Alex will review the sample draft” yields owner Alex and due date unknown.
Tests
Run python3 tests/validate.py from the repository root to check this skill's contract and example provenance. This is a structural test, not model-quality evidence.
Limitations
Transcription errors can propagate; the original recording or participant confirmation may be required.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

