Skip to content

feat: improve slidev skill#2479

Merged
antfu merged 1 commit into
slidevjs:mainfrom
popey:improve/skill-review-optimization
Mar 11, 2026
Merged

feat: improve slidev skill#2479
antfu merged 1 commit into
slidevjs:mainfrom
popey:improve/skill-review-optimization

Conversation

@popey

@popey popey commented Mar 11, 2026

Copy link
Copy Markdown
Contributor

Hullo @antfu 👋

I ran your skills through tessl skill review at work and found some targeted improvements. Here's the before/after:

Skill Before After Change
slidev 86% 100% +14%
Changes made
  • Expanded description trigger terms — added "slidedecks", "Slidev", "code walkthroughs", and "developer decks" to improve discoverability when agents match user intent
  • Added verification steps to Quick Start — confirms dev server loads and export output exists, addressing workflow clarity
  • Added pnpm run build command to Quick Start for completeness (was missing the static SPA build step)
  • Added export prerequisite noteplaywright-chromium dependency callout with error recovery guidance for PDF/PPTX/PNG export
  • Added "Code walkthroughs" use case to When to Use section

A note on generation

I noticed these skills are generated from /docs via the process documented in skills/GENERATION.md. That means these direct SKILL.md edits will be overwritten on the next regeneration. I've applied the changes here so you can see the concrete improvements, but you may want to fold similar tweaks into your generation pipeline instead — specifically:

  • Have the generator include the tool name ("Slidev") and natural synonyms ("slidedecks", "decks", "code walkthroughs") in the description to boost agent discoverability
  • Add a verification step after Quick Start commands
  • Include the pnpm run build step alongside dev/export
  • Mention the playwright-chromium prerequisite for export

That way the improvements survive future regenerations.

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at this Tessl guide and ask it to optimize your skill. Ping me - @popey - if you hit any snags.

Thanks in advance 🙏

Hullo @antfu 👋

I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the before/after:

| Skill | Before | After | Change |
|-------|--------|-------|--------|
| slidev | 86% | 100% | +14% |

<details>
<summary>Changes made</summary>

- **Expanded description trigger terms** — added "slidedecks", "Slidev", "code walkthroughs", and "developer decks" to improve discoverability when agents match user intent
- **Added verification steps** to Quick Start — confirms dev server loads and export output exists, addressing workflow clarity
- **Added `pnpm run build` command** to Quick Start for completeness (was missing the static SPA build step)
- **Added export prerequisite note** — `playwright-chromium` dependency callout with error recovery guidance for PDF/PPTX/PNG export
- **Added "Code walkthroughs" use case** to When to Use section

</details>

### A note on generation

I noticed these skills are generated from `/docs` via the process documented in `skills/GENERATION.md`. That means these direct SKILL.md edits will be overwritten on the next regeneration. I've applied the changes here so you can see the concrete improvements, but you may want to fold similar tweaks into your generation pipeline instead — specifically:

- Have the generator include the tool name ("Slidev") and natural synonyms ("slidedecks", "decks", "code walkthroughs") in the description to boost agent discoverability
- Add a verification step after Quick Start commands
- Include the `pnpm run build` step alongside dev/export
- Mention the `playwright-chromium` prerequisite for export

That way the improvements survive future regenerations.

Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute.

Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@popey](https://github.com/popey) - if you hit any snags.

Thanks in advance 🙏
@netlify

netlify Bot commented Mar 11, 2026

Copy link
Copy Markdown

Deploy Preview for slidev failed.

Name Link
🔨 Latest commit e9d24e7
🔍 Latest deploy log https://app.netlify.com/projects/slidev/deploys/69b1e4bd6484c000081b208e

@antfu antfu changed the title feat: improve slidev skill score (86% -> 100%) feat: improve slidev skill Mar 11, 2026
@antfu
antfu merged commit d76850d into slidevjs:main Mar 11, 2026
0 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants