feat: improve 5 lowest-scoring skill definitions#66
Open
rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
Open
feat: improve 5 lowest-scoring skill definitions#66rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
rohan-tessl wants to merge 1 commit intodatabricks:mainfrom
Conversation
rohan-tessl
requested review from
a team,
camielstee-db,
lennartkats-db and
simonfaltum
as code owners
Collaborator
|
@camielstee-db I think it needs your review |
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 @arsenyinfo 👋
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 databricks-dabs
Added quoted description with explicit "Use when" clause. Added compatibility and metadata.version fields. Removed redundant "When to Use This Skill" body section. Added a concrete quick-start workflow (init, configure, validate, deploy, run) with a minimal databricks.yml example.
What changed in databricks-core
Replaced vague description with concrete action verbs and explicit "Use when" clause listing specific trigger scenarios (CLI commands, authentication setup, workspace configuration, bundle deployment, data exploration).
What changed in databricks-jobs, databricks-pipelines, databricks-lakebase
Moved non-standard
parentfrontmatter key intometadata.parent. Expanded descriptions with concrete actions and "Use when" clauses. Removed verbose inline CLAUDE.md/AGENTS.md templates. Consolidated examples where content was duplicated.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.