Internal Communications Writer
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership.
$ npx skills add travisjneuman/.claude --skill leadership -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install travisjneuman/.claude leadership --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/travisjneuman/.claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leadership .claude/skills/leadership && 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 "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .claude/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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/travisjneuman/.claude/tree/master/skills/leadershipType 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 travisjneuman/.claude --skill leadership -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install travisjneuman/.claude leadership --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/leadership .agents/skills/leadership && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .agents/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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 travisjneuman/.claude --skill leadership -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install travisjneuman/.claude leadership --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/leadership .cursor/skills/leadership && 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 "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .cursor/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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/travisjneuman/.claude.git --path skills/leadership--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 travisjneuman/.claude --skill leadership -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install travisjneuman/.claude leadership --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/leadership .gemini/skills/leadership && 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 "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .gemini/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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 travisjneuman/.claude leadershipInstalls 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 travisjneuman/.claude --skill leadership -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/leadership .github/skills/leadership && 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 "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .github/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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 travisjneuman/.claude --skill leadership -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install travisjneuman/.claude leadership --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/travisjneuman/.claude.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/leadership .opencode/skills/leadership && 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 "leadership" agent skill from https://github.com/travisjneuman/.claude/tree/master/skills/leadership into .opencode/skills/leadership/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "leadership", 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.
leadershipExecutive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership.
Leadership is an agent skill from travisjneuman/.claude. Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/fortune-50-executive-leadership.md`).
It sits in Writing & Content, covering Internal communications. The repository describes itself as: The Ultimate Claude Code Toolkit: 180 skills, 10 agents, 29 commands, 7 hooks, and 81 marketplace repos (11,000+ community skills). Drop-in ~/.claude config with a generated… The licence is MIT.
Read from SKILL.md and the folder at commit 446a461. 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.
Leadership loads about 2.9k tokens when it runs, and up to ~20k if it reads all its reference files. Until then it costs about 66 tokens; SKILL.md has 415 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 travisjneuman/.claude at commit 446a461, republished under its MIT licence (© travisjneuman). 415 words, ~2,857 tokens.
.claude/skills/leadership/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Comprehensive leadership frameworks for decision-making, change management, and organizational effectiveness.
OODA LOOP (Fast Decisions):
Observe → Orient → Decide → Act
DECIDE FRAMEWORK (Complex Decisions):
D - Define the problem
E - Establish criteria
C - Consider alternatives
I - Identify best alternative
D - Develop action plan
E - Evaluate and monitor
WRAP FRAMEWORK (Avoiding Bias):
W - Widen your options
R - Reality-test assumptions
A - Attain distance before deciding
P - Prepare to be wrong| Factor | Questions to Ask |
|---|---|
| Frame | Are we solving the right problem? |
| Alternatives | Have we considered enough options? |
| Information | Do we have reliable data? |
| Values | Are we clear on what matters? |
| Reasoning | Is our logic sound? |
| Commitment | Will people execute? |
| Importance | Urgency | Decision By |
|---|---|---|
| High | High | Executive (fast) |
| High | Low | Executive (thoughtful) |
| Low | High | Delegate with check-in |
| Low | Low | Delegate fully |
1. Create Urgency - Compelling reasons, threats/opportunities
2. Build Guiding Coalition - Influential cross-functional team
3. Form Strategic Vision - Clear future state and strategy
4. Communicate Vision - Repeat across channels, model behaviors
5. Enable Action - Remove barriers, encourage risk-taking
6. Generate Short-term Wins - Plan victories, build momentum
7. Sustain Acceleration - Hire change agents, new projects
8. Institute Change - Anchor in culture, ensure continuity| Element | Definition | Key Actions |
|---|---|---|
| Awareness | Understanding why | Communicate business drivers |
| Desire | Want to participate | Address WIIFM, reduce resistance |
| Knowledge | How to change | Training, education |
| Ability | Skills to execute | Practice, coaching |
| Reinforcement | Sustain the change | Recognition, measurement |
SOURCES OF RESISTANCE:
- Fear of unknown
- Loss of control
- Surprise / timing
- Concerns about competence
- Past change failures
- Threat to status
- Peer pressure
- Mistrust of leadership
RESPONSE STRATEGIES:
| Type | Approach |
|------|----------|
| Information deficit | Education, communication |
| Skill deficit | Training, coaching |
| Incentive deficit | Align rewards |
| Resource deficit | Provide support |
| Values conflict | Dialogue, involvement |
| Politics | Negotiation, coalition |PRE-CRISIS: Risk ID, crisis team, templates, exercises
RESPONSE (Hour 1-4): Activate team, assess, secure safety, communicate
RESPONSE (Hour 4-24): Detailed assessment, stakeholder/media comms
RESPONSE (Day 2-7): Root cause, remediation, ongoing comms
POST-CRISIS: After-action review, improvements, reputation repairCOMMUNICATION PRINCIPLES:
- Acknowledge quickly
- Show empathy
- Take responsibility (where appropriate)
- Explain actions being taken
- Commit to updates
- Be honest about unknowns
STAKEHOLDER PRIORITIES:
1. Affected individuals (safety)
2. Employees
3. Regulators
4. Media
5. Investors
6. Customers
7. Partners
8. General public
MESSAGE FRAMEWORK:
1. What happened (facts known)
2. What we're doing (actions)
3. What it means for stakeholders
4. What to expect next| Element | Description |
|---|---|
| Risk Assessment | Identify potential disruptions |
| Business Impact Analysis | Critical processes, RTOs, RPOs |
| Recovery Strategies | Alternate facilities, IT, people |
| Plan Development | Documented procedures |
| Testing & Exercises | Regular drills, tabletops |
| Maintenance | Annual updates, post-incident |
STAKEHOLDER MAPPING:
Power/Influence
High Low
Interest
High MANAGE CLOSELY KEEP INFORMED
(Board, major (Employees,
investors) community)
Low KEEP SATISFIED MONITOR
(Regulators, (Low priority
lenders) groups)| Stakeholder | Interest | Influence | Strategy | Frequency |
|---|---|---|---|---|
| Board | High | High | Partner | Monthly |
| Investors | High | High | Inform & consult | Quarterly |
| Employees | High | Medium | Engage | Weekly |
| Customers | High | Medium | Listen & respond | Ongoing |
| Regulators | Medium | High | Comply & inform | As needed |
| Media | Variable | High | Proactive comms | As needed |
RECIPROCITY: Give first - help others, share resources, build credit
SOCIAL PROOF: Reference peers/competitors, share success stories
AUTHORITY: Demonstrate competence, use data and evidence
LIKING: Find common ground, show genuine interest
SCARCITY: Create urgency with limited opportunity/time
COMMITMENT: Start small, get incremental yes, build agreementsBOARD MEETING PREPARATION:
- Pre-read materials 1 week ahead
- Executive summary on page 1
- Clear recommendation/ask
- Supporting data in appendix
- Anticipate questions
BOARD PRESENTATION STRUCTURE:
1. Context (2 min)
2. Key issue/opportunity (3 min)
3. Options considered (5 min)
4. Recommendation (3 min)
5. Discussion (remaining time)
BOARD REPORTING CADENCE:
| Topic | Frequency |
|-------|-----------|
| Financial results | Monthly/Quarterly |
| Strategic initiatives | Quarterly |
| Risk dashboard | Quarterly |
| Talent/succession | Semi-annually |
| Strategy refresh | Annually |
| Competitive landscape | Annually || Practice | Description |
|---|---|
| Independent Chair | Separate from CEO for oversight |
| Executive Sessions | Independent director meetings |
| Board Evaluation | Annual self-assessment |
| Succession Planning | CEO and board renewal |
| Risk Oversight | Dedicated committee or process |
| Shareholder Engagement | Investor dialogue program |
EXECUTIVE PRESENCE:
- Clarity: Simple, direct messages
- Confidence: Conviction without arrogance
- Credibility: Expertise and authenticity
- Connection: Empathy and engagement
- Composure: Calm under pressure
MESSAGE DEVELOPMENT:
What? → So what? → Now what?
(Facts) (Impact) (Action)STRUCTURE:
1. Opening (5 min)
- Connect personally
- Set context and agenda
2. Business Update (15 min)
- Performance highlights
- Key wins and learnings
- Challenges and plans
3. Strategic Focus (10 min)
- Priority initiatives
- Progress and next steps
- Resource allocation
4. Recognition (5 min)
- Celebrate successes
- Acknowledge teams
5. Q&A (20 min)
- Prepared questions
- Open forum
- Honest responses
6. Close (5 min)
- Summarize key points
- Call to action
- Express appreciationPREPARE:
- Clarify your objective
- Gather facts
- Anticipate reactions
- Plan key messages
CONDUCT:
1. State purpose directly
2. Share facts, not judgments
3. Listen for understanding
4. Acknowledge emotions
5. Explore solutions together
6. Agree on next steps
FOLLOW UP:
- Document agreements
- Monitor progress
- Provide support
- Address issues promptly| Competency | Behaviors |
|---|---|
| Vision | Sets direction, inspires others |
| Strategic Thinking | Systems perspective, anticipates trends |
| Driving Results | Accountability, execution focus |
| Leading People | Develops talent, builds teams |
| Collaboration | Influence, partnerships |
| Innovation | Curiosity, courage to experiment |
| Integrity | Ethics, transparency, trust |
| Resilience | Adaptability, learning from setbacks |
| Source | % of Development | Examples |
|---|---|---|
| Experience | 70% | Stretch assignments, job rotations, projects |
| Relationships | 20% | Mentoring, coaching, feedback, networking |
| Education | 10% | Training, courses, reading, conferences |
GROW MODEL:
Goal - Specific objective, timeline, success criteria
Reality - Current situation, obstacles, resources
Options - Brainstorm possibilities, evaluate pros/cons
Will - Action steps, accountability, commitment| Lever | Impact |
|---|---|
| What leaders pay attention to | Highest |
| How leaders react to crises | High |
| How resources are allocated | High |
| Role modeling and teaching | Medium-High |
| Who gets rewarded/promoted | High |
| Who gets hired/fired | High |
| Organizational design | Medium |
| Systems and processes | Medium |
| Physical space | Low-Medium |
| Stories and symbols | Medium |
1. DEFINE - Specific language, observable behaviors
2. COMMUNICATE - Stories, visual reinforcement, leader modeling
3. INTEGRATE - Hiring, performance, recognition, decisions
4. HOLD ACCOUNTABLE - Consequences for violations, celebrate exemplars© travisjneuman, 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 1 other file (references) in skills/leadership of travisjneuman/.claude.
Open the folder on GitHubat commit 446a461
Leadership 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 |
|---|---|---|---|---|---|---|
| Leadership this skilltravisjneuman/.claude | 100 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Natural Japanese Business Writingcoji/natural-japanese | 1.9k | — | ~2.1k | Automated safety check: Pass | MIT | |
| My Weekly Reportmeain/dotfiles | 285 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Updatesjtenniswood/espframe | 208 | — | ~527 | Automated safety check: Pass | Custom licence | |
| Updateakseolabs-seo/AK-Threads-booster | 275 | — | ~1.1k | Automated safety check: Notes | MIT |
anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill…
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
meain/dotfiles
Generate a concise weekly status update in team format. An agent skill from meain/dotfiles.
jtenniswood/espframe
Summarize user-facing changes made to this project over the last 7 days.
akseolabs-seo/AK-Threads-booster
Check AK-Threads-Booster for upstream GitHub updates, safely fast-forward the local skill repo, or install an opt-in weekly Codex automation that keeps the skill on the latest version.
sgharlow/claude-code-recipes
Turn scattered weekly updates (notes, emails, task exports, meeting notes) into a structured status report with highlights, progress, severity-rated blockers, and next-week priorities.
travisjneuman/.claude
Test-writing patterns for JS/TS, Python, Go, and Rust (unit, integration, E2E, visual regression).
travisjneuman/.claude
Write codebase documentation: READMEs, architecture docs, getting-started guides, API docs, and code comments.
travisjneuman/.claude
Business strategy expertise for strategic planning, competitive analysis, market entry, M&A strategy, portfolio management, and strategic decision-making.
travisjneuman/.claude
Data science and analytics expertise for statistical analysis, machine learning pipelines, data governance, business intelligence, predictive modeling, and analytics strategy.
travisjneuman/.claude
Financial analysis expertise for financial modeling (DCF, LBO, M&A), valuation, financial statement analysis, capital allocation, treasury management, and corporate finance decisions.
travisjneuman/.claude
Workplace health and wellness expertise for employee wellness programs, mental health initiatives, ergonomics and safety, healthcare benefits strategy, and health analytics.
Categories
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. claude. Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership.
Leadership fits situations like: managing change; navigating crises; developing leadership skills.
Run `npx skills add travisjneuman/.claude --skill leadership -a claude-code`. Or copy the skill folder (skills/leadership in travisjneuman/.claude) into .claude/skills/leadership in your project. Claude Code loads it when a task matches its description.
Run `npx skills add travisjneuman/.claude --skill leadership -a codex`. Or copy the skill folder (skills/leadership in travisjneuman/.claude) into .agents/skills/leadership 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 travisjneuman/.claude --skill leadership -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/leadership, .gemini/skills/leadership, .github/skills/leadership and .opencode/skills/leadership in your project.
SKILL.md names no scripts, command-line tools or credentials: Leadership 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.
Leadership is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 17k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Leadership: Internal Communications Writer (anthropics/skills, 180k stars), Natural Japanese Business Writing (coji/natural-japanese, 1.9k stars), My Weekly Report (meain/dotfiles, 285 stars) and Updates (jtenniswood/espframe, 208 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
travisjneuman (a GitHub user) maintains it in travisjneuman/.claude, which has 100 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 9, 2026.
Source: travisjneuman/.claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.