Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计提醒

create-marp-deck创建马尔普甲板

Agent Skill

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

总安装

4,004

周安装

172

GitHub Stars

8

下载量

1,404
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:create-marp-deck(创建马尔普甲板)
来源仓库:https://github.com/omerr/claude-skills
仓库路径:skills/create-marp-deck
安装命令:
npx skills add https://github.com/omerr/claude-skills --skill create-marp-deck
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/omerr/claude-skills --skill create-marp-deck

简介

用于查找、检索和筛选相关信息,适合根据关键词或任务场景快速定位候选结果。

  • 适用于 Codex、Claude、Cursor、Gemini CLI 等宿主环境,支持 Marp Markdown 演示文稿生成。
  • 通过命令行安装,需结合来源仓库文档核验具体用法,确保幻灯片结构清晰且符合受众。
  • 安装前建议确认权限范围,避免触发未授权的联网或文件操作。
  • create-marp-deck 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

Create Marp Slide Deck

Create a presentation slide deck using the Marp markdown format, following the established conventions below.

Phase 1: Interview

Before generating anything, interview the user by asking these questions one at a time, waiting for each answer before proceeding to the next.

Question 1 — Goal & Topic: Ask: "What's this presentation about? What should the audience walk away knowing or being able to do?"

Question 2 — Audience: Ask: "Who's the audience? (e.g., engineering team, executives, external clients, conference attendees)"

Question 3 — Key Points: Ask: "What are the key points or sections you want to cover? List the main ideas, even if rough."

  • If the user provides files, URLs, or references, read/fetch them thoroughly before continuing.

Question 4 — Data & Demos: Ask: "Any specific data, code examples, diagrams, or demos to include? Do you have these ready, or should I create them?"

Question 5 — Constraints: Ask: "Any constraints? Think: target number of slides, time limit for the talk, things to avoid, or specific branding requirements."

After collecting all answers, briefly summarize what you understood and ask for confirmation before proceeding.

Phase 2: Generate the Deck

Follow the structure and conventions below exactly.


FRONTMATTER

Every deck starts with this exact frontmatter:

---
marp: true
theme: default
paginate: true
size: 16:9
---

CSS STYLE BLOCK

Immediately after the frontmatter, include a <style> block with:

  1. Base font sizes for section, table, blockquote, pre
  2. Header styles for breadcrumb navigation (gray text, blue for active section)
  3. Section classes for the title slide and each part/section divider - these get gradient backgrounds and white text

