post-call
Skill34 starsChanged 23 days agoMITView on GitHub
Capture a debrief right after a meeting or call: what was decided, what was committed, and what changed. Use for \"/post-call\", \"debrief the call with X\", or \"I just got off a call with Y\".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- guerrilla2799/sdr-copilottheir own version, first seen Oct 20, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- guerrilla2799/sdr-copilot★ 1same 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 repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-agentSkill
- build-listSkill
- chart-tufteSkill
- councilSkill
- design-precheckSkill
- document-exportSkill
- handoverSkill
- index-memorySkill
- log-decisionSkill
- mcp-debugSkill
- meeting-prepSkill
- memory-debtSkill
- merge-contactsSkill
- morning-briefSkill
- reflectSkill
- setupSkill
- system-auditSkill
- tasksSkill
- visual-explainerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Gather: Ask the user for the raw account of the call, or work from notes or a transcript they provide.
- Very specific: line 19
Write or update the meeting note vault/Meetings/YYYY-MM-DD-<slug>.md.
- Very specific: line 20
Update each attendee's vault/People/<Name>.md: append to ## Interactions, refresh their current focus.
- Distinctive: line 21
Update the relevant project or pipeline note.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Post-Call Debrief
Close the loop that /meeting-prep opens. Turn a finished conversation into durable vault state.
Steps
- Gather. Ask the user for the raw account of the call, or work from notes or a transcript they provide.
- Extract four things:
- Decisions: what was actually decided.
- Action items: who owes what, by when. Run these through the
second-braintask intake gate so they do not duplicate existing tasks. - New information: anything that changes what the vault knows about a person, account, or project.
- Follow-up: the next touchpoint, if any.
- Update the vault.
- Write or update the meeting note
vault/Meetings/YYYY-MM-DD-<slug>.md. - Update each attendee's
vault/People/<Name>.md: append to## Interactions, refresh their current focus. - Update the relevant project or pipeline note.
- Write or update the meeting note
- Confirm the changes with the user before writing anything that overwrites existing content.
Output
A short summary first: the one decision or change that matters most. Then the meeting note content for review. Then the list of vault files that will be created or updated, for approval.
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.