How do I install the Blog Slidev skill?

Run npx skillmds@latest add hu-wentao/blog-slidev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Blog Slidev safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Blog Slidev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Blog Slidev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Blog Slidev?

Hu-Wentao (@hu-wentao) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Blog Slidev by hu-wentao — Agent Skill

Name: Blog Slidev
Author: Hu-Wentao

Blog Slidev

Create, maintain, preview, build, and embed standalone Slidev projects in this Hugo blog repository. Use when adding a presentation under slides/, changing a deck's publishing path, updating the GitHub Pages Slidev build, or linking and embedding a deck from Hugo content.

Hu-Wentao Updated Sep 17, 2026

File contents

Blog Slidev Workflow

Use the globally installed slidev skill for Slidev syntax, layouts, components, animation, and export details. Apply the repository-specific rules below for project structure and publishing.

Repository contract

Store every deck as an independent pnpm project at slides/<slug>/.
Use a lowercase kebab-case slug. Treat it as a permanent public identifier.
Keep each deck's package.json, pnpm-lock.yaml, slides.md, components, layouts, snippets, and public assets inside its own directory.
Do not add deck dependencies to the blog root package.json and do not turn the repository into a pnpm workspace unless the user requests that migration.
Publish a deck at /slides/<slug>/. GitHub Actions writes its static build to public/slides/<slug>/ after Hugo builds the blog.
Never commit generated dist/, node_modules/, or public/ output.

Create a deck

Confirm the requested title and derive a stable kebab-case slug.

Run:

.agents/skills/blog-slidev/scripts/create-deck.sh <slug> "<title>"

Edit slides/<slug>/slides.md using the official slidev skill.
Run pnpm --dir slides/<slug> dev for local authoring.
Run pnpm --dir slides/<slug> exec slidev build --base /slides/<slug>/ before handoff.

The creation script refuses to overwrite an existing directory, copies the bundled template, substitutes the slug/title, and runs pnpm install in the new deck.

Publish and verify

The Pages workflow must keep this order:

Build Hugo into public/.
Discover direct child directories under slides/ that contain package.json.
Run pnpm install --frozen-lockfile in each deck.
Build each deck with pnpm --dir <deck> exec slidev build, base /slides/<slug>/, and output public/slides/<slug>/.
Upload public/ once with actions/upload-pages-artifact.

When changing deployment logic, verify both Hugo output and at least one deck build. Ensure generated HTML references the deck's /slides/<slug>/ base rather than /.

Link or embed in Hugo

Prefer a normal link when full-screen presenting is the main experience:

[打开演示文稿](/slides/<slug>/)

Use the repository shortcode when the deck must appear inside an article:

{{</* slidev slug="<slug>" title="演示文稿标题" */>}}

The shortcode validates the slug before rendering an iframe. Do not replace it with raw HTML or enable Goldmark's global unsafe option.

Change checklist

Preserve unrelated working-tree changes and follow the repository's commit rules.
Update the deck's lockfile whenever dependencies change.
Keep the public slug and build base identical.
Run the skill validator after editing this skill.
Report breaking path changes, compatibility configuration, verification commands, and the final public URL.

---name: blog-slidevdescription: Create, maintain, preview, build, and embed standalone Slidev projects in this Hugo blog repository. Use when adding a presentation under slides/, changing a deck's publishing path, updating the GitHub Pages Slidev build, or linking and embedding a deck from Hugo content.---# Blog Slidev WorkflowUse the globally installed `slidev` skill for Slidev syntax, layouts, components, animation, and export details. Apply the repository-specific rules below for project structure and publishing.## Repository contract- Store every deck as an independent pnpm project at `slides/<slug>/`.- Use a lowercase kebab-case slug. Treat it as a permanent public identifier.- Keep each deck's `package.json`, `pnpm-lock.yaml`, `slides.md`, components, layouts, snippets, and public assets inside its own directory.- Do not add deck dependencies to the blog root `package.json` and do not turn the repository into a pnpm workspace unless the user requests that migration.- Publish a deck at `/slides/<slug>/`. GitHub Actions writes its static build to `public/slides/<slug>/` after Hugo builds the blog.- Never commit generated `dist/`, `node_modules/`, or `public/` output.## Create a deck1. Confirm the requested title and derive a stable kebab-case slug.2. Run: ```bash .agents/skills/blog-slidev/scripts/create-deck.sh <slug> "<title>" ```3. Edit `slides/<slug>/slides.md` using the official `slidev` skill.4. Run `pnpm --dir slides/<slug> dev` for local authoring.5. Run `pnpm --dir slides/<slug> exec slidev build --base /slides/<slug>/` before handoff.The creation script refuses to overwrite an existing directory, copies the bundled template, substitutes the slug/title, and runs `pnpm install` in the new deck.## Publish and verifyThe Pages workflow must keep this order:1. Build Hugo into `public/`.2. Discover direct child directories under `slides/` that contain `package.json`.3. Run `pnpm install --frozen-lockfile` in each deck.4. Build each deck with `pnpm --dir <deck> exec slidev build`, base `/slides/<slug>/`, and output `public/slides/<slug>/`.5. Upload `public/` once with `actions/upload-pages-artifact`.When changing deployment logic, verify both Hugo output and at least one deck build. Ensure generated HTML references the deck's `/slides/<slug>/` base rather than `/`.## Link or embed in HugoPrefer a normal link when full-screen presenting is the main experience:```md[打开演示文稿](/slides/<slug>/)```Use the repository shortcode when the deck must appear inside an article:```md{{</* slidev slug="<slug>" title="演示文稿标题" */>}}```The shortcode validates the slug before rendering an iframe. Do not replace it with raw HTML or enable Goldmark's global `unsafe` option.## Change checklist- Preserve unrelated working-tree changes and follow the repository's commit rules.- Update the deck's lockfile whenever dependencies change.- Keep the public slug and build base identical.- Run the skill validator after editing this skill.- Report breaking path changes, compatibility configuration, verification commands, and the final public URL.

Frequently asked questions