Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SlideSpeak/slide-design-skill --skill product-marketinggit clone --depth 1 https://github.com/SlideSpeak/slide-design-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/slidespeak/slide-design-skill/product-marketing)<a href="https://agentmods.dev/skills/slidespeak/slide-design-skill/product-marketing"><img src="https://agentmods.dev/badge/skills/slidespeak/slide-design-skill/product-marketing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/slidespeak/slide-design-skill/product-marketing"><img src="https://agentmods.dev/badge/skills/slidespeak/slide-design-skill/product-marketing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.00950 |
| Opus 5.5 | $0.00024 | $0.00380 |
| Sonnet 5.5 | $0.00012 | $0.00190 |
| Haiku 4.5 | $0.00006 | $0.00095 |
Grade A, and why
product-marketing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Marketing Style — Authoring Guide
You write decks as if you are the PMM lead at a respected modern SaaS company launching a product. The audience is customers, press, or internal sales enablement.
Voice
- Lead with benefit, not feature. "Your team ships 4× faster" before "Real-time sync".
- Second person ("you", "your team").
- Specific not generic. "Cut your invoice cycle from 11 to 3 days" not "Save time".
- Use customer language, not internal jargon. If the user has provided customer quotes, lift them verbatim.
- One claim per slide. The deck reads as a story, not a list.
Structure (canonical launch arc)
- Cover — product name + single-line positioning + launch date
- Status quo — what's broken about the current world
- The shift — what changed (technology, behavior, market)
- The product — name + headline benefit + hero visual
- Features (3-5 slides) — one feature per slide, benefit-led headline
- Customer proof — quote + logo (logo region blank per constraint) + metric
- Pricing & availability — tiers, launch date, regions
- CTA — single next step (sign up, request demo, etc.)
Visual System
- Hero color: ONE bold brand color used as full-bleed ground on cover + section dividers + CTA.
- Body slides: white ground (#FFFFFF), near-black ink (#0A0A0A).
- Hero color reappears as accent on body slides (eyebrow tag, underline, big metrics).
- Display headlines: 96-144px on cover, 56-72px on body.
- UI mockups have rounded corners (radius 16-24px), gentle shadow, never tilted.
- No competing accent colors on a single slide.
Graphic system
- Signature mark: the stage light. Hero slides (cover, CTA) sit on a violet spotlight field with one large halo ring cropped by the top-right canvas edge. The light is the brand gesture; content slides stay on white.
- Structural device: the chip. Every section label is a small filled pill (violet tint on light slides, muted gray variant for the status quo), sentence case, never a bare mono label.
- Evidence and hero captions sit on a 6% violet tinted surface, never behind a colored edge stripe.
- Depth moment: customer proof carries one giant pale quote mark behind the quotation; the cover halo crops off-canvas.
- The system never does: spotlight on content slides, more than one halo, chips stacked in rows as decoration.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 71 lines · 59 tokens per session scan A 26608370ec5a
product-marketing is a skill published in the GitHub repository SlideSpeak/slide-design-skill (29 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 950 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
queues-jobs
Implement reliable asynchronous jobs and message consumers with explicit delivery, retry and shutdown semantics. Use when adding BullMQ or another established queue, background processing or scheduled work; enqueue success is not job completion.