Post Call
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".
Install
$ agentstack add skill-chacosoldier-compabob-post-call ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-chacosoldier-compabob-post-call) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-.md. - Update each attendee's
vault/People/.md: append to## Interactions, refresh their current focus. - Update the relevant project or pipeline 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: chacosoldier
- Source: chacosoldier/compabob
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.