Improve/skill review optimization#126
Open
yogesh-tessl wants to merge 2 commits intodev-five-git:mainfrom
Open
Improve/skill review optimization#126yogesh-tessl wants to merge 2 commits intodev-five-git:mainfrom
yogesh-tessl wants to merge 2 commits intodev-five-git:mainfrom
Conversation
Hey @owjs3901 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after:  | Skill | Before | After | Change | |-------|--------|-------|--------| | vespera | 61% | 87% | +26% | <details> <summary>Changes made</summary> **Description (40% → 100%)** - Expanded frontmatter description with concrete actions (define route handlers, derive schemas, auto-generate OpenAPI docs) - Added explicit "Use when..." clause for skill selection - Added broader trigger terms (REST API, HTTP endpoints, Swagger, ReDoc, SeaORM, multipart) **Content (65% → 70%)** - Added end-to-end workflow section (model → schema_type → handler → annotate → build → validate) - Added validation checkpoint after Quick Start using `swagger-cli validate` - Removed redundant "Same-File Model Reference" section (already covered in parameters table and Quick Reference) - Removed redundant "Complete Example" section (patterns already demonstrated in Quick Start and Basic Syntax) - Removed "Why Not Manual Structs?" section and DO/DON'T table (overlaps with Quick Reference examples) - Consolidated three parameter tables into one unified table with Priority column </details> 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. Thanks in advance 🙏
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
1 participant
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 @owjs3901 👋
Zero-config OpenAPI 3.1 generation for Axum with compile-time schema extraction, that vespera!() one-liner macro is the kind of DX that makes Rust feel like FastAPI. The file-based route discovery is a clean ergonomic win. Wanted to suggest a few improvements to the SKILL.md.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
Description (40% → 100%)
Content (65% → 70%)
swagger-cli validateHonest 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 - @yogesh-tessl - if you hit any snags.
Thanks in advance 🙏