Writing Livekit Scenarios
livekit-examples/agent-starter-python
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them.
Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it…
Install The Org Simulator
$ npx skills add mohitagw15856/pm-claude-skills --skill the-org-simulator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-org-simulator --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/the-org-simulator .claude/skills/the-org-simulator && 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 "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .claude/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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/the-org-simulatorType 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 the-org-simulator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-org-simulator --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/the-org-simulator .agents/skills/the-org-simulator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .agents/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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 the-org-simulator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-org-simulator --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/the-org-simulator .cursor/skills/the-org-simulator && 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 "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .cursor/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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/the-org-simulator--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 the-org-simulator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills the-org-simulator --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/the-org-simulator .gemini/skills/the-org-simulator && 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 "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .gemini/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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 the-org-simulatorInstalls 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 the-org-simulator -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/the-org-simulator .github/skills/the-org-simulator && 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 "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .github/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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 the-org-simulator -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 the-org-simulator --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/the-org-simulator .opencode/skills/the-org-simulator && 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 "the-org-simulator" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/the-org-simulator into .opencode/skills/the-org-simulator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "the-org-simulator", 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
the-org-simulator- GitHub stars
- 1.4k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 755 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it…
- Works in 5 steps: Simulate seats, not boxes. For each key… → Find the undecideds. The middle managers… → Forecast friction concretely. Not "there… → …
- Planning a reorg
- SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The Org Simulator is an agent skill from mohitagw15856/pm-claude-skills. Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it? Use when planning a reorg, changing reporting lines, merging or splitting teams, moving a function, or 'how will this org change land?'. Produces a winners/losers map, a friction forecast, the leak-test read, and a sequenced announcement plan.
Its SKILL.md is about 1.6k 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 Testing & QA, covering Load testing. 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
- Planning a reorg
- Changing reporting lines
- Splitting teams
- Moving a function
Example prompts
- “how will this org change land?”
- “/the-org-simulator”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Simulate seats, not boxes. For each key person: scope Δ, status Δ
- Find the undecideds. The middle managers and senior ICs who could go
- Forecast friction concretely. Not "there may be resistance" but "the
- Run the leak test. Rewrite the draft announcement's message as
- Sequence the rollout. Order: losers first, privately, from someone
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
The Org Simulator loads about 1.6k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 755 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). 755 words, ~1,558 tokens.
Download SKILL.mdSave it as
.claude/skills/the-org-simulator/SKILL.md (or your agent's skills folder).- name
- the-org-simulator
- description
- Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it? Use when planning a reorg, changing reporting lines, merging or splitting teams, moving a function, or 'how will this org change land?'. Produces a winners/losers map, a friction forecast, the leak-test read, and a sequenced announcement plan.
The Org Simulator Skill
Org changes are designed on the box-and-line level and experienced on the who-do-I-report-to-now level. The gap between those two is where reorgs fail: the map made sense, but the two best engineers quit, the middle managers went quiet, and the memo leaked on Tuesday before the Thursday announcement. This skill simulates the experienced version before the announced version exists — seat by seat for the key people, faction by faction for the rest, plus the one test almost nobody runs: reading the memo as the person it demotes, on a screenshot, out of context.
What This Skill Produces
- A winners / losers / undecided map — by named seat for key people, by group for the rest: what each actually loses or gains (scope, status, access, headcount, identity), not what the memo says they gain
- A friction forecast: the 5–8 specific breakpoints of the first 90 days, each with likelihood, blast radius, and the cheap preventative
- The leak test: the announcement read as a screenshot by its least charitable reader, plus what the corridor version of it will say by Friday
- A sequenced rollout plan: who hears it in which order, from whom, with the one question each conversation must answer
Required Inputs
Ask for (if not already provided):
- The change: current structure → proposed structure, and the honest why (the memo-why and the real-why, if different — the simulation needs both)
- The key seats affected: names/roles, current scope, and what's known of their ambitions and frustrations
- History that shapes reception: previous reorgs and how they went, standing rivalries, recent departures
- Timing and constraints: what's fixed, what's still movable, who already knows
Process
- Simulate seats, not boxes. For each key person: scope Δ, status Δ (title, audience, room access), boss Δ, identity Δ ("am I still the platform person?"). Losses count double — people fight losses harder than they chase gains. Mark each seat: champion / accepter / quiet-resister / flight-risk, with the because.
- Find the undecideds. The middle managers and senior ICs who could go either way decide reorg outcomes; list who they'll ask about it in the first 24 hours — those people, not the memo, are the actual communication channel.
- Forecast friction concretely. Not "there may be resistance" but "the two platform leads now share one headcount pool and will collide at Q3 planning". For each: likelihood, blast radius, the cheap preventative available before announcement (a scope clarification, a title fix, a pre-conversation).
- Run the leak test. Rewrite the draft announcement's message as received by its least charitable reader from a screenshot with no context, no Q&A, no follow-up meeting. If the leaked version is fatal, the announcement isn't ready. Then write the corridor version — the one sentence people will actually repeat — and check it's survivable.
- Sequence the rollout. Order: losers first, privately, from someone they trust (hearing it in the all-hands is how flight-risks convert) → undecideds' influencers → champions armed with the honest FAQ → everyone. Each conversation gets the one question it must answer for that hearer. Pressure-test the final plan against [[machiavelli-counsel]]'s friends-of- the-old-order column if politics run deep.
Show full SKILL.md (244 more words)Show less
Output Format
## The change in one line (memo-why · real-why)
## Seat map
| Seat | Scope Δ | Status Δ | Reads as | Champion/Accepter/Resister/Flight-risk | Because |
## The undecided middle
[Who they are · who they'll ask in the first 24h]
## Friction forecast — first 90 days
| # | Breakpoint (specific) | Likelihood | Blast radius | Cheap preventative |
## Leak test
[The screenshot read, least charitable voice · the corridor sentence ·
verdict: survivable / fix before announcing]
## Rollout sequence
| Order | Who | From whom | The one question this conversation must answer |Quality Checks
- Every key seat's read includes a because grounded in scope/status/ identity — no one is labelled a resister without a stated loss
- At least one friction item the user hadn't foreseen (probe the shared- resource collisions and the title deltas — that's where they hide)
- The leak test uses the least charitable reading, not the intended one, and issues a verdict
- Losers hear it first and privately in the rollout, or the plan argues explicitly why not
- The simulation stays a planning tool: predictions are labelled as predictions about reactions, not verdicts on people
Anti-Patterns
- Do not simulate boxes ("Team A reports to B") — simulate Tuesday morning for the person whose title just got shorter
- Do not let the memo-why hide the real-why from the simulation; people react to the real-why they infer, not the memo-why they're given
- Do not use the seat map as a loyalty dossier — it plans communication, not retaliation; decline that turn if asked
- Do not skip the leak test because "it won't leak" — the test costs ten minutes and reorg memos leak at a rate that rounds to always
- Do not end without the preventatives — a friction forecast with no cheap fixes is just organized dread
Related
[[machiavelli-counsel]] for the power analysis under this; [[change-management-plan]] for the full formal program; [[stakeholder-influence-mapper]] for the influence graph the rollout sequence rides on.
Example Trigger Phrases
- "Plan a reorg."
- "Split teams."
- "Move a function."
- "How will this org change land?"
© 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/the-org-simulator of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
The Org Simulator 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 |
|---|---|---|---|---|---|---|
| The Org Simulator this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Writing Livekit Scenarioslivekit-examples/agent-starter-python | 264 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Go Testingcxuu/golang-skills | 173 | 1 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Goalcraftgrp06/goalcraft | 102 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Thinking Partnermattnowdev/thinking-partner | 206 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Visionkunchenguid/vision | 331 | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Go Testing
cxuu/golang-skills
A skill your agent uses when writing, reviewing, or improving Go test code — including table-driven tests, subtests, parallel tests, test helpers, test doubles, and assertions with cmp.Diff.
Goalcraft
grp06/goalcraft
Turn a rough draft, vague ambition, or messy task brief into a powerful Codex /goal objective for persistent, evidence-checked work.
Thinking Partner
mattnowdev/thinking-partner
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly.
Vision
kunchenguid/vision
Draft and stress-test a VISION.md for a repository, then iterate with the author on an interactive review board until approved.
Volt Load Testing
owenHochwald/volt
Safely exercise and evaluate HTTP APIs with the Volt CLI, including authenticated requests, JSON bodies, staged load, machine-readable results, performance baselines, and before/after comparisons.
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 The Org Simulator
What does The Org Simulator do?
Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it…. The Org Simulator is an agent skill from mohitagw15856/pm-claude-skills. Stress-test a proposed org change before announcing it — simulate who gains, who loses, who blocks, where friction erupts in the first 90 days, and run the memo leak test: how does this land when it leaks before you announce it?
When should I use The Org Simulator?
The Org Simulator fits situations like: planning a reorg; changing reporting lines; splitting teams; moving a function.
How do I install The Org Simulator in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill the-org-simulator -a claude-code`. Or copy the skill folder (skills/the-org-simulator in mohitagw15856/pm-claude-skills) into .claude/skills/the-org-simulator in your project. Claude Code loads it when a task matches its description.
How do I install The Org Simulator in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill the-org-simulator -a codex`. Or copy the skill folder (skills/the-org-simulator in mohitagw15856/pm-claude-skills) into .agents/skills/the-org-simulator in your project. Codex loads it when a task matches its description.
Can I use The Org Simulator 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 the-org-simulator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/the-org-simulator, .gemini/skills/the-org-simulator, .github/skills/the-org-simulator and .opencode/skills/the-org-simulator in your project.
What does The Org Simulator need to run?
SKILL.md names no scripts, command-line tools or credentials: The Org Simulator is instructions for the agent only.
Does The Org Simulator 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 The Org Simulator 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 The Org Simulator use?
The Org Simulator 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 The Org Simulator use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 The Org Simulator?
Skills that share tags, products or a category with The Org Simulator: Writing Livekit Scenarios (livekit-examples/agent-starter-python, 264 stars), Go Testing (cxuu/golang-skills, 173 stars), Goalcraft (grp06/goalcraft, 102 stars) and Thinking Partner (mattnowdev/thinking-partner, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains The Org Simulator?
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.