Internal Narrative
alirezarezvani/claude-skills
Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners.
Build and maintain one coherent company story across employees, investors, customers, candidates, and partners.
$ npx skills add borghei/Claude-Skills --skill internal-narrative -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills internal-narrative --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/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/c-level-advisor/internal-narrative .claude/skills/internal-narrative && 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 "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .claude/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrativeType 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 borghei/Claude-Skills --skill internal-narrative -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills internal-narrative --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/c-level-advisor/internal-narrative .agents/skills/internal-narrative && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .agents/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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 borghei/Claude-Skills --skill internal-narrative -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills internal-narrative --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/c-level-advisor/internal-narrative .cursor/skills/internal-narrative && 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 "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .cursor/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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/borghei/Claude-Skills.git --path c-level-advisor/internal-narrative--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 borghei/Claude-Skills --skill internal-narrative -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills internal-narrative --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/c-level-advisor/internal-narrative .gemini/skills/internal-narrative && 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 "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .gemini/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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 borghei/Claude-Skills internal-narrativeInstalls 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 borghei/Claude-Skills --skill internal-narrative -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/c-level-advisor/internal-narrative .github/skills/internal-narrative && 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 "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .github/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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 borghei/Claude-Skills --skill internal-narrative -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills internal-narrative --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/c-level-advisor/internal-narrative .opencode/skills/internal-narrative && 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 "internal-narrative" agent skill from https://github.com/borghei/Claude-Skills/tree/main/c-level-advisor/internal-narrative into .opencode/skills/internal-narrative/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "internal-narrative", 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.
internal-narrativeBuild and maintain one coherent company story across employees, investors, customers, candidates, and partners.
Internal Narrative is an agent skill from borghei/Claude-Skills. 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.
Its SKILL.md is about 5.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/messaging_framework_generator.py`, `scripts/narrative_consistency_checker.py` and `scripts/stakeholder_mapper.py`).
It sits in Business, Finance & HR, covering Internal communications, Fundraising and pitch decks and Recruiting and HR. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
7 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Internal Narrative loads about 5.1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 2,216 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.
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); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,216 words, ~5,066 tokens.
.claude/skills/internal-narrative/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.Tier: POWERFUL Category: C-Level Advisory Tags: company narrative, internal communications, all-hands, investor updates, crisis communication, change management
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.
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:
Same fact. Five narratives needed. The skill is maintaining truth while serving each audience's actual question.
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
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.
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.
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.
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.
| 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 |
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:
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 |
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:
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 timeHour 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 designatedCrisis 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:
Run before any major external communication:
When communicating significant changes (reorgs, pivots, layoffs, policy changes):
| Stage | Communication Need | Example |
|---|---|---|
| Awareness | Why is this change happening? | "Our market shifted. Here is the data." |
| Desire | Why should I support it? | "This protects our future. Here is how." |
| Knowledge | What do I need to know? | "Your role changes from X to Y." |
| Ability | Can I actually do this? | "Training starts Monday. Support available." |
| Reinforcement | Is this working? | "30 days in: here is the progress." |
Day -1: Brief leadership team (they need to be able to answer questions)
Day 0: All-hands announcement (CEO, with full context)
Day 0: Written follow-up (email with details, FAQ)
Day 1-3: Team-level discussions (managers address team-specific impact)
Day 7: Follow-up Q&A session (address questions that emerged)
Day 30: Progress update (what changed, what is working)Watch for these signs that narrative is fracturing:
| Situation | Collaborate With | Alignment Needed |
|---|---|---|
| Investor update prep | CFO Advisor | Financial narrative matches company narrative |
| Reorg / leadership change | CEO + CHRO | Employees hear first, then external |
| Product pivot | CPO / Product Team | Customer communication aligns with investor story |
| Crisis | All C-suite | Single voice, consistent story, internal first |
| Fundraise narrative | CEO + CFO | Growth story consistent with burn and metrics |
| Recruiting push | CHRO + CEO | Candidate narrative matches employee experience |
| Skill | Use When |
|---|---|
| ceo-advisor | Strategic decisions that need to be communicated |
| cfo-advisor | Financial narrative for investors and board |
| scenario-war-room | Crisis scenarios that may require communication plans |
| cs-onboard | Building the foundational company context that feeds all narratives |
| Problem | Likely Cause | Resolution |
|---|---|---|
| Employees describe the company mission differently across departments | Core narrative not established or not communicated with enough frequency | Rebuild core narrative using Step 1 template; communicate through 7+ channels; re-test with 5-person test after 2 weeks |
| Investor update and all-hands deck tell conflicting stories | Different authors without shared source-of-truth document | Create single core narrative document; all communications must derive from it; run contradiction detection before every external communication |
| All-hands Q&A produces only softball questions | Employees don't trust that honest questions are safe | Switch to anonymous question submission; answer the hardest question first; CEO models vulnerability by sharing a mistake |
| Crisis communication arrives after employees see it on social media | No 4-hour rule in place or no internal communication chain | Establish internal-first protocol with pre-drafted templates; designate single spokesperson; practice crisis drills quarterly |
| Change communication met with cynicism ("another reorganization") | Past changes communicated without follow-through on ADKAR reinforcement stage | Include 30-day progress update in every change plan; reference previous successful changes as evidence |
| Careers page describes a culture employees don't recognize | Marketing owns careers page without HR/employee input | Co-create careers content with current employees; include real employee stories; audit annually against engagement survey data |
| Stakeholder groups receiving inconsistent messaging about company priorities | No audience translation matrix maintained | Build and maintain the translation matrix from Step 2; review before every major communication cycle |
| Skill | Integration | Data Flow |
|---|---|---|
ceo-advisor | CEO strategic decisions require narrative communication | CEO decisions → Narrative framing for each audience |
cfo-advisor | Financial narrative for investors must align with company narrative | CFO metrics → Investor update narrative |
cmo-advisor | External marketing narrative must match internal story | Narrative core → Marketing messaging alignment |
chro-advisor | Recruiting narrative must reflect employee reality | Narrative careers content → CHRO validation |
scenario-war-room | Crisis scenarios require pre-built communication plans | War room scenarios → Crisis narrative templates |
strategic-alignment | Strategy cascade depends on clear narrative communication | Narrative clarity → Alignment articulation test |
change-management | Every change initiative requires narrative support | Change plan → Narrative ADKAR communication |
| Tool | Purpose | Usage |
|---|---|---|
scripts/narrative_consistency_checker.py | Check two or more communication texts for factual contradictions and tone mismatches | python scripts/narrative_consistency_checker.py --texts investor_update.txt allhands_deck.txt --json |
scripts/messaging_framework_generator.py | Generate an audience translation matrix from a core narrative statement | python scripts/messaging_framework_generator.py --narrative "We are shifting from product A to product B" --audiences employees,investors,customers --json |
scripts/stakeholder_mapper.py | Map stakeholders by influence, interest, and communication needs | python scripts/stakeholder_mapper.py add --name "Board of Directors" --influence high --interest high --frequency quarterly --json |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in c-level-advisor/internal-narrative of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
Internal Narrative 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 |
|---|---|---|---|---|---|---|
| Internal Narrative this skillborghei/Claude-Skills | 881 | — | ~5.1k | Automated safety check: Pass | MIT | |
| Internal Narrativealirezarezvani/claude-skills | 28k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ceo Advisordavila7/claude-code-templates | 32k | 2 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Advisor Due DiligenceBubble252/offer-harvester | 123 | — | ~281 | Automated safety check: Pass | MIT | |
| Ceo Advisoralirezarezvani/claude-skills | 28k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Ceo Advisormajiayu000/claude-skill-registry | 666 | 1 repos | ~3.9k | Automated safety check: Pass | MIT |
alirezarezvani/claude-skills
Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners.
davila7/claude-code-templates
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management.
Bubble252/offer-harvester
Build an evidence-grounded advisor review covering identity, research direction, recruitment signals, lab context, source gaps, and community risk signals.
alirezarezvani/claude-skills
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management.
majiayu000/claude-skill-registry
Executive leadership guidance for strategic decisions, org development, and stakeholder management.
forcedotcom/sf-skills
A skill your agent uses to configure Education Cloud domains (Student Success, Recruitment & Admissions, Academic Operations, Alumni Relations, Student Management, or Mentoring) through…
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
Build and maintain one coherent company story across employees, investors, customers, candidates, and partners. Internal Narrative is an agent skill from borghei/Claude-Skills. Build and maintain one coherent company story across employees, investors, customers, candidates, and partners.
Internal Narrative fits situations like: preparing all-hands meetings; investor updates; board presentations; recruiting narratives.
Run `npx skills add borghei/Claude-Skills --skill internal-narrative -a claude-code`. Or copy the skill folder (c-level-advisor/internal-narrative in borghei/Claude-Skills) into .claude/skills/internal-narrative in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill internal-narrative -a codex`. Or copy the skill folder (c-level-advisor/internal-narrative in borghei/Claude-Skills) into .agents/skills/internal-narrative in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill internal-narrative -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/internal-narrative, .gemini/skills/internal-narrative, .github/skills/internal-narrative and .opencode/skills/internal-narrative in your project.
Going by SKILL.md and its folder, Internal Narrative needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
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.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Internal Narrative is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.1k tokens (SKILL.md is roughly 20k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Internal Narrative: Internal Narrative (alirezarezvani/claude-skills, 28k stars), Ceo Advisor (davila7/claude-code-templates, 32k stars), Advisor Due Diligence (Bubble252/offer-harvester, 123 stars) and Ceo Advisor (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/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.