Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计提醒

slide-generation幻灯片生成

Agent Skill

slide-generation 用于整理文档、README、Markdown 和说明材料,适合在 OpenClaw 中需要把零散信息整理成结构清晰的文档时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,224

周安装

50

GitHub Stars

公开资料未说明

下载量

396
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:slide-generation(幻灯片生成)
来源仓库:https://github.com/hh23333/slide-generation
安装命令:
openclaw skills install slide-generation
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install slide-generation

简介

专为教师设计的 Marp 幻灯片生成器,支持教学材料自动化排版。

  • 适合从 .md 文件或文件夹自动生成兼容 Marp 的课件。
  • 可处理章节划分、图表嵌入与教学逻辑结构组织。slide-generation 属于效率类 Skill,可作为该场景下的辅助能力补充。
  • 需确保输入内容符合 Marp 语法,避免格式错误。
  • 建议先在小样例中验证输出效果,再用于正式教学。

SKILL.md

name
slide-generation
description
>-

Slide Generation Skill

Generate Marp slides from source content following the AM Blue Course theme and workflow rules.

Quick Start

  1. Identify sources: Read all source .md files (or all .md files in a folder)
  2. Read references: Load references/rules.md and references/marp-guide.md before generating
  3. Design structure: Plan slide sections from source content
  4. Generate: Output .md file with Marp format

Input Modes

Single File

User: 生成关于"记忆与检索"的幻灯片,基于第八章.md
→ Read 第八章.md, generate slides

Multiple Files / Folder

User: 把这个文件夹里的内容整合成一组教学幻灯片
→ Read all .md files in the folder, merge by topic/chapter, generate unified slides

When multiple sources are provided:

  • Merge content by topic or chapter sequence
  • Avoid duplicate content across sources
  • If sources conflict, prefer the more recent or comprehensive one

Output Target

When user specifies an output path (e.g. chapter8/memory-slide.md):

  1. Create the output folder (e.g. chapter8/)
  2. Copy all used images to chapter8/images/
  3. Write the slide markdown to chapter8/memory-slide.md

Image path mapping:

  • Source path: ../images/xxx.png → Output path: ./images/xxx.png
  • Copy source images to the output images/ folder alongside the slide file

Marp YAML Header (Required)

Always use this exact header:

---
marp: true
size: 16:9
theme: am_blue_course
paginate: true
headingDivider: [2,3]
footer: '*敬业乐群*'
---

Required Slide Structure

1. Cover Page (First Slide)

<!-- _class: cover_c -->
<!-- _paginate: "" -->
<!-- _footer: 敬业乐群 -->
<!-- _header: ![](images/logo.png) -->

###### [Subtitle]

# [Main Title]

@PresenterName
<Email>

Subtitle format: use ###### (level 6 heading) Main title: use # (level 1 heading)

2. Table of Contents (Second Slide)

## 本节内容

<!-- _class: toc_a -->
<!-- _header: "CONTENTS" -->
<!-- _footer: 敬业乐群 -->
<!-- _paginate: "" -->

- [Topic 1](#3)
- [Topic 2](#N)
- ...

3. Content Slides

Use ## (level 2 heading) for main section titles. The headingDivider: [2,3] setting automatically splits pages at ## and ### headings.

For content-heavy pages, apply text-size classes:

  • <!-- _class: smalltext --> — 0.9x font size
  • <!-- _class: tinytext --> — 0.8x font size

For narrow/wide images, avoid left-right layouts; use full-width instead.

Core Rules

Must Follow

  • ✅ Content must come ONLY from source files — do not add external knowledge
  • ✅ Keep content rich but within source bounds
  • ✅ Preserve original images from source; copy to output images/ folder
  • ✅ Use logo.png as header image (path: images/logo.png in output)
  • ✅ Presenter name and email as specified by user
  • ✅ Use <!-- *class: smalltext* --> or <!-- *class: tinytext* --> for dense content
  • ✅ Inline math: wrap in $...$ (e.g. $f(x) = y$)
  • ✅ Convert code to pseudocode if it aids comprehension
  • ✅ Section numbering: use 2.2 not 10.2.2; omit chapter prefix

Must NOT

  • ❌ Use classes not defined in theme files
  • ❌ Use transition slides (<!-- _class: trans -->)
  • ❌ Use --- for manual page breaks (headingDivider already handles this)
  • ❌ Title encoding like 10.2.2 — use 2.2 instead
  • ❌ Generate images — only use images from source content

Layout Decision Rules

Based on image/table shape:

Content ShapeRecommended Layout
Wide image (aspect < 1:1)Full-width, no columns
Tall image (aspect > 1:1)Left-right columns possible
Square imageFlexible, consider columns
TablesFull-width or right-aligned; avoid narrow columns
Code blocksFull-width, consider tinytext
Mixed text + imageUse cols-2 (五五分) or cols-2-64 (六四分)

Image scaling: use ![#c w:700](path) or ![#c h:300](path) to adjust size dynamically.

Column Layout Examples

Two columns (五五分):

<!-- _class: cols-2 -->
<div class=ldiv>

Left column content
</div>

<div class=rdiv>

Right column content
</div>

Two columns (六四分, image on left):

<!-- _class: cols-2-64 -->
<div class=limg>

![#c](image.png)
</div>

<div class=rdiv>

Right column text
</div>

fig-top layout (image on top):

<!-- _class: fig-top -->
<div class=fig-container>

![width:850px](image.png)
</div>

<div class=text-container>

Content text
</div>

Available Classes

Reference: assets/example_file/AwesomeMarp_blue.md and assets/example_file/slide.md

Page layout: cols-2, cols-2-64, cols-2-73, cols-2-46, cols-2-37, cols-3, rows-2, pin-3

Text size: tinytext, smalltext, largetext, hugetext

Special: toc_a, cover_c, fig-top, fglass, caption, fixedtitleA, fixedtitleB

Callouts: bq-purple, bq-blue, bq-green, bq-red, bq-black

Image Handling

  1. Scan source for ![]() image syntax
  2. Copy each image file to output images/ folder
  3. In slide markdown, reference images relative to output location: ![](images/filename.png)
  4. Map original paths (e.g. ../images/8-figures/8-1.png) to new paths (images/8-1.png)

For logos and theme images, use: images/logo.png (copied from assets/images/logo.png)

Multi-Source Synthesis

When synthesizing from multiple sources:

  1. Read all sources first — get full picture of content
  2. Identify overlap — note repeated topics across files
  3. Deduplicate — consolidate overlapping content
  4. Merge by structure:

- If sources are chapters of the same book → follow chapter order - If sources are different perspectives → create unified section structure - If sources have conflicting info → prefer user's stated preference or most recent

  1. Generate one coherent slide deck — unified structure, consistent style

Quality Checklist

Before finishing, verify:

  • [ ] YAML header matches required format exactly
  • [ ] Cover page has all: main title, subtitle, presenter name, email, logo, footer, no page number
  • [ ] TOC page links to correct slide numbers
  • [ ] All images from source are included and copied to images/ folder
  • [ ] No Marp classes used beyond what's in theme files
  • [ ] No --- page breaks (headingDivider handles it)
  • [ ] Inline math uses $...$ syntax
  • [ ] No title encodings like 10.2.2 — use 2.2
  • [ ] Content stays within source material bounds
  • [ ] Logo path is images/logo.png

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

OpenClaw

97.38%
按下载量换算386

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

来源信息

继续浏览同类 Skills