SkillAgentSearch skills...

internal-narrative

Build and maintain one coherent company story across employees, investors, customers, candidates, and partners

Install / Use

npx skills add borghei/Claude-Skills --skill internal-narrative

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

89/100

Supported Platforms

Universal

Tags

Our assessment of internal-narrative

internal-narrative scores 89/100 on our quality scale, 23rd of 46 Human Resources skills we index (top 50%).

Its SKILL.md is 20 KB long, well organised into 24 sections with 6 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so internal-narrative is actively maintained.
  • Our last check on 2026-10-31 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

internal-narrative compared with similar skills

All 4 of these similar skills score higher than internal-narrative; compare them before choosing.

SkillScoreStarsUpdatedFormat
internal-narrative (this skill)by borghei8981757d agoSKILL.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md
pptxby anthropics100177.9k56d agoSKILL.md
prospectingby coreyhaines3110060.1k6d agoSKILL.md

Frequently asked questions

How do I install internal-narrative?
Run npx skills add borghei/Claude-Skills --skill internal-narrative. The install tabs above show the steps for each supported agent.
Which AI agents does internal-narrative work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is internal-narrative safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is internal-narrative still maintained?
The repository was last updated about 2 months ago, so internal-narrative is actively maintained.

name: internal-narrative description: > Build and maintain one coherent company story across employees, investors, customers, candidates, and partners. Use when preparing all-hands meetings, investor updates, board presentations, recruiting narratives, or crisis communications. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: c-level domain: narrative-strategy tier: POWERFUL updated: 2026-03-09 frameworks: narrative-construction, audience-translation, crisis-communication

Internal Narrative Builder

Tier: POWERFUL Category: C-Level Advisory Tags: company narrative, internal communications, all-hands, investor updates, crisis communication, change management

Overview

One company. Many audiences. Same truth -- different lenses. The Internal Narrative Builder creates and maintains coherent communication across every stakeholder group. Narrative inconsistency is trust erosion: when employees hear one story and investors hear another, it is not strategic framing -- it is a trust debt that compounds until someone catches it.


Core Principle

The same fact lands differently depending on who hears it and what they need.

"We are shifting resources from Product A to Product B" means:

  • Employees: "Is my job safe? Why are we abandoning what I built?"
  • Investors: "Smart capital allocation -- they are doubling down on the winner."
  • Customers (Product A): "Are they abandoning us?"
  • Candidates: "Decisive leadership -- exciting new focus."
  • Partners: "Does this affect our integration?"

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


