pm-call
Skill0 starsChanged 33 days agoMITView on GitHub
Turns a meeting transcript into a note and a list of decisions. Use when the user has put a file in raw/ and asks to process the meeting, says "process this call", "разбери звонок", "обработай встречу", or runs /pm-call.
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 3 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Read index.md and the active topics in topics/ to work out what the meeting relates to.
- Very specific: line 17
Read the file in raw/ in full.
- Very specific: line 20
Create a note in calls/ with the same name as the source:
- Very specific: line 35
Add a line to the "Log" section of the topic the meeting relates to.
- Very specific: line 36
If no topic fits, offer to open one with /pm-topic.
- Very specific: line 37
Add the new files to index.md.
- Very specific: line 42
Don't change the file in raw/.
- Distinctive: line 43
Every claim carries a link to its source.
- Distinctive: line 44
Don't invent what isn't in the transcript.
- Distinctive: line 45
Leave quoted speech in the language it was said in.
≈ “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
Process a meeting
Steps
- Read
index.mdand the active topics intopics/to work out what the meeting relates to. - Read the file in
raw/in full. - Name the 3–5 main takeaways and ask which matter and which to drop. Wait for the answer.
Create a note in
calls/with the same name as the source:--- type: call date: 2026-09-19 source: raw/2026-09-19-sync.md status: draft ---Then: who was there, what was discussed, what was decided, what was left open.
- For each decision create a separate file in
decisions/: what was decided, why, and how it is known. - Link the files with
[[file-name]]. - Add a line to the "Log" section of the topic the meeting relates to.
If no topic fits, offer to open one with
/pm-topic. - Add the new files to
index.md. - Report back: how many files you created and what questions are still open.
Rules
- Don't change the file in
raw/. - Every claim carries a link to its source.
- Don't invent what isn't in the transcript. Write an open question instead.
- Leave quoted speech in the language it was said in.
- A fact that is true always, not just this week, should be offered for
context/. Don't write there yourself without confirmation.
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.