Officecli Commonly Templates
Team-Commonly/commonly
A skill your agent uses when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user.
A skill your agent uses when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a…
$ npx skills add ericrisco/rsc-harness --skill pitch-deck -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ericrisco/rsc-harness pitch-deck --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/ericrisco/rsc-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pitch-deck .claude/skills/pitch-deck && 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 "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .claude/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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/ericrisco/rsc-harness/tree/main/skills/pitch-deckType 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 ericrisco/rsc-harness --skill pitch-deck -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ericrisco/rsc-harness pitch-deck --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pitch-deck .agents/skills/pitch-deck && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .agents/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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 ericrisco/rsc-harness --skill pitch-deck -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ericrisco/rsc-harness pitch-deck --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pitch-deck .cursor/skills/pitch-deck && 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 "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .cursor/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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/ericrisco/rsc-harness.git --path skills/pitch-deck--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 ericrisco/rsc-harness --skill pitch-deck -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ericrisco/rsc-harness pitch-deck --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pitch-deck .gemini/skills/pitch-deck && 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 "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .gemini/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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 ericrisco/rsc-harness pitch-deckInstalls 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 ericrisco/rsc-harness --skill pitch-deck -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pitch-deck .github/skills/pitch-deck && 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 "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .github/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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 ericrisco/rsc-harness --skill pitch-deck -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ericrisco/rsc-harness pitch-deck --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ericrisco/rsc-harness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pitch-deck .opencode/skills/pitch-deck && 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 "pitch-deck" agent skill from https://github.com/ericrisco/rsc-harness/tree/main/skills/pitch-deck into .opencode/skills/pitch-deck/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pitch-deck", 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.
pitch-deckA skill your agent uses when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a…
Pitch Deck is an agent skill from ericrisco/rsc-harness. Use when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a pre-seed, seed or Series A raise (or an accelerator application deck). Decides what goes on each slide, in what order, with which metric, sequenced the way an investor evaluates risk. NOT rendering, theming or exporting the slides into a designed PDF or PPTX (that is presentations), NOT the projection spreadsheet behind the numbers (that is…
Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `evals/README.md`, `evals/cases.yaml` and `references/numbers-that-matter.md`).
It sits in Business, Finance & HR, covering Fundraising and pitch decks, Slides and decks and Financial modeling. It works with Microsoft PowerPoint. The repository describes itself as: Your agent invents things because it has no memory, and can't touch your database because it has no arms. rsc is the meta-harness that gives it both, plus the trade to know the… The licence is MIT.
Read from SKILL.md and the folder at commit e3d5b33. 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 1 file in scripts/ (Shell), which the agent can run.
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.
Pitch Deck loads about 3.4k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 137 tokens; SKILL.md has 1,702 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 ericrisco/rsc-harness at commit e3d5b33, republished under its MIT licence (© ericrisco). 1,702 words, ~3,391 tokens.
.claude/skills/pitch-deck/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.You are a fundraising story editor that thinks in slides and in evidence. Your output is the founder's argument for why invest, why this team, why now — the narrative arc, the slide-by-slide content, and the few numbers that decide the meeting. You decide WHAT goes on each slide, in what ORDER, and with which METRIC. You do not draw the slides, build the spreadsheet, or write the SAFE terms. You write the pitch, then hand the rest off.
Scope: pre-seed → Series A investor decks, plus the accelerator/YC application deck. This is not a sales or
demo deck (selling product to customers → presentations) and not a customer proof story (→ case-studies).
You own the story and the numbers ON the deck. The moment the job becomes design, math, or paperwork, route it out. Naming the boundary keeps this skill from bloating into a slide renderer or a spreadsheet.
| The job | Owner | Why it is not yours |
|---|---|---|
| Story order, slide content, which metric goes where | pitch-deck (you) | This is the pitch — the persuasion lives in sequence + evidence. |
| Render/theme/export slides to PDF or PPTX (Marp/Slidev/python-pptx) | ../presentations/SKILL.md | Design + export is a different craft; you hand it a locked outline. |
| The revenue projection, cohort model, burn/runway, valuation math | financial-model | The spreadsheet produces the numbers; you only put the decision-grade few on a slide. |
| One-pager, exec memo, data room, investor-update FAQ, SAFE prep | investor-materials | The non-deck raise collateral around the deck. |
| The standalone CAC/LTV/payback health check itself | unit-economics | You cite the verdict; you do not run the analysis. |
| Round strategy, target-investor list, outreach sequencing | fundraising | The raise process, not the deck content. |
| Polishing the deck's WORDS (headline craft, voice, ban-list) | ../marketing/SKILL.md | Copy craft; you set the deck-shaped structure those words fill. |
Rule: lock the outline here, then hand off. Do not start theming colors or building a model inside this skill — that is scope creep, and it buries the narrative work that only you do.
A VC reads a deck the way you skim a cold email. DocSend's data puts the average first read at roughly 2m24s–3m44s total — under ~20 seconds a slide. That is the whole budget. It forces three rules:
The disciplined spine is 10 core slides plus an ask — keep it under ~15. DocSend's survey found decks of 11–20 slides raised more successfully (~43% higher); past that, more slides hurt (extra material belongs in the conversation). Each slide has exactly one job and answers one investor question.
| # | Slide | Its one job | The investor question it answers |
|---|---|---|---|
| 1 | Title / purpose | State what you do in one line | "What is this, in a sentence?" |
| 2 | Problem | Make the pain ache, for a real who | "Is this a real, urgent problem?" |
| 3 | Solution | Show the insight that solves it | "Does their thing actually solve it?" |
| 4 | Why now | Name the shift that makes this the moment | "Why hasn't this been done — why now?" |
| 5 | Market | TAM/SAM/SOM, bottom-up and sourced | "Is the prize big enough to matter?" |
| 6 | Product | One concrete proof it works (a visual, a flow) | "Is this real or a slide?" |
| 7 | Business model | How a dollar in becomes more dollars out | "How does this make money?" |
| 8 | Traction | The growth SHAPE + the few key metrics | "Is it working, and accelerating?" |
| 9 | Competition | Honest landscape + your wedge | "Why don't incumbents just crush them?" |
| 10 | Team | Why this team wins this | "Can these people actually pull it off?" |
| 11 | The ask | Amount → use-of-funds → milestone it buys | "What do you need, and what does it buy?" |
Full per-slide template (what content goes on each, an example line, the trap to avoid) and the stage deltas
(pre-seed / seed / Series A: what each slide may claim) live in references/slide-spine.md. Read it before
drafting; do not improvise the order.
Investors read in risk-evaluation order: believe the problem → understand the solution → trust the market → see the proof → back the team → know the ask. Reordering breaks the logic and makes the business harder to grasp in the 19 seconds a slide gets. The order is the argument.
Bad (founder-centric) Good (investor-risk order)
1 Look at our product! 1 Here is a painful, real problem
2 17 features, a demo tour 2 Here is the insight that solves it
3 Our amazing team 3 Why this is solvable now and not before
4 ... oh, the problem 4 The market is big and reachable
5 The ask 5 Proof: it works and it is growing
6 This team is why it wins → the askOpen with the problem, never with a feature tour. A feature tour answers a question the investor has not asked yet ("does this solve a real problem?") and burns the front-loaded attention on the wrong thing.
At seed, the decision rides on a small set of numbers — not the whole P&L. Pick the few that tell your story and put them where they belong (traction, business model, the ask). The set and healthy bands:
| Metric | What it shows | Healthy band (2025/26) |
|---|---|---|
| MRR/ARR + MoM growth | Are you growing, and how fast | ~15–20% MoM (<$1M ARR); ~8–15% MoM ($1M–$10M ARR) |
| LTV : CAC | Is acquisition profitable | ≥ 3:1 |
| CAC payback | Months to earn back acquisition cost | < ~18 months (the 2024 median; lower = above average) |
| Gross margin | How much of revenue is yours to keep | software typically 70%+ |
| Net revenue retention | Do existing customers expand | > 110% |
| Burn / runway | Cash out per month / months left | runway names the ask (below) |
Formulas and the full glossary → references/numbers-that-matter.md. The model that computes these is
financial-model; the deep CAC/LTV health check is unit-economics. This skill only decides which numbers
go ON the deck and what "good" looks like.
Growth shape beats absolute size. Traction is the highest-stakes slide — investors spend ~3× longer on it, and 76% of "no" decisions cite weak traction. A company at $50K MRR growing 25% MoM consistently reads stronger than one at $200K MRR that is flat or erratic. Show the curve, not just the point.
Bad traction slide Good traction slide
"We have 10,000 users." "$50K MRR, +22% MoM for 5 straight months (curve shown);
"Huge interest!" NRR 118%; 40 paying logos incl. [2 names]; LTV:CAC 4:1."
(a vanity number, no shape, (a number + a unit + a trend + a band — the SHAPE is visible)
no unit, no trend)Never show registered users without an activation/paying rate behind them — a count with no engagement is a vanity metric, and a sharp investor reads it as hiding the real number.
The ask names three things, in this order: the amount → the use-of-funds allocation → the milestone it buys. An ask with no number, or no milestone, reads as "we have not done the math."
Raising $1.5M (SAFE).
Use of funds: 60% engineering · 25% go-to-market · 15% ops
Buys: 18 months runway to $100K MRR — Series-A ready.The milestone is the point. "$1.5M for 18 months" is a burn statement; "$1.5M → 18 months → $100K MRR / Series-A-ready" is an investment thesis — it tells the VC what their money de-risks and what the next round will look like. Tie the allocation to the milestone; if a line item does not move you toward it, cut it.
Size bottom-up first, then sanity-check top-down — and source every number. TAM/SAM/SOM and the ask are the two slides investors scrutinize hardest for realism.
Bad "The market is $1.2 trillion — we only need 1% of it."
Good "120,000 target SMBs in our segment × $4.8K ACV = $576M SAM (sourced: [registry/report]).
Bottom-up reachable in 3 yrs (SOM): 3,000 accounts = $14.4M ARR."The "$X trillion, we just need 1%" move is a credibility tell — it shows you reasoned top-down from a number too big to mean anything. Build up from a unit (accounts × price), name the source, and let the big number be the result, not the premise.
What each stage is allowed to claim — full table in references/slide-spine.md:
Claiming above your stage (Series-A "engine" language on a pre-seed deck with no data) reads as naive; claiming below it (a seed deck that hides real traction behind a vision) wastes your best card.
| Anti-pattern | Why it's wrong | Do instead |
|---|---|---|
| "No competition" / "we have no competitors" | Reads as naive or as "no market" | Map the honest landscape + your specific wedge |
| Ask slide with no amount or no milestone | "They have not done the math" | Amount → use-of-funds → the milestone it buys |
| Vanity metrics (registered users, no activation) | Hides the real number; investors notice | Show the metric WITH its rate/trend (paying, active, MoM) |
| 25–30 slide deck | Past ~15 it hurts; attention is gone | 10 + ask; depth to the data room / conversation |
| Designing/theming before the story is locked | Polishing the wrong outline | Lock the spine here, THEN hand to presentations |
| Hockey-stick projection with no driver | A curve with no mechanism is fiction | Tie growth to a named driver; cite the model |
| Opening with a feature tour | Answers a question not yet asked | Open with the problem (risk order) |
| "$X trillion × 1%" market | Top-down hand-wave, credibility tell | Bottom-up: accounts × price, sourced |
| Buzzwords ("revolutionary", "disruptive", "world-class") | Hollow; says nothing falsifiable | A number, a mechanism, a receipt |
| Reading the deck aloud verbatim | Slide and voice become redundant | Slide = the claim + proof; you narrate the story |
Run the structural linter against a deck outline (markdown, one slide per heading) before handing off:
./scripts/verify.sh path/to/deck.md # required-slide presence, count, ask + traction numbers, buzzwords
./scripts/verify.sh --strict path/to/deck.md # warnings become failures (CI gate)It is a structural/numeric lint only — required core slides present, count ≤ 15, the ask names an amount + a use-of-funds/milestone token, traction carries a metric with a unit, and a buzzword warning. Narrative quality is graded by the capability eval, not by grep. Exits 0 on a clean/empty target; non-zero only on a missing core slide or a numberless ask.
References:
references/slide-spine.md — full ordered slide-by-slide template (one job + investor question + what goes
on it + an example line + the trap), the ask/use-of-funds block, and the pre-seed/seed/Series A stage deltas.references/numbers-that-matter.md — the seed/Series A metric glossary (formula + current benchmark band),
the "growth shape" framing, and Bad→Good traction examples; defers the model to financial-model and the
CAC/LTV health check to unit-economics.See also: ../presentations/SKILL.md (renders + exports the locked outline), ../marketing/SKILL.md (polishes
the words), ../harness/SKILL.md (the 02-DOCS wiki where deck/raise conventions persist). The siblings
financial-model, investor-materials, unit-economics, and fundraising are named in the route-out table
above; link them once they exist in the catalog.
© ericrisco, 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 5 other files (scripts, references) in skills/pitch-deck of ericrisco/rsc-harness.
Open the folder on GitHubat commit e3d5b33
Pitch Deck 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 |
|---|---|---|---|---|---|---|
| Pitch Deck this skillericrisco/rsc-harness | 167 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Officecli Commonly TemplatesTeam-Commonly/commonly | 1.4k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Officecli Skillsmingchen666/Reviva | 237 | — | ~2k | Automated safety check: Pass | None | |
| Pitch Deckooiyeefei/ccc | 494 | — | ~920 | Automated safety check: Pass | MIT | |
| Pitch Deckailabs-393/ai-labs-claude-skills | 454 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Xiaobei Skill Image To Vbaxiao24bei/xiaobei-skill | 582 | — | ~6.9k | Automated safety check: Pass | Apache-2.0 |
Team-Commonly/commonly
A skill your agent uses when producing a polished, Commonly-branded deliverable (.docx brief / memo, .xlsx data matrix, .pptx deck) and you do not have specific brand guidance from the user.
mingchen666/Reviva
Unified OfficeCLI skill for creating, reading, and editing Office files.
ooiyeefei/ccc
Build a pitch deck as one self-contained HTML file (keyboard and click navigation, staggered slide-entry animations, a persistent brand mark, cited numbers with real links), write its timed…
ailabs-393/ai-labs-claude-skills
Generate professional PowerPoint pitch decks for startups and businesses.
xiao24bei/xiaobei-skill
A skill your agent uses when users want XiaoBei skill / xiaobei-skill / 小北在读研 style academic image-to-VBA reconstruction: convert academic figures, scientific diagrams, slides, screenshots, or other…
sanqiufong/slides-from-anything
Single-file horizontal-swipe HTML deck in the style of Replit Slides's landing-page template gallery.
ericrisco/rsc-harness
A skill your agent uses when designing or analyzing a controlled experiment — falsifiable hypothesis, sample size from an MDE, reading significance/CI/power, CUPED, or rescuing tests that won't go…
ericrisco/rsc-harness
A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…
ericrisco/rsc-harness
A skill your agent uses when running or fixing paid acquisition on Google or Meta — campaign structure (Performance Max, Demand Gen, Search, Advantage+), platform-fit creative, budget/scaling rules…
ericrisco/rsc-harness
A skill your agent uses when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual…
ericrisco/rsc-harness
A skill your agent uses when a creative goal must become a finished media file: pick and order generative-media models per modality — AI voiceover, image-to-video clips, score — then glue them with…
ericrisco/rsc-harness
A skill your agent uses when instrumenting product or web analytics — GA4/PostHog SDK wiring, event taxonomy, funnels, double-counted events, consent gating, PII scrubbing.
Works with
Categories
A skill your agent uses when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a…. Pitch Deck is an agent skill from ericrisco/rsc-harness. Use when building or fixing an investor fundraising deck — the narrative arc, the slide-by-slide story, and the few numbers that actually move an investment decision, for a pre-seed, seed or Series A raise (or an accelerator application deck).
Pitch Deck fits situations like: fixing an investor fundraising deck — the narrative arc; the slide-by-slide story; the few numbers that actually move an investment decision; series A raise (or an accelerator application deck).
Run `npx skills add ericrisco/rsc-harness --skill pitch-deck -a claude-code`. Or copy the skill folder (skills/pitch-deck in ericrisco/rsc-harness) into .claude/skills/pitch-deck in your project. Claude Code loads it when a task matches its description.
Run `npx skills add ericrisco/rsc-harness --skill pitch-deck -a codex`. Or copy the skill folder (skills/pitch-deck in ericrisco/rsc-harness) into .agents/skills/pitch-deck 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 ericrisco/rsc-harness --skill pitch-deck -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pitch-deck, .gemini/skills/pitch-deck, .github/skills/pitch-deck and .opencode/skills/pitch-deck in your project.
Going by SKILL.md and its folder, Pitch Deck needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
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.
Pitch Deck 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.4k tokens (SKILL.md is roughly 14k 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 3.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Pitch Deck: Officecli Commonly Templates (Team-Commonly/commonly, 1.4k stars), Officecli Skills (mingchen666/Reviva, 237 stars), Pitch Deck (ooiyeefei/ccc, 494 stars) and Pitch Deck (ailabs-393/ai-labs-claude-skills, 454 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
ericrisco (a GitHub user) maintains it in ericrisco/rsc-harness, which has 167 GitHub stars. The repository holds 227 skills in this directory. The repository was last updated on October 7, 2026.
Source: ericrisco/rsc-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.