Clarify First

Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] The situation type (routine update, all-hands, investor update, pivot/reorg, or crisis) — determines which framework and template you use and the urgency of the cadence
  • [ ] Which audiences must hear this (employees, investors, customers, candidates, partners) — each gets its own column in the translation matrix with a different frame of the same fact
  • [ ] The core facts and current state (honest metrics, what changed, what's good and bad) — every audience narrative derives from one true core; vague facts produce hollow narrative
  • [ ] Any prior public statements on this topic (last investor update, last all-hands) — needed to run contradiction detection before the new communication ships

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Framework

Step 1: Build the Core Narrative

One paragraph that every other communication derives from. This is the single source of truth.

Template:

[Company] exists to [mission -- present tense, specific].
We are building [what] because [the problem, stated concretely].
Our approach is [what makes your way different].
We are at [honest description of current state] and heading toward
[where you are going, in concrete measurable terms].

Good example:

Acme Health exists to reduce preventable falls in elderly care using smartphone-based mobility analysis. We are building an AI diagnostic tool for care teams because current fall risk assessments are subjective, infrequent, and often wrong. Our approach -- using the phone camera during a 10-second walking test -- means no new hardware and no specialist required. We have 80 care facilities in DACH paying us EUR 800K ARR, and we are heading to EUR 3M ARR by demonstrating clinical value at scale before our Series B.

Bad example:

Acme Health is an innovative AI company revolutionizing elderly care through cutting-edge technology that empowers care providers.

The good version is usable. The bad version says nothing.

Step 2: Audience Translation Matrix

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

| Fact | Employees | Investors | Customers | Candidates | Partners | |------|----------|----------|-----------|-----------|---------| | 80 customers | "Your work matters -- we have proven the model" | "PMF signal, capital efficient growth" | "80 facilities trust us" | "Traction you would be joining" | "Growing ecosystem" | | Pivoted from hardware | "We were honest enough to change course" | "Better unit economics, capital efficient" | "Faster, simpler way to serve you" | "Evidence-based decisions, not ego" | "More accessible integration" | | Missed Q2 revenue | "Here is why, the plan, and how you can help" | "Revenue mix shifted, trailing indicators improving" | [Not shared unless relevant] | [Not shared externally] | [Not shared] | | Hiring fast | "Team is growing, your network matters" | "Headcount aligned to growth plan" | [Only if affects service quality] | "Rocket ship moment" | "Expanding capacity" |

Critical rule: Different framing is not different facts. "We told investors growth and told employees efficiency" is a contradiction. People talk to each other.

Step 3: Contradiction Detection Protocol

Before any major communication, run this check:

Question 1: What did we tell investors last quarter about this topic? Question 2: What did we tell employees at the last all-hands? Question 3: Are these consistent? If not -- which version is true?

Common contradictions to catch:

| Contradiction | Audiences | Why Dangerous | |--------------|-----------|---------------| | "Efficient growth" to investors + "hiring aggressively" to candidates | Investors vs candidates | Candidates talk to investors at events | | "Strong pipeline" to investors + "sales is struggling" at all-hands | Investors vs employees | Board members visit offices | | "Customer-first culture" + decisions clearly prioritizing revenue | External vs internal | Employees see through performative values | | "Stable and growing" to customers + "runway concerns" to board | Customers vs board | Customers hear rumors | | "World-class team" to investors + high turnover internally | Investors vs reality | Due diligence reveals truth |

When you catch a contradiction: Fix the less accurate version. Communicate the correction explicitly. "Last month I said X. After more analysis, the clearer picture is Y." Correcting yourself before someone catches it builds more trust than being caught.

Step 4: Communication Cadence

| Audience | Format | Frequency | Owner | Key Content | |----------|--------|-----------|-------|-------------| | All employees | All-hands meeting | Monthly | CEO | State of company, wins, challenges, Q&A | | Teams | Team standup/update | Weekly | Team leads | Team-specific progress and blockers | | Investors | Written update | Monthly | CEO + CFO | Metrics, narrative, asks | | Board | Board meeting + memo | Quarterly | CEO | Strategy, financials, key decisions | | Customers | Product updates | Per release | CPO / CS | What changed, what is coming | | Candidates | Careers page + interviews | Ongoing | CHRO + Founders | Why join, culture, mission | | Partners | Business review | Quarterly | BD / Partnerships | Joint metrics, roadmap alignment |

Step 5: All-Hands Design

The all-hands is the most important recurring internal communication. Most companies get it wrong.

Structure (60 minutes):

| Segment | Duration | Content | |---------|----------|---------| | State of the company | 10 min | Honest assessment -- good and bad | | Key metrics | 5 min | 3-5 metrics everyone should know, with context | | Wins and recognition | 10 min | Connect team work to company outcomes | | Challenges and plan | 10 min | What is not working and what we are doing about it | | Strategic update | 10 min | Where we are headed and why | | Open Q&A | 15 min | Unscreened, unfiltered questions |

All-Hands Principles:

  1. Lead with honest state. No spin. Employees detect inauthenticity instantly.
  2. Connect metrics to people: "Sarah's team shipped X, which drove Y."
  3. Give people a reason to be proud of their choice to work here.
  4. Leave real time for Q&A -- not curated questions, not "any quick questions?"
  5. Follow up on unanswered questions within 48 hours.

All-Hands Failure Modes:

| Failure | Signal | Fix | |---------|--------|-----| | CEO monologue | 55 of 60 minutes is one person talking | Max 30 min presentation, rest is interactive | | Sunshine and rainbows | Only good news, every metric is "great" | Include one honest challenge and its plan | | Metrics without context | "ARR grew 15%" with no benchmark | Always: metric + context + what it means | | Deflected questions | "Great point, let's follow up" (never followed up) | Answer or commit to written follow-up by date | | No employee voice | Leadership talks, employees listen | Include team demos, recognition, Q&A | | Slides over substance | 50 slides of bullet points | Max 15 slides, mostly visuals and charts |

Step 6: Investor Update Template

Monthly investor updates should be concise, honest, and actionable.

Subject: [Company] Monthly Update - [Month Year]

TL;DR: [One sentence -- honest state of things]

METRICS:
  MRR/ARR: $[X] ([+/-Y]% MoM)
  Burn: $[X]/month
  Runway: [X] months
  Key Metric: [Your North Star] at [value]

WINS:
  - [Specific win with context]
  - [Specific win with context]

CHALLENGES:
  - [Honest challenge with your plan to address it]

ASKS:
  - [Specific ask: intro, hire, advice]
  - [Specific ask]

NEXT MONTH FOCUS:
  - [Priority 1]
  - [Priority 2]

Rules:

  • Send on the same date every month (builds trust through consistency)
  • Include challenges -- investors respect honesty, distrust all-good-news updates
  • Make asks specific -- "intro to head of product at Stripe" not "intros to SaaS companies"
  • Keep under 500 words -- investors read dozens of these

Step 7: Crisis Communication

When the narrative breaks -- someone leaves publicly, a product fails, a security breach, negative press.

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 social media or press.

Crisis Communication Sequence:

Hour 0-4 (Internal First):

1. CEO or relevant leader sends internal message
2. Acknowledge what happened -- factual, no spin
3. State what you know and what you don't know yet
4. Tell people what you are doing about it
5. Tell people what to say if asked externally
6. Commit to next update by specific time

Hour 4-24 (External If Needed):

1. External statement only if event is public
2. Consistent with internal message -- same facts, audience-appropriate framing
3. Legal review if any claims or liability involved
4. Single spokesperson designated

Crisis Internal Template:

Team,

Here is what happened: [factual description, no editorializing]

Here is what we know right now: [confirmed facts]

Here is what we don't know yet: [honest uncertainty]

Here is what we are doing: [specific actions with owners]

If you are asked about this externally: [specific guidance]

I will update you by [specific time] with more information.

[Name]

Crisis Don'ts:

  • Silence (vacuum fills with speculation)
  • Spin (people detect it, trust dies)
  • "No comment" (implies guilt)
  • Blaming (your audience only cares what you are doing about it)
  • Deleting social media comments (people screenshot, makes it worse)
  • Humor (read the room)

Narrative Consistency Checklist

Run before any major external communication:

  • [ ] Consistent with what we told investors last quarter?
  • [ ] Consistent with what we told employees at last all-hands?
  • [ ] Contradicts anything on website, careers page, or press releases?
  • [ ] If an employee read this external communication, would they recognize the company described?
  • [ ] If an investor read our internal all-hands deck, would they fin

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryHuman
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium