wshobson/pptx-deck-context
plugins/pptx-deck-creation/skills/pptx-deck-context/SKILL.md
Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
$ install --global
skillsauthnpx skillsauth add wshobson/agents pptx-deck-contextInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 19, 2026, 2:18 AM106.0s2 files scanned
SKILL.md
- name:
- pptx-deck-context
- description:
- Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
PPTX Deck Context
Prepare the deck before coordinates or PPTX objects are authored. This skill owns the business narrative, source lineage, and design lock.
Decision sequence
- Confirm audience, decision, slide count, language, sources, and brand requirements.
- Use the user-selected narrative framework. If none is specified, offer
mckinsey,scqa,pyramid,mece,action-title,assertion-evidence,exec-summary-first, orcustom; do not choose silently. - Assign stable source IDs and plan a
source_reffor every metric, quotation, chart value, and factual claim. - Choose a documented design direction. Prefer a user brand guide, then read-only reference-deck evidence, then a reusable profile from
references/design-profiles.md. - Record the framework, assumptions, source manifest, palette, typography, spacing, and signature elements in
summarybefore authoring slides.
Rules
- One slide should communicate one message, with an action-style title where the framework calls for it.
- Treat design references as design evidence, not content or asset sources.
- Do not copy external fonts, images, icons, or logos without recorded licensing evidence.
- Translate design signals into explicit fills, typography, spacing, and bboxes; do not rely on an automatic layout engine.
- Keep long source material concise. Ask for a summary or decision-relevant excerpt instead of turning a deck spec into a document dump.
See references/design-profiles.md for reusable profile guidance.
Related Skills
wshobson/hermes-tweet
tools
VerifiedTrustedCommunity
Install and operate Hermes Tweet, a Hermes Agent plugin for X/Twitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X/Twitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X/Twitter context. Requires XQUIK_API_KEY for read and action tools.
39,228SKILL.mdUpdated Jul 9, 2026
wshobson/avoid-ai-writing
testing
VerifiedTrustedCommunity
Audit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode, a rewrite mode, and an edit-in-place mode, with optional voice and context profiles.
38,906SKILL.mdUpdated Aug 19, 2026
wshobson/python-design-patterns
development
VerifiedTrustedCommunity
Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.
38,906SKILL.mdUpdated Apr 25, 2026
wshobson/prompt-engineering-patterns
development
VerifiedTrustedCommunity
This skill should be used when the user asks to "optimize a prompt", "improve prompt performance", "design a prompt template", "write better prompts", "debug prompt issues", "use chain-of-thought", "structured prompting", "few-shot prompting", or wants to apply advanced prompt engineering patterns for production LLM applications.
38,906SKILL.mdUpdated Apr 25, 2026