feat: improve skill scores for claude-code-tauri-skills#2
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @dchuk 👋 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 | |-------|--------|-------|--------| | understanding-tauri-architecture | 39% | 90% | +51% | | configuring-tauri-capabilities | 59% | 90% | +31% | | developing-tauri-plugins | 59% | 90% | +31% | | setting-up-tauri-projects | 79% | 90% | +11% | | testing-tauri-apps | 79% | 86% | +7% | <details> <summary>Changes made</summary> **All 5 skills:** - Added explicit "Use when..." clauses with natural trigger keywords to descriptions - Switched descriptions to quoted string format with concrete action verbs - Added domain-specific trigger terms (e.g. `tauri.conf.json`, `capability.json`, `tauri plugin new`) **tauri-architecture (39% → 90%):** - Removed large ASCII diagrams that consumed tokens without adding value for an LLM - Cut explanations of concepts Claude already knows (what HTML/CSS/JS is, webview benefits) - Added a 5-step numbered workflow with validation checkpoints - Reduced from 424 to 199 lines while preserving all code examples **tauri-capabilities (59% → 90%):** - Removed "What Are Capabilities?" explainer section - Removed "Security Boundaries" section (known concepts) - Added 4-step workflow with build verification and permission testing checkpoints **tauri-plugins (59% → 90%):** - Added 6-step end-to-end workflow (scaffold → implement → permissions → bindings → mobile → test) - Added verification checkpoints after key steps - Added a Testing and Verification section - Folded standalone "Android 16KB Page Size" note into the Android section **tauri-project-setup (79% → 90%):** - Condensed "What is Tauri?" from 7 lines to 2 - Added prerequisite verification checks (`rustc --version`, `node --version`) - Added validation checkpoints after both project creation methods **tauri-testing (79% → 86%):** - Removed redundant "Testing Approaches Overview" section - Added WebDriver setup validation checkpoints (version check, listener verify, binary exists) - Tightened best practices to essential Tauri-specific guidance </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 - [@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
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 @dchuk 👋
39 skills covering everything from Tauri's IPC architecture to platform-specific distribution across Android, iOS, macOS, Windows, and Linux. That's one of the most thorough Tauri v2 reference sets out there. The detail in things like the ASCII architecture diagrams and the security-focused skills (CSP, runtime authority, ecosystem security) really stands out.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:Changes made
All 5 skills:
tauri.conf.json,capability.json,tauri plugin new)tauri-architecture (39% → 90%):
tauri-capabilities (59% → 90%):
tauri-plugins (59% → 90%):
tauri-project-setup (79% → 90%):
rustc --version,node --version)tauri-testing (79% → 86%):
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.
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 🙏