feat: improve skill scores for faire#1
Open
rohan-tessl wants to merge 1 commit intojack-michaud:mainfrom
Open
Conversation
Hey @jack-michaud 👋 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 | |-------|--------|-------|--------| | modal | 15% | 85% | +70% | | writing-python-services | 18% | 97% | +79% | | committing | 18% | 89% | +71% | | cmux | 18% | 71% | +53% | | ticket-workflow | 18% | 78% | +60% | This PR is intentionally scoped to 5 skills to keep it reviewable — more skills can be improved in follow-ups or via automated review on future PRs. <details> <summary>Changes summary</summary> ### modal (15% → 85%) - Fixed invalid frontmatter: renamed `describe:` to `description:`, removed unknown keys - Changed name from `Modal` to kebab-case `modal` - Added "Use when" trigger clause to description - Expanded body with structured sections: When to Use, Core Patterns, CLI Reference - Preserved reference to `resources/environments.md` and external docs links ### writing-python-services (18% → 97%) - Changed name from `Writing python services` to kebab-case `writing-python-services` - Expanded description with "Use when" clause covering API clients, logging, database access - Added complete, executable code examples for `@cached_property` and dataclass patterns - Structured content into clear sections: Type Conventions, Constructor Rules, Method Signatures ### committing (18% → 89%) - Changed name from `Committing` to kebab-case `committing` - Expanded description with specific jj commands and "Use when" clause - Added structured sections: Standard Commit Flow, Splitting Commits, Commit Message Format, Troubleshooting - Preserved reference to `resources/jj-stale-remote-push.md` ### cmux (18% → 71%) - Changed name from `cmux Workspace Orchestration` to kebab-case `cmux` - Converted description from YAML chevron format to standard quoted string with "Use when" clause - Preserved all existing body content (core concepts, CLI reference, tips, workflows, resources) ### ticket-workflow (18% → 78%) - Changed name from `Ticket Workflow` to kebab-case `ticket-workflow` - Expanded description with "Use when" clause listing specific trigger scenarios - Preserved all existing body content including phase table, state management, agent topology, and resource references </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 - [@rohan-tessl](https://github.com/rohan-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 @adamrdrew 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements.Here's the full before/after:
This PR is intentionally scoped to 5 skills to keep it reviewable — more skills can be improved in follow-ups or via automated review on future PRs.
Changes summary
complete-card, create-card, describe-cards, list-cards (10% → 87-90%)
name,description,user-invocablefields) — these skills were scoring 10% becausetessl skill reviewvalidation requires frontmatterdescribe-ushabti (41% → 75%)
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 and ask it to optimize your skill. Ping me - @rohan-tessl - if you hit any snags.
Thanks in advance 🙏