feat: improve project-dev skill score (78% → 97%)#37
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @Simon-McIntosh 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `project-dev`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | project-dev | 78% | 97% | +19% | | service-ops | 87% | 87% | — | | plan-execution | 70% | 70% | — | <details> <summary>What changed in <code>project-dev</code></summary> - **Description**: Replaced generic terms ("develop, test, lint, build") with specific tool names (`pytest`, `ruff`, `LinkML`) and added trigger terms (`formatting`, `CI`, `generated models`) — description score jumped from 67% to 100% - **Git workflow**: Added a lint → format → test validation sequence before staging and committing, addressing the missing feedback loop the reviewer flagged — workflow clarity went from 2/3 to 3/3 - **No structural rewrites**: kept the existing content intact, just made the description more discoverable and the git workflow more explicit </details> I also stress-tested your `service-ops` skill against a few real-world task evals and it held up really well on multi-service SLURM orchestration with Neo4j + embedding server startup sequencing. 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. Thanks in advance 🙏
Author
|
hey @Simon-McIntosh, just bumping this in case it got lost in the queue, happy to address any feedback! No pressure if reviews run on a schedule here. |
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 @Simon-McIntosh 👋
truly impressive work. Four skills in .claude/skills/ covering facility access patterns, graph queries, mapping workflows, and schema summaries. The facility access table with SSH aliases and reference shots per site is the kind of practical detail that makes a skill actually useful day to day.
ran your skills through
tessl skill reviewat work and found some targeted improvements forproject-dev. Here's the before/after:What changed in
project-devpytest,ruff,LinkML) and added trigger terms (formatting,CI,generated models) - description score jumped from 67% to 100%also stress-tested your
project-devskill against a few real-world task evals and it held up really well on multi-service SLURM orchestration with Neo4j + embedding server startup sequencing. Kudos for that.quick honest disclosure. I work at https://github.com/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.