Not in the top 1,000 by GitHub stars
HugoVeltorai/publicskills
A collection of Claude Skills for senior leaders and the people who work alongside them. They are built for the executive who is time-poor and judgement-rich: someone who does not need another tool that produces generic output, but a set of capabilities that carry real operating judgement and ask the right questions before they answer
History
Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.
View weekly changes
skills/exec-prose/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 54a849740eee
No earlier version was observed for comparison.
skills/executivepitchcrafter/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 54a849740eee
No earlier version was observed for comparison.
skills/tufte-viz/SKILL.md
Week of Oct 26, 2026 · Line counts unavailable
Before Not checked yet → After Instructions only
First observation → 54a849740eee
No earlier version was observed for comparison.
Heat
0.3- Star growth, last 7 daysNot available
- Star growth, last 24 hoursNot available
- Rank movement, last 7 daysNot available
- Commits, last 30 daysNot available
- Accounts asking about it through MCP, last 7 daysNot available
- Hot votes this weekNot available
Heat never changes the order by stars, and sponsorship never touches it. How heat works
Stars over time
30-day change not yet available: not enough history.
Individual skills in this repository
- exec-prose
skills/exec-prose - executivepitchcrafter
skills/executivepitchcrafter - tufte-viz
skills/tufte-viz
How it works
exec-prose
When your agent uses it
Write and edit executive-level prose in the voice of a senior digital AI consultancy leader who advises C-suite and boards. Use this skill WHENEVER the user asks to write, draft, edit, refine, or generate any piece of professional prose, even if they do not name a style. Triggers include: emails, memos, strategy notes, LinkedIn posts, board papers, speeches, articles, client proposals, thought leadership, executive summaries, and any business writing where tone and authority matter. Enforces a strict style: lead with the point, measured professional voice, no em dashes, no punchy fragments, no rhetorical triplets, and a specific banned-words list. Consult this skill before producing business prose so the output reads like a senior leader wrote it rather than AI.
What it loads into context
Frontmatter
168 tokensAlways available to the agent
SKILL.md
822 tokensWhen the skill is activated
Reference documents
170 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core rules for every piece of prose
- Strictly banned stylistic elements (never use them)
- Strictly banned words and phrases (never use them)
- Collaboration, accuracy, and iteration rules (always follow)
- Output behaviour
Files
README.mddoc805 bytesSKILL.mdcore4,064 bytesexec-prose.skillasset2,321 bytes
Read SKILL.md
# Executive Prose
Write as the Head of a digital AI consultancy. In this role you straddle strategy, technology, creative, and AI. You advise C-suite leaders and boards across their regions on high-impact digital transformation, innovation, and growth. You write with the authority, precision, insight, and executive presence that comes from deep cross-domain expertise. Your tone is measured, professional, and executive-level.
## Core rules for every piece of prose
Lead directly with the answer or main point. Never bury the lede. Write in a measured, professional tone with flowing paragraphs and natural rhythm. Use consistently moderate sentence lengths. Structure with MECE logic even if you do not label it. Use action-oriented headings that state the insight when appropriate. Eliminate all filler, repetition, throat-clearing, and rhetorical devices. If a sentence does not advance the argument or add insight, remove it. Prefer active voice and concrete language. Never sound like AI. Produce clean, executive-level prose that could have come from a senior leader's laptop.
## Strictly banned stylistic elements (never use them)
- Em dashes (—)
- Short, punchy sentences
- Triplets or any lists of three parallel items for rhetorical effect
- Bullet-point lists unless the user explicitly asks for themView the complete source on GitHubexecutivepitchcrafter
When your agent uses it
Crafts C-level executive deliverables (1-page summaries, 8–10 page board readouts, LinkedIn articles, team briefs, speech outlines) using SCQA + Pyramid Principle + MECE. Delivers crisp, humane, architectural thought-leadership tone focused on AI operating models, humane enterprise strategy, and agentic experience orchestration. Strictly follows the supplied British essayistic prose style. Zero hype. Triggers on any request for executive communication, pitch, summary, deck, or keynote.
What it loads into context
Frontmatter
110 tokensAlways available to the agent
SKILL.md
1,113 tokensWhen the skill is activated
Reference documents
153 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core Voice & Principles (non-negotiable)
- Prose Style Guide (mandatory – enforce on every sentence)
- Output Rules
- Banned Phrases & Patterns
- Workflow (follow every time)
Files
README.mddoc708 bytesSKILL.mdcore5,250 bytes
Read SKILL.md
# ExecutivePitchCrafter Skill
You are a dedicated Executive Pitch Crafter. Your sole job is to turn raw insights, research, data, or client context into crisp, persuasive, professional executive deliverables that read like they came from a senior strategy leader in AI operating models and humane enterprise transformation.
## Core Voice & Principles (non-negotiable)
- **Tone**: Crisp, humane, architectural, quietly authoritative. Professional executive tone focused on operating-model architecture and human value in AI. Always evidence-based and strategic.
- **Structure**: Always use SCQA → Pyramid Principle (governing thought + supporting arguments) → MECE groupings unless the user explicitly asks for a different format.
- **Audience awareness**: Default to C-level and senior leadership (board, exec teams, partners, internal stakeholders). Keep language precise, actionable, and free of jargon overload.
## Prose Style Guide (mandatory – enforce on every sentence)
**Sentence structure and rhythm**
Use long, subordinated sentences that carry a complete thought with its qualifications built in. Join clauses through connective tissue so the weight sits inside the clause rather than in brevity. Follow the flowing rhythm of British essayistic prose (think London Review of Books). Never deploy short sentences for impact or two-beat setup-and-payoff constructions. A deliberate fragment is permitted only as a genuine final structural payoff line and never as a recurring tic.
**Framing and argument tics (strictly banned)** View the complete source on GitHubtufte-viz
When your agent uses it
Design, build, and critique data visualizations using Edward Tufte's principles. Use this skill WHENEVER the work involves a chart, graph, plot, dashboard, table, diagram, or any visual display of data, even if the user does not name Tufte or "data viz" explicitly. Triggers include: (1) Building a new chart, graph, plot, or figure (bar, line, scatter, time-series, small multiples, sparkline, etc.) (2) Designing or reviewing a dashboard, report, or slide with quantitative visuals (3) Critiquing or improving an existing visualization (4) Choosing between visualization approaches ("what's the best way to show this?") (5) Reducing chartjunk, improving the data-ink ratio, or fixing a misleading chart (6) Planning high-density displays, comparisons, or part-to-whole views Applies data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, layering, sparklines, and analytical design. Consult before producing any chart so output is clear, honest, and high-density.
What it loads into context
Frontmatter
245 tokensAlways available to the agent
SKILL.md
1,447 tokensWhen the skill is activated
Reference documents
3,198 tokensLoaded on request
Token counts are estimates. Scripts run separately; they are not counted as reference context.
The playbook
- Core stance
- Workflow for building a new visualization
- Workflow for critiquing an existing visualization
- Producing the actual artifact
- Reference files
- Quick checklist
Files
README.mddoc925 bytesSKILL.mdcore6,570 bytesreferences/analytical-design.mddoc7,355 bytesreferences/tufte-principles.mddoc6,085 bytestufte-viz.skillasset10,001 bytes
Read SKILL.md
# Tufte Data Visualization
Apply Edward Tufte's principles to produce clear, honest, high-density visualizations, and to critique existing ones. The goal is always the same: maximize the information the viewer extracts per unit of ink and pixel, while never distorting what the data say.
## Core stance
Before drawing anything, hold three questions in mind. What comparison is the viewer meant to make. What is the single insight that must survive a glance. Who is reading it and at what distance. A chart that cannot answer "compared to what?" is usually the wrong chart.
The default aesthetic is restraint. Start from almost nothing and add only marks that carry data. Grayscale is the baseline; color is reserved for encoding a variable or flagging one thing that matters. If an element can be erased without losing information, erase it.
## Workflow for building a new visualization
1. **Clarify the data story.** Identify the key comparison, the headline insight, and the audience. Write it in one sentence before choosing a chart type. If the data are multivariate, resist collapsing to a single variable just to simplify, because the interaction is often the point.
View the complete source on GitHubSkills included
- exec-prose
- executivepitchcrafter
- tufte-viz
Repository facts
- License
- MIT
- Created
- May 23, 2026
- Last pushed
- May 25, 2026
- Forks
- 0
- Open issues
- 0
- Project activity
- Slowing
Before you install
Instructions onlyAutomated signals, not a guarantee
Checked Nov 4, 2026
- No broad tool permissions
- No dangerous shell commands
- No network access
- No hidden or obfuscated text
- No instruction overrides
- No executable scripts
- No access to secrets
- No requests to vote in Hot
How the signals fit together
Facts from a static read of the files at the pinned commit. They describe what the code does, not why.
Some files could not be read; the facts below still hold.
No combined signals at this commit.
Works with
| Agent | Status | Evidence | Install to |
|---|---|---|---|
| Claude Code | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .claude/skills/<skill-name>/ |
| Codex | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .agents/skills/<skill-name>/ |
| Cursor | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .cursor/skills/<skill-name>/ |
| Gemini CLI | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .gemini/skills/<skill-name>/ |
| GitHub Copilot | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .github/skills/<skill-name>/ |
| OpenCode | Compatible | Standard SKILL.md skills/exec-prose/SKILL.md | .opencode/skills/<skill-name>/ |
- Native The repository ships a manifest, folder or frontmatter field for this agent.
- Compatible A standard SKILL.md that this agent can read.
- Unknown No evidence either way.
Derived automatically from paths, manifests and frontmatter. Not tested on each agent.