agent-launcher-orchest…
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when preparing an all-hands, investor update, recruiting pitch or crisis message, or when stories told to different audiences drift apart. Keeps one company story and flags contradictions.
Claude Code
$ npx -y skills add alirezarezvani/claude-skills --skill internal-narrative --agent claude-code
Codex
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a codex -y
Cursor
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a cursor -y
Gemini CLI
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a gemini-cli -y
GitHub Copilot
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a github-copilot -y
OpenCode
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a opencode -y
Windsurf
$ npx skills add alirezarezvani/claude-skills --skill internal-narrative -a windsurf -y
name: "internal-narrative" description: "Use when preparing an all-hands, investor update, recruiting pitch or crisis message, or when stories told to different audiences drift apart. Keeps one company story and flags contradictions." license: MIT metadata: version: 1.0.0 author: Alireza Rezvani category: c-level domain: narrative-strategy updated: 2026-03-05 frameworks: narrative-frameworks, all-hands-template
One company. Many audiences. Same truth — different lenses. Narrative inconsistency is trust erosion. This skill builds and maintains coherent communication across every stakeholder group.
narrative, company story, internal communication, investor update, all-hands, board communication, crisis communication, messaging, storytelling, narrative consistency, audience translation, founder narrative, employee communication, candidate narrative, partner communication
**The same fact lands differently depending on who hears it and what they need.**
"We're shifting resources from Product A to Product B" means:
Same fact. Four different narratives needed. The skill is maintaining truth while serving each audience's actual question.
---
One paragraph that every other communication derives from. This is the source of truth.
**Core narrative template:** > [Company name] exists to [mission — present tense, specific]. We're building [what you're building] because [the problem you're solving]. Our approach is [your unique way of doing this]. We're at [honest description of current state] and heading toward [where you're going in concrete terms].
**Good core narrative (example):** > Acme Health exists to reduce preventable falls in elderly care using smartphone-based mobility analysis. We're building an AI diagnostic tool for care teams because current fall risk assessments are subjective, infrequent, and often wrong. Our approach — using the phone's camera during a 10-second walking test — means no new hardware, no specialist required. We have 80 care facilities in DACH paying us €800K ARR, and we're heading to €3M ARR by demonstrating clinical value at scale before our Series B.
**Bad core narrative:** > Acme Health is an innovative AI company revolutionizing elderly care through cutting-edge technology that empowers care providers and improves patient outcomes across the continuum of care.
The good version is usable. The bad version says nothing.
---
Take the core narrative and translate it for each audience. Same truth, different frame.
| Fact | Employees need to hear | Investors need to hear | Customers need to hear | Candidates need to hear | |------|----------------------|----------------------|----------------------|------------------------| | We have 80 customers | "We've proven the model — your work matters" | "Product-market fit signal, capital efficient" | "80 care facilities trust us" | "Traction you'd be joining" | | We pivoted from hardware | "We were honest enough to change course" | "Capital-efficient pivot to better unit economics" | "We found a faster, simpler way to serve you" | "We make decisions based on evidence, not ego" | | We missed Q2 revenue | "Here's why, here's the plan, here's what you can do" | "Revenue mix shifted — trailing indicator improving" | [Usually don't tell customers revenue misses] | [Usually not shared externally] | | We're hiring fast | "The team is growing — your network matters" | "Headcount plan aligned to growth" | [Not relevant unless it affects service] | "This is a rocket ship moment" |
**Rules:**
---
Before any major communication, run the contradiction check:
**Question 1:** What did we tell investors last month about [topic]? **Question 2:** What did we tell employees about the same topic? **Question 3:** Are these consistent? If not — which version is true?
**Common contradictions:**
**When you catch a contradiction:** Fix the less accurate version, then communicate the correction explicitly. "Last month I said X. After more reflection, X is not quite right. Here's the clearer version."
Correcting yourself before someone else catches it builds more trust than getting caught.
---
| Audience | Format | Frequency | Owner | |----------|--------|-----------|-------| | Employees | All-hands | Monthly | CEO | | Employees | Team updates | Weekly | Team leads | | Investors | Written update | Monthly | CEO + CFO | | Board | Board meeting + memo | Quarterly | CEO | | Customers | Product updates | Per release | CPO / CS | | Candidates | Careers page + interview narrative | Ongoing | CHRO + Founders | | Partners | Quarterly business review | Quarterly | BD Lead |
---
See `templates/all-hands-template.md` for the full template.
**Principles:**
411 production-ready skills for Claude Code and 12 other coding agents, covering engineering, product, marketing, compliance, finance and the C-suite. We test whether each skill loads when you ask in plain words, and publish the results.
Use when someone wants to build, launch, grade or schedule a Claude Managed Agent in their own Anthropic account ('build me an…
Use when a launched managed agent needs grading against a rubric and improving ('grade my agent', 'is it good enough'). Builds…
Use when someone has an agent idea to scope before launch ('help me scope an agent'). Interviews them about the one job and…
Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates…
Use when a managed-agent build sheet is ready to launch ('launch it', 'deploy the agent'). Generates and validates API payloads…
Use when closing out a launched managed agent ('wrap up', 'what do I own now'). Inventories primitives with…
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid…
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI…