Token导航 LogoToken导航

Agent Skill · 研究检索

deck-creator(套牌创造者)

deck-creator 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

deck-creator 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 47,060。

总安装 751周安装 31GitHub Stars 3下载 246核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:deck-creator(套牌创造者)
来源仓库:https://github.com/b-open-io/gemskills
仓库路径:skills/deck-creator
安装命令:
npx skills add https://github.com/b-open-io/gemskills --skill deck-creator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/b-open-io/gemskills --skill deck-creator

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

创建专业演示文稿,融合 AI 生成图像与统一视觉风格。可选 HTML 互动版式与视频背景增强现场展示效果。输入可为文档摘要或需求描述,自动拆分为逻辑幻灯片序列。输出包含 PNG/JPG 或可部署的静态 HTML 播放器两种形式。deck-creator 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/deck-creator

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/b-open-io/gemskills --skill deck-creator;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

deck-creator 怎么安装?

在终端执行 npx skills add https://github.com/b-open-io/gemskills --skill deck-creator。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

deck-creator 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

deck-creator 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/b-open-io/gemskills --skill deck-creator 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

deck-creator 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

deck-creator 用的人多吗?

公开数据是累计安装 751 次,近一周安装 31 次,下载 246 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

deck-creator 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
deck-creator

套牌创造者 · 本页

7513执行命令未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Deck Creator

Create professional presentation decks with consistent visual style, compelling copy, AI-generated slide images, and optional interactive HTML presenter with video backgrounds.

When to Use

  • Create a presentation or slide deck
  • Build a pitch deck, proposal, or sales presentation
  • Design slides for a product launch, company overview, or partnership
  • Generate a complete deck from a document, requirements, or brief
  • Restyle an existing deck with a different art style
  • Build an interactive HTML presenter for live presentations
  • Add ambient video backgrounds to a deck
  • Use the "deck playground", "visual deck editor", or "deck builder UI"

Interactive Playground

For a visual UI to design and generate decks interactively:

bun run --cwd ${CLAUDE_PLUGIN_ROOT} ${CLAUDE_PLUGIN_ROOT}/skills/deck-creator/scripts/playground_server.ts --dir <deck-dir>

The playground provides style browsing, per-slide editing, live preview, and one-click generation. Supports both Gemini PNG and text-layered HTML modes.

IMPORTANT: Invoke this skill via the Skill tool (Skill("deck-creator")). Do not manually execute phases without loading this skill first. Follow the workflow step by step; do not skip phases.

Fast-Path Defaults (Minimize Friction)

Prefer speed over exhaustive questioning. Ask only what is necessary, infer the rest, and get the user into the UI quickly.

Ask one compact question set first:

  1. Goal/topic of the deck
  2. Audience
  3. Approx slide count
  4. Output mode (pdf, html+pdf, or web/publish)

Infer defaults when missing:

  • Slide count: 10
  • Mode: html+pdf for live/web use, otherwise pdf
  • Theme: modern high-contrast business style
  • Video background: none
  • Art style: none unless requested

After creating THEME.md + DECK-PLAN.md, launch the playground immediately with the target deck dir preloaded:

bun run --cwd ${CLAUDE_PLUGIN_ROOT} ${CLAUDE_PLUGIN_ROOT}/skills/deck-creator/scripts/playground_server.ts --dir <deck-dir>

Then ask exactly one fork-in-the-road question:

  • Option A (recommended): "Generate slides in parallel now while you watch in Deck Creator?"
  • Option B: "Open Deck Creator first and wait before generating?"

Do not auto-generate slides without explicit user confirmation (cost-sensitive), but offer a one-click quick start to generate slide 1 first.

Process Overview

Six phases, executed in order:

  1. Discovery - Gather context, examples, and references
  2. Launch - Bootstrap files and open Deck Creator UI with the deck preloaded
  3. Theme - Establish visual style, color palette, and optional art style
  4. Copy - Plan and write slide content using marketing principles
  5. Generation - Create all slides in parallel with consistent style + stitch PDF
  6. Present/Publish - Build interactive HTML presenter and publish/share link (optional)

Phase 1: Discovery

Gather only the minimum information needed before opening the UI.

Ask in tiers:

Tier 1 (Always): Audience, Purpose, Content sources/materials, Slide count (recommend 10-16)

Tier 2 (Context): Presentation setting, Brand guidelines, Style references, Existing assets

Tier 3 (If live/conference/webinar): PDF only or HTML presenter too? Video backgrounds? Browse styles visually or auto-suggest?

If example decks or references are provided, analyze visual style, layout patterns, typography, and messaging patterns.

Phase 2: Launch (Default Early Step)

  1. Create or confirm <deck-dir>
  2. Bootstrap THEME.md and DECK-PLAN.md with best-guess defaults
  3. Launch Deck Creator with --dir <deck-dir> so the user lands in the deck immediately
  4. Ask the Option A/Option B generation fork question

This is the normal flow. Do not delay UI launch until every detail is finalized.

Phase 3: Theme Selection

Establish a consistent visual system before generating slides.

Option A: Theme Factory (recommended) - Install and invoke theme-factory skill for a cohesive palette.

Option B: Manual - Define Background, Primary, Secondary, Text, and Accent colors from brand guidelines.

Style Parameters

Aspect Ratio: 16:9 (--size 2K produces 1376x768)
Art Style: (optional) Any style ID from browsing-styles skill (e.g., pixl, cybr, deco)
Typography: Headlines Bold 48-64px, Body 18-24px, Stats Extra Bold 72-96px
Layout: Card-based with generous whitespace

Apply a consistent art style across all slides using --style <id>. Browse 169 styles with the browsing-styles skill. When a style is specified, add --style <id> to every generation command.

If the user wants an HTML presenter, add a Presenter Settings block to THEME.md:

## Presenter Settings
Format: html+pdf
Video Background: none | url(<url>) | veo-global | veo-per-slide
Transition: 500ms
Auto-Advance: false

Document the complete theme in THEME.md.

Phase 4: Copy & Content Planning

Apply copywriting principles: one message per slide, headlines tell the story, show don't tell, problem-solution-proof structure, concrete over abstract, end with action.

Create a DECK-PLAN.md with deck overview and per-slide plan (headline, content points, visual concept, key message). Continue gathering content until 10-16 slides are fully planned. Do not proceed to generation until the content plan is complete.

Consult references/copywriting.md for headline formulas, persuasion patterns, and audience-specific framing. Consult references/slide-types.md for detailed templates per slide type.

Phase 5: Slide Generation

Pre-Generation Checklist

  • Theme defined (colors, typography, style)
  • All slides planned (10-16 slides)
  • Each slide has: headline, content, visual concept
  • Output directory created

Generate Slides

Launch all slide generation agents simultaneously. Spawn one gemskills:content-specialist agent per slide via the Task tool. Include theme spec, slide prompt, output path, and the generate-image command:

bun run --cwd ${CLAUDE_PLUGIN_ROOT} ${CLAUDE_PLUGIN_ROOT}/skills/generate-image/scripts/generate.ts "prompt" --aspect 16:9 --size 2K [--style <id>] --output <path>

Limit to 12 parallel generations. For 14+ slides, generate in two batches.

Post-Generation

Verify all slides exist, stitch into PDF, verify PDF, create DECK-INDEX.md, provide summary. Consult references/generation.md for detailed prompt templates, PDF stitching methods, and post-generation steps.

Do not read generated slide images back into context. Ask the user to visually inspect.

Phase 6: Present/Publish (Optional)

If the user requested an HTML presenter (or THEME.md specifies Format: html+pdf):

bun run --cwd ${CLAUDE_PLUGIN_ROOT} ${CLAUDE_PLUGIN_ROOT}/skills/deck-creator/scripts/build_presenter.ts --dir <deck-dir> [--open]

For video backgrounds, either pass --video <url> with a user-provided URL, or generate an ambient loop via Veo 3.1 first. Consult references/presenter.md for full CLI options, video modes, keyboard shortcuts, and verification checklist.

If the user asked for web/share/publish, guide them to Deck > Publish & Share... in the playground and complete one publish route (Vercel, Zip, or Cloudflare Tunnel). Treat "publish link delivered" as the finish line for web mode.

Output Structure

project/deck/
├── THEME.md              # Visual style definition
├── DECK-PLAN.md          # Content planning document
├── DECK-INDEX.md         # Final deck inventory
├── deck.pdf              # Stitched presentation PDF
├── presenter.html        # Interactive HTML presenter (optional)
├── ambient.mp4           # AI-generated video background (optional)
├── PRESENTER-CONFIG.json # Per-slide video config (optional)
└── slides/
    ├── 01-title.png
    └── ...

Best Practices

  1. Uniform Style - Every slide uses the same theme parameters
  2. Consistent Terminology - Same words for concepts throughout
  3. Visual Hierarchy - Headlines largest, supporting text smaller
  4. Generous Whitespace - Avoid overcrowding slides
  5. Center-Weight Important Elements - Account for cropping
  6. High Contrast - Ensure readability on projectors
  7. No Orphan Slides - Every slide connects to the narrative

Reference Files

  • references/slide-types.md - Expanded templates for each slide type
  • references/copywriting.md - Marketing copy principles and headline formulas
  • references/generation.md - Prompt templates, parallel generation, PDF stitching
  • references/presenter.md - HTML presenter build, video modes, keyboard shortcuts
  • assets/videos/ - Bundled ambient video backgrounds (seeded to ~/.gemskills on first use)

平台分布

Codex

36.41%
按下载量换算90

Claude

28.35%
按下载量换算70

Cursor

19.14%
按下载量换算47

Gemini CLI

9.28%
按下载量换算23

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/b-open-io/gemskills --skill deck-creator 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills