Pptx deck context
Skill bg-szy/TOP-SKILLS/skills/awesome-skills/pptx-deck-context
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill pptx-deck-contextAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when preparing the narrative, sources, and design context for a new editable PPTX deck.
SKILL.md
1.6 KB, as published. Nobody here has run it
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.