Color palette for section dividers (pick 2-4 based on number of parts):

  • Blue: linear-gradient(135deg, #1e3a5f 0%, #2d5a8e 100%)
  • Green: linear-gradient(135deg, #064e3b 0%, #047857 100%)
  • Amber: linear-gradient(135deg, #7a4a1a 0%, #a66b2e 100%)
  • Purple: linear-gradient(135deg, #3d1e5c 0%, #5a2d8e 100%)
  • Title slide (always dark navy): linear-gradient(135deg, #0f172a 0%, #1e293b 50%, #0f172a 100%)

Template:

<style>
section {
  font-size: 22px;
}
table {
  font-size: 18px;
}
blockquote {
  font-size: 22px;
}
pre {
  font-size: 16px;
}
header {
  font-size: 14px;
  color: #999;
}
header strong {
  color: #2563eb;
}
section.title-slide {
  background: linear-gradient(135deg, #0f172a 0%, #1e293b 50%, #0f172a 100%);
}
section.part-FIRST,
section.part-SECOND,
section.part-THIRD,
section.title-slide {
  --h1-color: #fff;
  --heading-strong-color: #fff;
  --fgColor-default: rgba(255, 255, 255, 0.95);
  --fgColor-muted: rgba(255, 255, 255, 0.7);
  color: white;
}
section.part-FIRST {
  background: linear-gradient(135deg, #1e3a5f 0%, #2d5a8e 100%);
}
section.part-SECOND {
  background: linear-gradient(135deg, #064e3b 0%, #047857 100%);
}
section.part-THIRD {
  background: linear-gradient(135deg, #3d1e5c 0%, #5a2d8e 100%);
}
</style>

Replace FIRST, SECOND, THIRD with short descriptive names for each part (e.g., part-context, part-results, part-summary).


SLIDE STRUCTURE

The deck follows this exact order:

1. Title Slide

<!-- _class: lead title-slide -->

# Main Title
## Subtitle

**Key detail 1**: value
**Key detail 2**: value
**Date**: Month Year

2. Questions / Goals slide

List 3-5 questions the deck will answer, as a numbered list with bold lead-ins.

3. Agenda slide

<!-- _class: lead title-slide -->

# Agenda

### Part 1: Name
Short description

### Part 2: Name
Short description

### Part 3: Name
Short description

4. For each part: section divider + content slides

Section divider (full-bleed colored background):

<!-- _header: "" -->
<!-- _class: lead part-NAME -->

# Part N: Section title

**One-line description**

Content slides (with breadcrumb header):

<!-- header: "**Active section** > Other section > Other section" -->

# Slide title

Content here

The breadcrumb shows where you are in the deck. The active section is wrapped in **bold**. The header directive persists until changed, so you only need to set it once per section (on the first content slide after the divider). Reset it with <!-- _header: "" --> before each section divider.

5. Final Slides

End with summary/takeaway slides, still within the last section.


FORMATTING RULES

  1. Sentence case for all headings — only capitalize the first letter and proper nouns (e.g., "Get started in 5 minutes", not "Get Started in 5 Minutes"). Breadcrumb headers follow the same rule
  2. No trailing periods on bullets, text lines, or table cells
  3. Single dash (-) for parenthetical separators, not double dash (--)
  4. Backticks for program names, file names, and technical identifiers (not bold)
  5. Bold for emphasis on key phrases and findings
  6. Tables for data comparisons - keep them concise
  7. Blockquotes (>) for key callouts or distinctions
  8. One idea per slide - if a slide is getting dense, split it into two
  9. Keep bullet lists to 3-5 items max per slide
  10. No parenthetical notes in the slide body unless absolutely necessary

EXPORTING

After writing the deck, export to both HTML and PPTX:

npx @marp-team/marp-cli@latest --no-stdin FILENAME.md -o FILENAME.html
npx @marp-team/marp-cli@latest --no-stdin --pptx FILENAME.md -o FILENAME.pptx

Always use --no-stdin to prevent marp from hanging on stdin.


EDITABLE PPTX EXPORT (OPTIONAL)

If the user asks for editable PPTX (text that can be edited in PowerPoint or Google Slides), run these additional steps. This requires LibreOffice and python-pptx to be installed.

# PPTX - editable text (experimental, requires LibreOffice)
npx @marp-team/marp-cli@latest --no-stdin --pptx --pptx-editable --allow-local-files FILENAME.md -o FILENAME-editable.pptx
python3 -c "
from pptx import Presentation
from pptx.util import Emu
prs = Presentation('FILENAME-editable.pptx')
margin = Emu(747720)
for slide in prs.slides:
    for shape in slide.shapes:
        if shape.has_text_frame and shape.shape_type == 17:
            tf = shape.text_frame
            if not tf.text.strip() or tf.text.strip().isdigit():
                continue
            font_size = None
            if tf.paragraphs and tf.paragraphs[0].runs:
                font_size = tf.paragraphs[0].runs[0].font.size
            if not font_size:
                continue
            new_width = prs.slide_width - margin - shape.left
            if new_width > shape.width:
                shape.width = new_width
            min_height = int(font_size * 1.4) * 2
            if shape.height < min_height:
                shape.height = min_height
            tf.word_wrap = True
prs.save('FILENAME-editable.pptx')
"

Notes:

  • --allow-local-files needed for local images
  • --pptx-editable requires LibreOffice installed
  • The python-pptx post-processing fixes text box sizing issues from LibreOffice conversion
  • Always use --no-stdin to prevent marp from hanging on stdin

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

33.88%
按下载量换算476

Claude

33.51%
按下载量换算470

Cursor

17.88%
按下载量换算251

Gemini CLI

8.91%
按下载量换算125

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills