Skip to content

feat: improve skill scores for hook workspace#1

Open
rohan-tessl wants to merge 1 commit intoheyAyushh:mainfrom
rohan-tessl:improve/skill-review-optimization
Open

feat: improve skill scores for hook workspace#1
rohan-tessl wants to merge 1 commit intoheyAyushh:mainfrom
rohan-tessl:improve/skill-review-optimization

Conversation

@rohan-tessl
Copy link
Copy Markdown

@rohan-tessl rohan-tessl commented Apr 6, 2026

Hey @ChrisTowles 👋

I ran your skills through tessl skill review at work and found some targeted improvements.

image

Here's the full before/after:

Skill Before After Change
typescript-best-practices 83% 92% +9%
screenshot 90% 99% +9%
towles-tool 96% 100% +4%
setup-multi-repo 99% 99% +0%

This PR covers all 4 skills in the repo — intentionally scoped to keep things reviewable.

Changes summary

typescript-best-practices (+9%)

  • Rewrote description from abstract framing to concrete actions (generates Zod schemas, converts enums, applies branded types, builds discriminated unions, configures DeepImmutable state trees)
  • Converted description from YAML chevron (>) to quoted string format
  • Trimmed explanatory prose that restated what code examples already demonstrate
  • Removed redundant exhaustive switch handler example (kept the guidance)
  • Tightened AsyncGenerator and DeepImmutable section intros

screenshot (+9%)

  • Converted description from YAML chevron (>) to quoted string format
  • Added specific tool name (cosmic-screenshot on Wayland) to description for better specificity
  • Added error-recovery step 3 to the workflow: check stderr if no screenshot file is found

towles-tool (+4%)

  • Expanded description from category labels ("git helpers", "developer utilities") to specific concrete actions (create branches from issues, open PRs, clean merged branches, generate journal notes, etc.)

setup-multi-repo (+0%)

  • Converted description from YAML chevron (>) to quoted string format (cosmetic, score was already 99%)

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 🙏

Hey @heyAyushh 👋

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 |
|-------|--------|-------|--------|
| hook-serve | 73% | 89% | +16% |
| kafka-openclaw-hook | 79% | 94% | +15% |
| relay-core | 83% | 100% | +17% |
| contract-authoring | 80% | 97% | +17% |
| kafka-add-broker | 90% | 90% | +0% |

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>

- Converted all frontmatter descriptions from YAML chevron (>) to quoted strings for consistent parsing
- Expanded descriptions with concrete action verbs — e.g. "configure Kafka topics, validate hook contracts, register ingress/egress adapters" instead of abstract "build, maintain, and operate"
- Added natural trigger terms users would actually say — "webhook source", "toml config errors", "cross-service contracts", "AWS MSK", "Confluent"
- Added explicit validation feedback loops to workflows — e.g. "If clippy fails on contract changes, verify envelope schema compatibility in relay-core"
- Annotated Key Docs and References with brief descriptions of what each file contains and when to consult it
- Added validate-fix workflow to contract-authoring skill with explicit error recovery steps
- Trimmed redundant "What a Contract Is" section in contract-authoring — consolidated into a concise opening paragraph

</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 🙏
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant