菜单
Implement or specify save, version, publish, share, public page, iframe embed, analytics, and access-policy behavior for a DeckForge-compatible web presentation.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/tph-kds/deckforge --skill deckforge-publish命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Create, redesign, or extend a professional browser-native slide deck or presentation webapp. Activate for end-user requests such as “create slides”, “make a presentation website”, pitch decks, lessons, seminars, technical talks, web slide editors, presenter mode, slide templates, animations, or presentation UI/UX. Unless the user explicitly requests presenter-only output, deliver an editable deck with a real editor workspace, persistent save, theme/layout controls, shortcut help, and a separate clean presenter surface. Do not use for PPTX-only requests.
Add or repair export capabilities for a DeckForge-compatible or custom web slide application without redesigning the entire product. Activate for requests to add PowerPoint download, fix export issues, add multiple export formats, audit export readiness, or add PPTX export with preflight checks.
Evaluate and improve DeckForge Agent Skills by comparing baseline, current, and candidate conditions on deterministic outcome tests, trigger precision, blind review, context cost, runtime, and cross-agent consistency. Use for skill development and release gates; do not use for end-user deck creation.
基于 SOC 职业分类
正在显示 SKILL.md
| name | deckforge-publish |
| description | Implement or specify save, version, publish, share, public page, iframe embed, analytics, and access-policy behavior for a DeckForge-compatible web presentation. |
| version | 3.0.0 |
Read ../deckforge/built-in-skills/publish-and-embed.md, ../deckforge/built-in-skills/security.md, ../deckforge/assets/deck-project.schema.json, and ../../docs/RUNTIME_CONTRACT.md.
Inspect the target application's authentication, authorization, persistence, asset delivery, routing, CSP, telemetry, and deployment model before designing the publishing flow. Preserve the existing stack when it is coherent.
Define or implement explicit states for draft, private, unlisted, and public decks; immutable or restorable versions; safe slug changes; share links; revocation; and embed policies. Validate ownership, workspace membership, visibility, version, origin allow-list, iframe sandbox, token expiry, asset URLs, analytics privacy, and cache behavior at runtime boundaries. Never trust security fields supplied only by the client-side deck document.
Return the API and data contracts, UI states, error paths, tests, and rollout considerations needed for production. Keep editor-only controls out of the published audience route. Do not expose credentials, unrestricted embed tokens, private notes, comments, or hidden source material in public responses.
