Internal Narrative
alirezarezvani/claude-skills
Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners.
ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical…
$ npx skills add w95/awesome-claude-corporate-skills --skill executive-communication -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install w95/awesome-claude-corporate-skills executive-communication --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/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/01-executive-leadership/executive-communication .claude/skills/executive-communication && 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 "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .claude/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communicationType 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 w95/awesome-claude-corporate-skills --skill executive-communication -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install w95/awesome-claude-corporate-skills executive-communication --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/01-executive-leadership/executive-communication .agents/skills/executive-communication && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .agents/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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 w95/awesome-claude-corporate-skills --skill executive-communication -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install w95/awesome-claude-corporate-skills executive-communication --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/01-executive-leadership/executive-communication .cursor/skills/executive-communication && 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 "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .cursor/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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/w95/awesome-claude-corporate-skills.git --path 01-executive-leadership/executive-communication--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 w95/awesome-claude-corporate-skills --skill executive-communication -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install w95/awesome-claude-corporate-skills executive-communication --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/01-executive-leadership/executive-communication .gemini/skills/executive-communication && 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 "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .gemini/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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 w95/awesome-claude-corporate-skills executive-communicationInstalls 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 w95/awesome-claude-corporate-skills --skill executive-communication -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/01-executive-leadership/executive-communication .github/skills/executive-communication && 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 "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .github/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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 w95/awesome-claude-corporate-skills --skill executive-communication -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install w95/awesome-claude-corporate-skills executive-communication --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/w95/awesome-claude-corporate-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/01-executive-leadership/executive-communication .opencode/skills/executive-communication && 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 "executive-communication" agent skill from https://github.com/w95/awesome-claude-corporate-skills/tree/main/01-executive-leadership/executive-communication into .opencode/skills/executive-communication/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "executive-communication", 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.
executive-communicationACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical…
Executive Communication is an agent skill from w95/awesome-claude-corporate-skills. ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical communication to employees, investors, customers, or media. Executive communications require persuasion, clarity, emotional intelligence, and alignment with company values and strategy.
Its SKILL.md is about 3.8k 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 Business, Finance & HR, covering Internal communications and Fundraising and pitch decks. The repository describes itself as: 166 production-ready Claude AI skills organized by corporate role — executive leadership, finance, HR, marketing, sales, legal, operations, engineering, product, data, customer…. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 78dbc7c. 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.
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.
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.
Executive Communication loads about 3.8k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 1,057 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); files beside SKILL.md are not scanned.
The full file from w95/awesome-claude-corporate-skills at commit 78dbc7c, republished under its MIT licence (© w95). 1,057 words, ~3,795 tokens.
.claude/skills/executive-communication/SKILL.md (or your agent's skills folder).Executive communication is how leadership sets culture, builds trust, maintains alignment, and manages perception during both opportunity and crisis. This skill enables you to craft compelling speeches, write persuasive investor updates, draft transparent crisis communications, and deliver messages that inspire action and build credibility. Use this skill whenever you need to communicate significant company news, strategic direction, values, crisis management, or any high-stakes message to employees, investors, customers, or the media.
Define Your Core Message
Before drafting, answer these critical questions:
MESSAGE FRAMEWORK
1. WHAT IS THE PRIMARY MESSAGE?
- What single idea do you want the audience to remember?
- Can you state it in one sentence?
2. WHO IS THE AUDIENCE?
- Employees? Investors? Customers? Media?
- What do they care about most?
- What questions will they have?
- What do you need them to do?
3. WHY NOW?
- What's the trigger for this message?
- Why is this communication important at this moment?
- What happens if you don't communicate this?
4. WHAT EMOTION DO YOU WANT TO EVOKE?
- Inspiration? Urgency? Calm? Confidence?
- What's the emotional journey through your message?
5. WHAT CALL TO ACTION DO YOU WANT?
- Do you want people to do something specific?
- Or simply understand and accept the message?
6. WHAT'S YOUR CREDIBILITY?
- Why should they believe you?
- What evidence or experience validates this?Structure the Message
Use the pyramid approach: key message first, supporting details second, evidence third.
KEY MESSAGE (Hook, compelling opening)
↓
SUPPORTING POINTS (3-4 reasons why this matters)
↓
EVIDENCE & STORIES (Data, examples, anecdotes)
↓
CALL TO ACTION (What you want them to do)All-Hands Meeting Structure
An effective all-hands combines business updates with cultural moments:
Duration: 45-60 minutes for full meeting
COMPANY ALL-HANDS STRUCTURE
0:00-0:05 | OPENING
| Welcome, land the key message
| Why this meeting matters
0:05-0:15 | BUSINESS SNAPSHOT
| Revenue, growth, key metrics
| Market position and customer wins
| What we're winning at
0:15-0:25 | STRATEGIC FOCUS
| Where we're going (vision/OKRs)
| Why this direction matters
| How it connects to our mission
0:25-0:35 | CHALLENGES & HONESTY
| What we're struggling with
| What didn't work
| What we're learning
| HOW WE'RE FIXING IT (action plan)
0:35-0:45 | PEOPLE, CULTURE & VALUES
| Organizational changes/new hires
| Culture highlights or shifts
| Celebration of team wins
| Leadership message on values
0:45-0:55 | Q&A
| Pre-screened and live questions
| Prepare 5-7 tough questions
| Answer honestly, don't dodge
0:55-1:00 | CLOSE
| Restate key message
| Thank you and inspired exitAll-Hands Best Practices:
Opening Hook (60 seconds):
Bad opening: "We're here today to go over Q3 results." Better opening: "Three months ago, we made a bet on expanding into healthcare. Today, I want to tell you about our first major customer win in that space—and what it means for all of us."
Body: Tell Stories With Data
Bad: "We grew 45% YoY." Better: "We grew 45% YoY—that's 12,000 new customers whose workflows we're improving every day. That's about 50 customers for every person in this room."
Handling Difficult News:
Bad: "We missed our revenue target but we have a lot of pipeline." Better: "We missed our Q3 revenue target by 15%. Here's why: [honest explanation]. This means [specific impact]. Here's what we're doing about it: [action plan]. And here's how we're adjusting: [strategic pivot]. I'm confident because [evidence]."
Closing Call to Action:
Investor Update Structure
Quarterly updates to investors (board and VCs):
QUARTERLY INVESTOR UPDATE
[SUBJECT: Q[X] Update - [Company Name] - [Headline Result]]
OPENING PARAGRAPH
- Headline result: revenue, growth rate, major milestone
- Tone: confident, transparent, forward-looking
- 2-3 sentences maximum
FINANCIAL PERFORMANCE
- Revenue: $[X]M, [+Y%] QoQ, [+Z%] YoY
- Growth rate: [X%] (what does this mean for trajectory?)
- Profitability/burn: Path to profitability? Runway?
- Key metrics: CAC, LTV, retention, NPS
BUSINESS HIGHLIGHTS
- Major customer wins (with permission, name them)
- Product launches or feature releases
- Market traction (market share, positioning)
- Competitive wins or differentiation examples
STRATEGIC UPDATES
- Progress on key initiatives
- Market expansion updates
- Partnership or M&A activity
- Product roadmap progress
CHALLENGES & TRANSPARENCY
- What didn't go as planned
- Risks we're monitoring
- Market headwinds or tailwinds
- How we're adapting
PEOPLE & ORGANIZATION
- Key executive hires or promotions
- Team growth metrics
- Culture and retention signals
NEXT QUARTER FOCUS
- Top 3 priorities
- Expected milestones
- Key dates to watch
CLOSING
- Reiterate confidence and trajectory
- Invite questions or discussionInvestor Letter (Quarterly or Annual)
A more personal, narrative-driven update (500-750 words):
INVESTOR LETTER STRUCTURE
OPENING NARRATIVE (100 words)
- Personal reflection or story
- One major event or realization from the quarter
- Sets the tone for what follows
BUSINESS MOMENTUM (150 words)
- Revenue and growth snapshot
- Major customer wins or market validation
- Competitive position and market share
STRATEGIC NARRATIVE (200 words)
- Long-term vision and where we are in that journey
- Key bets we're making and why
- How recent results validate or adjust our strategy
- Multi-year trajectory and inflection points
HONEST ASSESSMENT (150 words)
- What's working better than expected
- What's harder or taking longer than planned
- How we're learning and adapting
- Market opportunities we're pursuing
LOOKING AHEAD (100 words)
- Next quarter and next year priorities
- What we're most excited about
- How investors can help
- Closing thought connecting back to opening storyExample Investor Letter Opening:
"When we started [Company], we believed that [core insight]. Three years later, we've served 50,000 customers across [markets], and that belief has become clearer, not harder. This quarter alone, we saw [specific validation]. But we also learned something unexpected: [insight that required strategy adjustment]. This letter is about that journey, what it means, and where we're headed."
Crisis Communication Fundamentals
When bad news breaks, communicate fast and transparently:
Crisis Communication Principles:
Crisis Communication Timeline
IMMEDIATE (First 2 hours)
- Gather facts and confirm information
- Notify executive team, board, legal counsel
- Draft initial holding statement
- Share with affected stakeholders first
- Prepare additional detail for media if needed
SHORT-TERM (First 24 hours)
- Send detailed message to all staff/customers
- Explain impact and mitigation steps
- Assign accountability and ownership
- Establish communication cadence
NEAR-TERM (First week)
- Daily updates to stakeholders on progress
- Regular all-hands or leadership updates
- Address media inquiries with facts
- Monitor and manage social media narrative
ONGOING (Weeks 2-4)
- Regular updates on remediation progress
- Acknowledge impact and empathize
- Share lessons learned
- Rebuild trust through consistent communicationCrisis Statement Template
CRISIS STATEMENT
HEADLINE
[What happened, stated factually - 1 sentence]
IMMEDIATE IMPACT
[Who was affected and how - be specific]
ACKNOWLEDGMENT
[We understand the seriousness; we take full responsibility]
WHAT WE'RE DOING
[Specific actions we're taking immediately]
WHY THIS HAPPENED
[Honest explanation of root cause]
HOW WE'RE PREVENTING IT
[Changes we're making to prevent recurrence]
SUPPORT FOR AFFECTED PARTIES
[What we're doing to help those impacted]
TIMELINE
[When people can expect resolution/updates]
CONTACT
[Who should people reach out to with questions]Example Crisis Message:
"At 2 PM PT today, we discovered a data breach affecting [X] customer records. We immediately took those systems offline and notified law enforcement. Here's what happened: [explanation]. Here's what we're doing: [specific actions with timeline]. Here's what we're offering affected customers: [support]. We take this seriously. This is unacceptable, and we're committed to making this right."
Press Statement Structure
A formal statement for media distribution (150-250 words):
PRESS STATEMENT
[HEADLINE - Catchy, newsworthy, one-liner]
[LEAD PARAGRAPH - Answer the 5 W's]
What: What announcement or news?
Who: Which company and executives?
When: Timeline or date?
Where: Geographic scope?
Why: Why does this matter?
[SUPPORTING DETAILS - 2-3 paragraphs]
- Specific metrics or results
- Customer or market impact
- Strategic significance
- Supporting quotes from executives
[QUOTE FROM CEO]
[1-2 sentences reflecting company values and vision]
[ADDITIONAL CONTEXT - 1 paragraph]
- Company background
- Market opportunity
- Future plans or roadmap
[BOILERPLATE]
About [Company Name]
Contact information for media inquiriesQuote Strategy:
Speech Structure for Maximum Impact
OPENING (2 minutes)
- Story or personal moment
- Why you're giving this speech
- What the audience will learn
- Make them want to listen
MAIN BODY (20-30 minutes)
- 3-4 main points (not more)
- Each point: story + data + why it matters
- Use specific examples, not generalizations
- Connect to audience values and mission
HANDLING OBJECTIONS (5 minutes)
- Anticipated questions or resistance
- Address them head-on
- Show you've thought through concerns
CALL TO ACTION (2 minutes)
- What do you want people to do?
- Make it specific and achievable
- Connect to their work and values
CLOSING (2 minutes)
- Restate the key message
- Personal reflection or gratitude
- Inspirational note that lingersDelivery Tips:
Preparation:
Delivery Mechanics:
Handling Nerves:
Monthly:
Quarterly:
Annually:
Ad Hoc:
Use this skill to build organizational culture, maintain stakeholder trust, and drive alignment around strategic priorities through compelling, authentic communication.
© w95, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in 01-executive-leadership/executive-communication of w95/awesome-claude-corporate-skills.
Open the folder on GitHubat commit 78dbc7c
Executive Communication 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 |
|---|---|---|---|---|---|---|
| Executive Communication this skillw95/awesome-claude-corporate-skills | 235 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Internal Narrativealirezarezvani/claude-skills | 28k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Pitchcraft Persuasive Briefingsmoshuying/pitchcraft | 191 | 1 repos | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Ceo Advisordavila7/claude-code-templates | 32k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ceo Advisoralirezarezvani/claude-skills | 28k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| Data Researchinbrainfun/inbrain | 142 | 1 repos | ~1.2k | Automated safety check: Pass | Custom licence |
alirezarezvani/claude-skills
Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners.
moshuying/pitchcraft
Structures kickoffs, status updates, wrap-ups, investor pitches and solution selling on one five-part persuasion framework, with a pre-submit checklist.
davila7/claude-code-templates
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management.
alirezarezvani/claude-skills
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management.
inbrainfun/inbrain
Structured data research: search sources, extract structured data, archive raw sources, maintain canonical tracker pages, deduplicate.
borghei/Claude-Skills
Executive leadership guidance for strategic decisions, org development, and stakeholder management.
w95/awesome-claude-corporate-skills
Generate or improve a company-specific data analysis skill by extracting tribal knowledge from analysts.
w95/awesome-claude-corporate-skills
Framework for competitive landscape analysis across any industry.
w95/awesome-claude-corporate-skills
Research a company using Common Room data. An agent skill from w95/awesome-claude-corporate-skills.
w95/awesome-claude-corporate-skills
Prepare for a customer or prospect call using Common Room signals.
w95/awesome-claude-corporate-skills
Generate personalized outreach messages using Common Room signals.
w95/awesome-claude-corporate-skills
Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.).
Categories
ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical…. Executive Communication is an agent skill from w95/awesome-claude-corporate-skills. ACTIVATE when drafting all-hands speeches, investor updates, quarterly letters to stakeholders, press statements, CEO announcements, crisis communications, customer updates, or any mission-critical communication to employees, investors, customers, or media.
Executive Communication fits situations like: tasks that involve Internal communications; tasks that involve Fundraising and pitch decks.
Run `npx skills add w95/awesome-claude-corporate-skills --skill executive-communication -a claude-code`. Or copy the skill folder (01-executive-leadership/executive-communication in w95/awesome-claude-corporate-skills) into .claude/skills/executive-communication in your project. Claude Code loads it when a task matches its description.
Run `npx skills add w95/awesome-claude-corporate-skills --skill executive-communication -a codex`. Or copy the skill folder (01-executive-leadership/executive-communication in w95/awesome-claude-corporate-skills) into .agents/skills/executive-communication 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 w95/awesome-claude-corporate-skills --skill executive-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executive-communication, .gemini/skills/executive-communication, .github/skills/executive-communication and .opencode/skills/executive-communication in your project.
SKILL.md names no scripts, command-line tools or credentials: Executive Communication is instructions for the agent only.
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. Review the folder before installing.
Executive Communication is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k 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 Executive Communication: Internal Narrative (alirezarezvani/claude-skills, 28k stars), Pitchcraft Persuasive Briefings (moshuying/pitchcraft, 191 stars), Ceo Advisor (davila7/claude-code-templates, 32k 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.
w95 (a GitHub user) maintains it in w95/awesome-claude-corporate-skills, which has 235 GitHub stars. The repository holds 43 skills in this directory. The repository was last updated on February 26, 2026.
Source: w95/awesome-claude-corporate-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.