MCPInstall

internal-narrative

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs. Use when preparing investor updates, all-hands presentations, board communications, recruiting narratives, crisis communications, or when user mentions company narrative, messaging consistency, storytelling, all-hands, investor update, or crisis communication.

Installs
549
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/alirezarezvani/claude-skills --skill internal-narrative
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads internal-narrative automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Internal Narrative Builder

One company. Many audiences. Same truth — different lenses. Narrative inconsistency is trust erosion. This skill builds and maintains coherent communication across every stakeholder group.

Keywords

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

Core Principle

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:

  • To employees: "Is my job safe? Why are we abandoning what I built?"
  • To investors: "Smart capital allocation — they're doubling down on the winner"
  • To customers of Product A: "Are they abandoning us?"
  • To candidates: "Exciting new focus — are they decisive?"

Same fact. Four different narratives needed. The skill is maintaining truth while serving each audience's actual question.


Framework

Step 1: Build the Core Narrative

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.


Step 2: Audience Translation Matrix

Take the core narrative and translate it for each audience. Same truth, different frame.

FactEmployees need to hearInvestors need to hearCustomers need to hearCandidates 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:

  • Never contradict yourself across audiences. Different framing ≠ different facts.
  • "We told investors growth, told employees efficiency" is a contradiction. Audit for this.
  • Investors and employees see each other. Board members talk to your team. Candidates google you.

Step 3: Contradiction Detection

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:

  • "Efficient growth" to investors + "we're hiring aggressively" to candidates
  • "Strong pipeline" to investors + "sales is struggling" at all-hands
  • "Customer-first" in culture + recent decisions that clearly prioritized revenue over customer need

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.


Step 4: Audience-Specific Communication Cadence

AudienceFormatFrequencyOwner
EmployeesAll-handsMonthlyCEO
EmployeesTeam updatesWeeklyTeam leads
InvestorsWritten updateMonthlyCEO + CFO
BoardBoard meeting + memoQuarterlyCEO
CustomersProduct updatesPer releaseCPO / CS
CandidatesCareers page + interview narrativeOngoingCHRO + Founders
PartnersQuarterly business reviewQuarterlyBD Lead

Step 5: All-Hands Structure and Cadence

See templates/all-hands-template.md for the full template.

Principles:

  • Lead with honest state of the company. No spin.
  • Connect company performance to individual work: "Here's how what you built contributed to this outcome."
  • Give people a reason to be proud of their choice to work here.
  • Leave time for real Q&A — not curated questions.

All-hands failure modes:

  • CEO speaks for 55 of 60 minutes; Q&A is "any quick questions?"
  • All good news, all the time — employees know when you're not being honest
  • Metrics without context: "ARR grew 15%" without explaining if that's good, bad, or expected
  • Questions deflected: "That's a great point, we should follow up on that" → never followed up

Step 6: Crisis Communication

When the narrative breaks — someone leaves publicly, a product fails, a security breach, a press article.

The 4-hour rule: If something is public or about to be, communicate internally within 4 hours. Employees should never learn about company news from Twitter.

Crisis communication sequence:

Hour 0–4 (internal first):

  1. CEO or relevant leader sends an internal message
  2. Acknowledge what happened factually
  3. State what you know and what you don't know yet
  4. Tell people what you're doing about it
  5. Tell people what they should do if they're asked about it

Hour 4–24 (external if needed):

  1. External statement (press, social) only if the event is public
  2. Consistent with the internal message — same facts, audience-appropriate framing
  3. Legal review if any claims or liability involved

What not to do in a crisis:

  • Silence: letting rumors fill the vacuum
  • Spin: people can detect it and it destroys trust
  • "No comment": says "we have something to hide"
  • Blaming: even if someone else caused the problem, your audience only cares what you're doing about it

Template for crisis internal communication:

