feat: improve slidev skill#2479
Merged
Merged
Conversation
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 🙏
❌ Deploy Preview for slidev failed.
|
antfu
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hullo @antfu 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:Changes made
pnpm run buildcommand to Quick Start for completeness (was missing the static SPA build step)playwright-chromiumdependency callout with error recovery guidance for PDF/PPTX/PNG exportA note on generation
I noticed these skills are generated from
/docsvia the process documented inskills/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:pnpm run buildstep alongside dev/exportplaywright-chromiumprerequisite for exportThat 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 🙏