Eks Best Practices
aws-samples/appmod-blueprints
Advisory guidance for Amazon EKS architecture and configuration decisions — compute strategy, networking, security, reliability, cost, autoscaling, observability, multi-tenancy, and upgrade planning.
Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the…
Install Sales Demo Script
$ npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-demo-script --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/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sales-demo-script .claude/skills/sales-demo-script && 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 "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .claude/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-scriptType 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 mohitagw15856/pm-claude-skills --skill sales-demo-script -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-demo-script --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sales-demo-script .agents/skills/sales-demo-script && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .agents/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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 mohitagw15856/pm-claude-skills --skill sales-demo-script -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-demo-script --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sales-demo-script .cursor/skills/sales-demo-script && 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 "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .cursor/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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/mohitagw15856/pm-claude-skills.git --path skills/sales-demo-script--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 mohitagw15856/pm-claude-skills --skill sales-demo-script -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-demo-script --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sales-demo-script .gemini/skills/sales-demo-script && 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 "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .gemini/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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 mohitagw15856/pm-claude-skills sales-demo-scriptInstalls 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 mohitagw15856/pm-claude-skills --skill sales-demo-script -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sales-demo-script .github/skills/sales-demo-script && 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 "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .github/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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 mohitagw15856/pm-claude-skills --skill sales-demo-script -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills sales-demo-script --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sales-demo-script .opencode/skills/sales-demo-script && 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 "sales-demo-script" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/sales-demo-script into .opencode/skills/sales-demo-script/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sales-demo-script", 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.
Facts
- Skill name
sales-demo-script- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 540 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the…
- Works in 7 steps: Set the objective — the single… → Open with their world — restate the… → Design the shortest path — pick the 2–4… → …
- Asked to write a sales demo script
- SKILL.md covers What This Skill Produces, Required Inputs, Process and Output Format, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Sales Demo Script is an agent skill from mohitagw15856/pm-claude-skills. Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (backup video, reset state, narration bridge). Use when asked to write a sales demo script, structure a product demo, plan the demo talk track, our demos meander through features, or the demo broke live last time. Produces the scene-by-scene flow tied to buyer pain, talk track, aha moments…
Its SKILL.md is about 1.1k 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 DevOps & Cloud, covering Platform engineering and Text to speech and voice. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a sales demo script
- Structure a product demo
- Plan the demo talk track
- Our demos meander through features
Example prompts
- “/sales-demo-script”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Set the objective — the single feeling/decision the demo should produce.
- Open with their world — restate the pain; get agreement before showing anything.
- Design the shortest path — pick the 2–4 scenes that prove the value; cut the rest.
- Script talk track per scene — say the value, then show the feature as evidence.
- Mark the "aha" — the moment the payoff lands; slow down there.
- Write transitions — connect scenes with the buyer's logic, not the menu structure.
- Close — recap value in their words and ask for the specific next step.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
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.
Runs code
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.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sales Demo Script loads about 1.1k tokens when it runs. Until then it costs about 142 tokens; SKILL.md has 540 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.
Safety
Auto-check passed
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.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 540 words, ~1,056 tokens.
Download SKILL.mdSave it as
.claude/skills/sales-demo-script/SKILL.md (or your agent's skills folder).- name
- sales-demo-script
- description
- Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (backup video, reset state, narration bridge). Use when asked to write a sales demo script, structure a product demo, plan the demo talk track, our demos meander through features, or the demo broke live last time. Produces the scene-by-scene flow tied to buyer pain, talk track, aha moments, transitions, and a close with next steps.
Sales Demo Script Skill
Write a demo that makes a buyer feel their problem being solved — a value story, not a click-through of every screen. The best demos show the shortest path to the "aha," anchored in the pain the buyer already told you about.
What This Skill Produces
- A demo objective and the one thing the buyer should feel by the end
- Discovery hooks to tailor the demo live
- A scene-by-scene flow tied to buyer pain, with talk track
- Clearly marked "aha" moments and clean transitions
- A close with a concrete next step
Required Inputs
Ask for these if not provided:
- Product and the persona/buyer you're demoing to
- Their pain — what problem they're trying to solve (from discovery)
- The value story — the outcome the product delivers
- Key capabilities to show (and which to skip)
- Proof — data, before/after, or a realistic demo dataset
- Meeting context — first demo, technical deep-dive, competitive bake-off; time available
Use realistic sample data; don't imply results or claims you can't back — mark [to confirm].
Process
- Set the objective — the single feeling/decision the demo should produce.
- Open with their world — restate the pain; get agreement before showing anything.
- Design the shortest path — pick the 2–4 scenes that prove the value; cut the rest.
- Script talk track per scene — say the value, then show the feature as evidence.
- Mark the "aha" — the moment the payoff lands; slow down there.
- Write transitions — connect scenes with the buyer's logic, not the menu structure.
- Close — recap value in their words and ask for the specific next step.
Output Format
Demo Script — [Product] for [Persona]
Objective: [the one thing they should feel/decide] · Time: [minutes] · Context: [first demo / deep-dive]
Open (restate their world)
- Say: "[Restate the pain and the outcome they want]"
- Confirm: [question to get a yes before showing anything]
Discovery Hooks (tailor live)
- If they care about [X] → emphasize [scene]
- If they mention [Y] → show [capability]
Scene Flow
Show full SKILL.md (216 more words)Show less
Scene 1 — [Buyer outcome, not feature name]
- Setup: [the before state / realistic data]
- Say: [value-led talk track]
- Show: [the specific action]
- ✨ Aha: [the payoff moment — slow down]
Scene 2 — [Buyer outcome]
- Transition: "[connect from Scene 1 in buyer logic]"
- Say / Show / Aha: [...]
Handle Live Questions
- [Likely question] → [crisp answer, then return to the story]
Close
- Recap: "[value in the buyer's words]"
- Next step: [the specific ask — trial, technical eval, mutual plan]
Quality Checks
- The demo opens with the buyer's pain, not the product
- It shows the shortest path to the payoff, not every feature
- Each scene leads with value; the feature is the evidence
- "Aha" moments are explicitly marked
- Transitions follow buyer logic, not menu structure
- The close asks for a specific, concrete next step
Anti-Patterns
- Do not do a feature tour or "let me show you the settings"
- Do not start clicking before confirming the pain
- Do not demo on empty or unrealistic data
- Do not rush the "aha" — that's the moment that sells
- Do not end with "any questions?" — end with a next step
Example Trigger Phrases
- "Write a demo script for [product] to a [persona]"
- "Turn this feature list into a value-story demo"
- "Structure a 20-minute demo that leads with buyer pain"
- "Script the talk track and aha moments for our product demo"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/sales-demo-script of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Sales Demo Script 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 |
|---|---|---|---|---|---|---|
| Sales Demo Script this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Eks Best Practicesaws-samples/appmod-blueprints | 115 | — | ~5k | Automated safety check: Pass | MIT-0 | |
| Devops EngineerYikai-Liao/symusic | 189 | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Thermo Nuclear Reviewcursor/plugins | 11k | 1 repos | ~1.1k | Automated safety check: Pass | None | |
| Mcaf Devexmanagedcode/Storage | 138 | — | ~911 | Automated safety check: Pass | MIT | |
| Sap Btp Best Practicessecondsky/sap-skills | 462 | — | ~3.8k | Automated safety check: Pass | GPL-3.0 |
Similar skills
- Official
Devops Engineer
Yikai-Liao/symusic
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates.
- Official
Thermo Nuclear Review
cursor/plugins
Comprehensive security and correctness audit of a branch's changes.
Mcaf Devex
managedcode/Storage
Improve developer experience for multi-component solutions: onboarding, F5 contract, cross-platform tasks, local inner loop, and reproducible setup.
Sap Btp Best Practices
secondsky/sap-skills
SAP BTP best practices for enterprise architecture, account management, security, and operations, with verification evidence tracked in the repository ledger.
Patch Backstage
redhat-developer/rhdh
Workflow to backport Backstage changes into RHDH by syncing a downstream maintenance branch and generating yarn patches.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Sales Demo Script
What does Sales Demo Script do?
Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the…. Sales Demo Script is an agent skill from mohitagw15856/pm-claude-skills. Write a product demo script that tells a value story instead of a feature tour — the buyer's-workflow storyline, the golden path rehearsed with fallbacks, the wow moment placed early, and the demo-death contingencies (backup video, reset state, narration bridge).
When should I use Sales Demo Script?
Sales Demo Script fits situations like: asked to write a sales demo script; structure a product demo; plan the demo talk track; our demos meander through features.
How do I install Sales Demo Script in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script -a claude-code`. Or copy the skill folder (skills/sales-demo-script in mohitagw15856/pm-claude-skills) into .claude/skills/sales-demo-script in your project. Claude Code loads it when a task matches its description.
How do I install Sales Demo Script in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script -a codex`. Or copy the skill folder (skills/sales-demo-script in mohitagw15856/pm-claude-skills) into .agents/skills/sales-demo-script in your project. Codex loads it when a task matches its description.
Can I use Sales Demo Script in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill sales-demo-script -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sales-demo-script, .gemini/skills/sales-demo-script, .github/skills/sales-demo-script and .opencode/skills/sales-demo-script in your project.
What does Sales Demo Script need to run?
SKILL.md names no scripts, command-line tools or credentials: Sales Demo Script is instructions for the agent only.
Does Sales Demo Script access the network?
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.
Is Sales Demo Script safe to install?
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.
What licence does Sales Demo Script use?
Sales Demo Script is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sales Demo Script use?
About 1.1k tokens (SKILL.md is roughly 4.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Sales Demo Script?
Skills that share tags, products or a category with Sales Demo Script: Eks Best Practices (aws-samples/appmod-blueprints, 115 stars), Devops Engineer (Yikai-Liao/symusic, 189 stars), Thermo Nuclear Review (cursor/plugins, 11k stars) and Mcaf Devex (managedcode/Storage, 138 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sales Demo Script?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-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.