Budget And Fee Manager Scott Margetts
lawve-ai/awesome-legal-skills
Matter budgeting and ongoing WIP/variance monitoring. An agent skill from lawve-ai/awesome-legal-skills.
Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief.
Install Post Event Debrief
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debrief --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/post-event-debrief .claude/skills/post-event-debrief && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .claude/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debriefType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debrief --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/post-event-debrief .agents/skills/post-event-debrief && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .agents/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debrief --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/post-event-debrief .cursor/skills/post-event-debrief && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .cursor/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/post-event-debrief--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debrief --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/post-event-debrief .gemini/skills/post-event-debrief && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .gemini/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debriefInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/post-event-debrief .github/skills/post-event-debrief && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .github/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills post-event-debrief --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/post-event-debrief .opencode/skills/post-event-debrief && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "post-event-debrief" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/post-event-debrief into .opencode/skills/post-event-debrief/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "post-event-debrief", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
post-event-debrief- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 757 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief.
- Works in 7 steps: Start with the objectives and the… → Reconstruct the actual timeline. Against… → Separate the stressful from the broken.… → …
- Asked to run a post-event debrief
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Numbers First, Then… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Post Event Debrief is an agent skill from mohitagw15856/pm-claude-skills. Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief. Use when asked to run a post-event debrief, write an event wrap report, review how an event went, or capture lessons learned after a conference, launch, or wedding. Produces the outcome scorecard against the original objectives, the timeline of what actually happened, the root causes separated from symptoms, supplier performance, and…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR, covering Root cause analysis. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to run a post-event debrief
- Write an event wrap report
- Review how an event went
- Capture lessons learned after a conference
Example prompts
- “/post-event-debrief”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Start with the objectives and the numbers. Before opinion enters the room. An event that felt chaotic and hit every objective is a…
- Reconstruct the actual timeline. Against the run of show. Slippage is visible here in a way it never is in recollection.
- Separate the stressful from the broken. Plenty of things feel terrible and harm nothing; some quiet failures matter enormously. Do not…
- Trace each problem to its decision. The AV failure at 19:00 usually traces to a supplier chosen in March or an access time agreed in…
- Collect individual accounts before the group meets. Otherwise you get one narrative, shaped by whoever speaks first.
- Record supplier performance specifically. 'Good' is useless in twelve months; 'crew arrived 90 minutes late, recovered without impact…
- Write fixes as instructions to the next brief. 'Load-in must start 4 hours before doors' belongs in the next brief. 'Load-in was rushed'…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Post Event Debrief loads about 1.5k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 757 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 757 words, ~1,481 tokens.
Download SKILL.mdSave it as
.claude/skills/post-event-debrief/SKILL.md (or your agent's skills folder).- name
- post-event-debrief
- description
- Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief. Use when asked to run a post-event debrief, write an event wrap report, review how an event went, or capture lessons learned after a conference, launch, or wedding. Produces the outcome scorecard against the original objectives, the timeline of what actually happened, the root causes separated from symptoms, supplier performance, and the changes written into the next event's brief.
Post-Event Debrief
Most event debriefs produce a feelings-based list nobody reads before the next event, and the same three problems recur annually. This separates what went wrong from what merely felt stressful, traces each problem to the decision that caused it — usually made weeks earlier — and writes the fixes into the next brief rather than into a document that gets filed.
What This Skill Produces
- The outcome scorecard — performance against the objectives set before the event, not against how it felt
- The actual timeline — what really happened versus the run of show, with the slippage visible
- Root causes — each problem traced back to the decision or omission that produced it
- Supplier performance — a record specific enough to be useful at the next procurement
- The budget out-turn — final versus budget, with the variances explained
- Changes into the next brief — the fixes, written as instructions to the next event rather than observations about this one
Required Inputs
Ask for these if not provided:
- The original objectives — what this event was supposed to achieve, from the brief
- The numbers — attendance versus target, budget versus out-turn, and any measured outcomes such as leads, funds raised, or satisfaction
- What happened — the actual timeline, incidents, and deviations from plan
- Feedback — attendee, client, staff and supplier, and how it was gathered
- The team's account — what each person found hard, gathered before the group discussion so it is not shaped by the loudest voice
Framework: Numbers First, Then Causes, Then the Next Brief
- Start with the objectives and the numbers. Before opinion enters the room. An event that felt chaotic and hit every objective is a different problem from one that felt smooth and missed them.
- Reconstruct the actual timeline. Against the run of show. Slippage is visible here in a way it never is in recollection.
- Separate the stressful from the broken. Plenty of things feel terrible and harm nothing; some quiet failures matter enormously. Do not confuse adrenaline with evidence.
- Trace each problem to its decision. The AV failure at 19:00 usually traces to a supplier chosen in March or an access time agreed in April. Debriefing the symptom changes nothing.
- Collect individual accounts before the group meets. Otherwise you get one narrative, shaped by whoever speaks first.
- Record supplier performance specifically. 'Good' is useless in twelve months; 'crew arrived 90 minutes late, recovered without impact, communicated well' is procurement evidence.
- Write fixes as instructions to the next brief. 'Load-in must start 4 hours before doors' belongs in the next brief. 'Load-in was rushed' belongs nowhere.
Output Format
Show full SKILL.md (328 more words)Show less
Event debrief: [event] · [date] · [debrief date]
Objectives vs outcome
| Objective (from the brief) | Target | Actual | Met |
|---|
Numbers: attendance [actual/target] · budget [out-turn/budget] · [other measured outcomes]
What actually happened
| Planned | Actual | Variance | Effect |
|---|
Problems — traced
| What went wrong | Felt bad or was bad? | Root cause (the earlier decision) | Fix |
|---|
Supplier performance
| Supplier | Delivered as briefed | Specific notes | Use again |
|---|
Budget out-turn: [budget] → [actual] · Variances over [threshold]: [line — amount — why]
Feedback: attendees [summary, method, n] · client [summary] · team [summary] · suppliers [summary]
What worked and must be kept: [the things to deliberately repeat, which debriefs usually forget to record]
Into the next brief — written as instructions
- [specific instruction] — owner [name]
- [specific instruction] — owner [name]
Quality Checks
- Objectives and numbers are reviewed before any discussion of how it felt
- The actual timeline is reconstructed against the plan
- Each problem is classified as felt-bad or was-bad
- Root causes point at earlier decisions, not at the moment of failure
- Individual accounts were collected before the group session
- Supplier notes are specific enough to be useful at next procurement
- What worked is recorded, not only what failed
- Fixes are written as instructions into the next brief, with owners
Anti-Patterns
- Debriefing on feelings alone. The stressful and the harmful are not the same set.
- Fixing symptoms. The AV failure was a March procurement decision; changing the cable supplier fixes nothing.
- Group discussion first. Produces one story, usually the most confident person's.
- 'Supplier was fine.' Useless as evidence a year later.
- Recording only failures. What worked is how you keep it working.
- A lessons-learned document nobody opens. If it is not in the next brief, it did not happen.
- Debriefing three weeks later. Detail is gone, and only the emotional peaks remain.
Example Trigger Phrases
- "Run a debrief for last week's conference"
- "Write an event wrap report for the client"
- "How do I stop the same problems happening at every event?"
- "Capture lessons learned from our launch event"
- "What should we change for next year's gala?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/post-event-debrief of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Post Event Debrief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Post Event Debrief this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Budget And Fee Manager Scott Margettslawve-ai/awesome-legal-skills | 847 | — | ~6.7k | Automated safety check: Pass | Apache-2.0 | |
| Backtest DiagnosisHKUDS/Vibe-Trading | 35k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Process Mapperalirezarezvani/claude-skills | 28k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Operational RiskJoelLewis/finance_skills | 206 | — | ~7.4k | Automated safety check: Pass | MIT | |
| CAPA Officerdavila7/claude-code-templates | 33k | 1 repos | ~2k | Automated safety check: Pass | MIT |
Similar skills
Backtest Diagnosis
HKUDS/Vibe-Trading
Finds why a trading backtest crashed or gave odd results, sorts the cause into a runtime, logic or data error, fixes the code and checks the rerun metrics.
Process Mapper
alirezarezvani/claude-skills
A skill your agent uses when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff…
Operational Risk
JoelLewis/finance_skills
Guide identification, measurement, and management of operational risk in trading and brokerage operations.
CAPA Officer
davila7/claude-code-templates
Guides corrective and preventive action (CAPA) work in a quality management system, from initiation and root cause analysis through effectiveness verification.
Brand Discovery
affaan-m/ECC
Run a structured, resumable multi-session brand identity interview across 8 modules (purpose, positioning, audience, personality, voice, narrative, founder tension) using laddering, 5 Whys, and…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Post Event Debrief
What does Post Event Debrief do?
Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief. Post Event Debrief is an agent skill from mohitagw15856/pm-claude-skills. Run an event debrief that changes the next event — what the numbers say, what actually went wrong versus what felt stressful, and the specific changes carried into the next brief.
When should I use Post Event Debrief?
Post Event Debrief fits situations like: asked to run a post-event debrief; write an event wrap report; review how an event went; capture lessons learned after a conference.
How do I install Post Event Debrief in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a claude-code`. Or copy the skill folder (skills/post-event-debrief in mohitagw15856/pm-claude-skills) into .claude/skills/post-event-debrief in your project. Claude Code loads it when a task matches its description.
How do I install Post Event Debrief in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a codex`. Or copy the skill folder (skills/post-event-debrief in mohitagw15856/pm-claude-skills) into .agents/skills/post-event-debrief in your project. Codex loads it when a task matches its description.
Can I use Post Event Debrief in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill post-event-debrief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/post-event-debrief, .gemini/skills/post-event-debrief, .github/skills/post-event-debrief and .opencode/skills/post-event-debrief in your project.
What does Post Event Debrief need to run?
SKILL.md names no scripts, command-line tools or credentials: Post Event Debrief is instructions for the agent only.
Does Post Event Debrief access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Post Event Debrief safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Post Event Debrief use?
Post Event Debrief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Post Event Debrief use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Post Event Debrief?
Skills that share tags, products or a category with Post Event Debrief: Budget And Fee Manager Scott Margetts (lawve-ai/awesome-legal-skills, 847 stars), Backtest Diagnosis (HKUDS/Vibe-Trading, 35k stars), Process Mapper (alirezarezvani/claude-skills, 28k stars) and Operational Risk (JoelLewis/finance_skills, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Post Event Debrief?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.