使用方法
- 复制安装命令，在自己的智能体环境安装前先检查源码包。
- 从原始文档核对所需工具、凭据和支持的宿主。
- 说明输入材料与期望交付物，并对照来源检查输出。
npx skills add https://github.com/wshobson/agents --skill pptx-deck-context开始前需了解
- 安装不包含模型订阅、API 额度或访问文件的权限。
- 仓库星数和安装量反映活跃情况，不等于独立质量或安全测试。
仓库原始内容
按源仓库内容呈现，保留标题、案例、代码、表格、链接以及原文引用的演示图片。
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.
