Improve/skill review optimization#1
Open
yogesh-tessl wants to merge 2 commits intointerf-labs:mainfrom
Open
Conversation
Hey @gedossman 👋 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 | |-------|--------|-------|--------| | enterprise-readiness-protocol | 45% | 76% | +31% | | interf-draft | 79% | 88% | +9% | | interf-preview | 74% | 88% | +14% | **enterprise-readiness-protocol** (+31%) - Rewrote description with concrete actions (defines schema, validation rules, field specs) instead of abstract "open standard" language - Added inline YAML example so the contract format is immediately visible without reading spec.md - Added `npx interf validate` command to the Draft step for actionability - Made workflow steps more concrete (Draft step now mentions validation) **interf-draft** (+9%) - Expanded description with specific dependency types scanned (API endpoints, auth providers, infrastructure, stakeholders) and natural trigger terms (rollout prerequisites, pre-launch checklists) - Tightened Step 1 from rhetorical questions to a focused scan checklist - Made validation step non-optional with a fix-and-rerun feedback loop - Changed heading from "Declare" to "Draft" to match the skill name **interf-preview** (+14%) - Added natural trigger terms to description (deployment plan, implementation preview, go-to-market readiness assessment) - Added input verification step in "Before You Start" (contract has requirements, canonical IDs resolve) - Added validation checkpoint after building enterprise profile - Added example dependency chain to make Step 3 concrete - Added structured output table format in Step 4 for consistent deliverables **All skills** - Converted description frontmatter from block scalar (>) to quoted string format 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
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 @gedossman 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:enterprise-readiness-protocol (+31%)
npx interf validatecommand to the Draft step for actionabilityinterf-draft (+9%)
interf-preview (+14%)
All skills
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.
I also added a lightweight GitHub Action that auto-reviews any skill.md changed in a PR (includes min permissions, uses a pinned action version, only posts a review comment).
This means that it gives you and your contributors an instant quality signal before you have to review yourself (no signup, no tokens needed).
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 🙏