feat: improve 5 lowest-scoring skill definitions#86
Open
rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
Open
feat: improve 5 lowest-scoring skill definitions#86rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
Conversation
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 @philip 👋
I ran your skills through
tessl skill reviewat work and found targeted improvements in your skills. Here's the before/after:These were easy changes to bring the skill's structure and activation in line with what performs well against Anthropic's best practices.
What changed in vercel-cli and vercel-composition-patterns
Added quoted descriptions with "Use when" clauses listing specific triggers. Added concrete workflows with validation checkpoints. For composition-patterns, added 3 before/after TSX code examples (boolean props to compound components, explicit variants, React 19 forwardRef removal). Consolidated rule lists into compact priority tables.
What changed in building-components
Quoted the description string. Added a 7-step workflow with explicit validation checkpoint. Added a concrete TSX quick example (Button component with data attributes, ARIA, forwardRef). Added a decision tree for routing to the correct reference file.
What changed in seo-audit
Cut from 451 lines to 93 lines (~80% reduction). Removed all explanations of concepts Claude already knows (E-E-A-T definitions, what title tags are, HTTPS basics). Kept only thresholds (LCP under 2.5s, title 50-60 chars), the schema detection limitation, and actionable checklists.
What changed in databricks-core
Rewrote the description with a leading "Use when" clause listing specific triggers (CLI commands, authentication, workspace configuration, profile management, Unity Catalog, DAB deployment).
In addition, I stress-tested your
databricks-dabsskill against a few real-world scenarios, and it held up really well. This means that your skill meaningfully improves agent steering and contributes to stronger output quality. 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 @rohan-tessl, if you hit any snags.