"Here's what happened: [factual description]. Here's what we know right now: [known facts]. Here's what we don't know yet: [honest uncertainty]. Here's what we're doing: [specific actions]. Here's what you should do if you're asked about this: [specific guidance]. I'll update you by [specific time] with more information."


Narrative Consistency Checklist

Run before any major external communication:

  • Is this consistent with what we told investors last month?
  • Is this consistent with what we told employees at the last all-hands?
  • Does this contradict anything on our website, careers page, or press releases?
  • If an employee read this external communication, would they recognize the company being described?
  • If an investor read our internal all-hands deck, would they find anything inconsistent?
  • Have we been accurate about our current state, or are we projecting an aspiration?

Key Questions for Narrative

  • "Could a new employee explain to a friend why our company exists? What would they say?"
  • "What do we tell investors about our strategy? What do we tell employees? Are these the same?"
  • "If a journalist asked our team members to describe the company independently, what would they say?"
  • "When did we last update our 'why we exist' story? Is it still true?"
  • "What's the hardest question we'd get from each audience? Do we have an honest answer?"

Red Flags

  • Different departments describe the company mission differently
  • Investor narrative emphasizes growth; employee narrative emphasizes stability (or vice versa)
  • All-hands presentations are mostly slides, mostly one-way
  • Q&A questions are screened or deflected
  • Bad news reaches employees through Slack rumors before leadership communication
  • Careers page describes a culture that employees don't recognize

Integration with Other C-Suite Roles

When...Work with...To...
Investor update prepCFOAlign financial narrative with company narrative
Reorg or leadership changeCHRO + CEOSequence: employees first, then external
Product pivotCPOAlign customer communication with investor story
Culture changeCulture ArchitectEnsure internal story is consistent with external employer brand
M&A or partnershipCEO + COOControl information flow, prevent narrative leaks
CrisisAll C-suiteSingle voice, consistent story, internal first

Detailed References

  • references/narrative-frameworks.md — Storytelling structures, founder narrative, bad news delivery, all-hands templates
  • templates/all-hands-template.md — All-hands presentation template

FAQ

What does the internal-narrative skill do?

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs. Use when preparing investor updates, all-hands presentations, board communications, recruiting narratives, crisis communications, or when user mentions company narrative, messaging consistency, storytelling, all-hands, investor update, or crisis communication.

How do I install internal-narrative?

Run npx skills add https://github.com/alirezarezvani/claude-skills --skill internal-narrative in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/internal-narrative/ (personal) or .claude/skills/internal-narrative/ (project).

Which AI agents can use internal-narrative?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is internal-narrative safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains internal-narrative?

It is published by alirezarezvani in alirezarezvani/claude-skills. It has 549 recorded installs.

More from alirezarezvani/claude-skills

View all →

engineering-skills

alirezarezvani/claude-skills

Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.

Backend & APIs2.4K installs

finance-skills

alirezarezvani/claude-skills

Router/index for the finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts), saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio) and month-end-close (close calendar, reconciliations, flux review). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').

Business & Finance2.3K installs

marketing-skills

alirezarezvani/claude-skills

Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.

Marketing & SEO2.3K installs

business-growth-skills

alirezarezvani/claude-skills

Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').

Business & Finance2.2K installs

engineering-advanced-skills

alirezarezvani/claude-skills

Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops.

AI & Agents2K installs

product-skills

alirezarezvani/claude-skills

Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

Popular business & finance skills

View category →

sales-enablement

coreyhaines31/marketingskills

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),

Business & Finance119.5K installs

revops

coreyhaines31/marketingskills

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

Business & Finance114.1K installs

sales-funnel-blueprint

autonnel/autonnel-skills

Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.

Business & Finance104.5K installs

pricing

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.

Business & Finance80K installs

cross-border-ecommerce

nexscope-ai/ecommerce-skills

Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.

Business & Finance62.9K installs

pricing-strategy

coreyhaines31/marketingskills

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

Business & Finance61.2K installs