feat: improve local-temporal skill score (90% → 94%)#3498
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @Alex-Tideman 👋 ## Description & motivation 💭 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 | |-------|--------|-------|--------| | local-temporal | 90% | 94% | +4% | | svelte-migrate | 86% | 86% | — | | auth-testing | 82% | 82% | — | | setup-worktree | 82% | 82% | — | <details> <summary>Changes made</summary> **Description improvement (main impact):** - **local-temporal**: Expanded the frontmatter description from a general summary to list specific concrete actions — `make start`, `pnpm dev:local-temporal`, and syncing `go.temporal.io/api` proto versions. Added "proto version mismatches" as an additional trigger term so the skill activates when developers hit the common "unknown field" error. **Content tightening:** - Removed the redundant `(aliased to pnpm dev:ui-server)` clause from the "Why not pnpm dev?" section - Condensed the proto sync explanation — collapsed the grpc-gateway architecture paragraph into a single sentence while preserving the critical "unknown field" diagnostic insight - Renamed the section header from "Keeping the ui-server in sync with the Temporal server branch" to "Keeping the ui-server proto versions in sync" for scannability </details> I also stress-tested your `local-temporal` skill against a few real-world task evals and it held up really well on the proto version mismatch debugging scenario — the 4-step sync workflow is exactly what a developer needs when they hit "unknown field" errors after switching branches. Kudos for that. ### Screenshots (if applicable) 📸 N/A — skill file change only. ### Design Considerations 🎨 N/A ## Testing 🧪 ### How was this tested 👻 - [x] Manual testing Ran `tessl skill review` before and after the change to verify the score improvement (90% → 94%). Description dimension improved from 90% to 100%. ### Steps for others to test: 🚶🏽♂️🚶🏽♀️ 1. Run `tessl skill review .claude/skills/local-temporal/SKILL.md` on the branch 2. Verify the score is 94% or higher ## Checklists ### Merge Checklist - [x] Skill review score maintained or improved - [x] No functional changes to skill content - [x] Diff is minimal and easy to review 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 🙏
|
@yogesh-tessl is attempting to deploy a commit to the Temporal Team on Vercel. A member of the Team first needs to authorize it. |
|
|
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 @Alex-Tideman 👋
truly impressive work. Four skills for auth testing, Svelte migration, worktree setup, and local Temporal dev. The fact that you already have a claude.yml in your workflows tells me you're serious about AI-assisted development, and the Svelte migration skill especially is the kind of thing that saves real time.
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the before/after:Changes made
Description improvement (main impact):
make start,pnpm dev:local-temporal, and syncinggo.temporal.io/apiproto versions. Added "proto version mismatches" as an additional trigger term so the skill activates when developers hit the common "unknown field" error.Content tightening:
(aliased to pnpm dev:ui-server)clause from the "Why not pnpm dev?" sectionalso stress-tested your
local-temporalskill against a few real-world task evals and it held up really well on the proto version mismatch debugging scenario. The 4-step sync workflow is exactly what a developer needs when they hit "unknown field" errors after switching branches. 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.