feat: improve create-lab-guide skill score 69% → 90%#25011
Merged
dvdksn merged 1 commit intoMay 12, 2026
Conversation
Hey @dvdksn 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `create-lab-guide`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | create-lab-guide | 69% | 90% | +21% | | check-pr | 99% | — | — | | fix-issue | 99% | — | — | | research | 97% | — | — | | triage-issue | 96% | — | — | | write | 93% | — | — | | agent-readiness-audit | 93% | — | — | | testcontainers-guides-migrator | 90% | — | — | | create-pr | 90% | — | — | | review-changes | 86% | — | — | | migrate-content-ia | 79% | — | — | ## Description Improves the `create-lab-guide` skill's description and content structure. The skill had the lowest baseline score (69%) across the repo's 11 skills, with the most room to grow — so it made sense to focus here. <details> <summary>Changes made</summary> - **Rewrote frontmatter description** with explicit "Use when..." clause and five natural trigger terms (`create a lab guide`, `write a Labspace page`, `add a Docker lab tutorial`, `migrate a lab to docs`, `document a hands-on lab`) - **Fixed duplicate "Step 2" heading** — renumbered to a proper 5-step sequence (Clone → Extract → Write → Style → Validate) - **Added validation step (Step 5)** with explicit gate: frontmatter field checks, prettier formatting, lint/vale pass, and manual review before commit - **Compressed style rules** from a verbose bullet list into a scannable two-column table - **Replaced prose file listing** with a structured table mapping files to their purpose - **Preserved all Labspace domain expertise**: `labspace.yaml`, `labspace-launch` shortcode, `dockersamples` org conventions, `model-download` parameter, `compose.override.yaml` model detection </details> I also stress-tested your `triage-issue` skill against a few real-world task evals and it held up really well on issue verdict decision trees with cross-referenced timeline checks. Kudos for that. 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 — [@yogesh-tessl](https://github.com/yogesh-tessl) — if you hit any snags. ## Related issues or tickets N/A — proactive improvement based on skill evaluation. ## Reviews - [ ] Technical review - [ ] Editorial review Thanks in advance 🙏
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Thanks @yogesh-tessl cc @mikesir87 / @ajeetraina - wanna have a squizz here? |
Contributor
Author
|
@dvdksn, the way you've split concerns across 11 skills here, especially keeping triage-issue and write as separate decision trees rather than one monolith, made the review straightforward since each skill had a clean boundary to evaluate. Great to see this resonates. I’ve reviewed a bunch of skills now and have picked up a few useful patterns around keeping them maintainable and secure as usage grows. Happy to swap notes over a quick 15-min coffee and share the latest practices we've seen. also eager to hear how you’re thinking about use cases on your side, as it helps us refine the approach. |
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
2 participants
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.
Hey @dvdksn 👋
ran your skills through
tessl skill reviewat work and found some targeted improvements forcreate-lab-guide. Here's the full before/after:improves the
create-lab-guideskill's description and content structure. The skill had the lowest baseline score (69%) across the repo's 11 skills, with the most room to grow, so it made sense to focus here.Changes made
create a lab guide,write a Labspace page,add a Docker lab tutorial,migrate a lab to docs,document a hands-on lab)labspace.yaml,labspace-launchshortcode,dockersamplesorg conventions,model-downloadparameter,compose.override.yamlmodel detectionI also stress-tested your
writeskill against a few real-world task evals and it held up really well on issue verdict decision trees with cross-referenced timeline checks. Kudos for that.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.
If you want to self-improve your skills, or define your own scenarios to pressure test, just ask your agent (Claude Code, Codex, etc.) to evaluate and optimize your skill with Tessl. Ping me @yogesh-tessl, if you hit any snags.