feat: improve zuplo-guide skill score from 74% to 90%#6
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @ntotten 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for `zuplo-guide`. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | zuplo-guide | 74% | 90% | +16% | | zudoku-guide | 83% | 83% | — | | zuplo-cli | 86% | 86% | — | | zuplo-monetization | 94% | 94% | — | I picked `zuplo-guide` because it had the most headroom and it's the "front door" skill — the one users hit first for general Zuplo development. <details> <summary>Changes made to <code>zuplo-guide</code></summary> - **Expanded description with natural trigger terms** — added "rate limiting", "API keys", "JWT", "OAuth", "CORS", "API proxy", "API management" so the skill gets matched when users describe tasks in everyday language (not just Zuplo-internal terminology) - **Added concrete route configuration example** — a copy-paste-ready `routes.oas.json` snippet with `x-zuplo-route`, `urlForwardHandler`, and inbound policy references - **Added concrete policy configuration example** — a `policies.json` snippet showing API key auth and rate limiting setup with realistic options - **Added specific CLI validation commands** — `npx zuplo dev`, `npx zuplo test`, `npx zuplo deploy`, and `npx zuplo list` in the development workflow and error handling sections - **Added explicit feedback loop** — "if tests fail, read the error output, fix the configuration, and re-run before deploying" - **Reduced repetition** — consolidated the "read docs first" messaging to a single concise critical rule instead of restating it in multiple sections - **Tightened core concepts** — removed redundant explanations, clarified policy pipeline directionality (inbound before handler, outbound after) </details> I also stress-tested your `zuplo-monetization` skill against a few real-world task evals and it held up really well on multi-tier Stripe billing with metered usage tracking. 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 🙏
There was a problem hiding this comment.
Pull request overview
Improves the zuplo-guide skill’s matchability and usefulness by expanding its description with common trigger terms and adding concrete configuration/workflow examples for Zuplo routes, policies, and CLI validation steps.
Changes:
- Expanded the skill frontmatter description with additional Zuplo-relevant trigger terms (auth, rate limiting, CORS, proxying, etc.).
- Added example
routes.oas.json/policies.jsonsnippets plus CLI validation/deploy commands and a tighter troubleshooting workflow. - Refined core concepts phrasing (policy pipeline directionality, web-standards runtime) and reduced repeated “read docs” messaging.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+87
to
+90
| A route in `config/routes.oas.json` with API key auth and rate limiting policies: | ||
|
|
||
| ```json | ||
| { |
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
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 @ntotten 👋
that is really clean setup, covering both Zuplo and Zudoku in one repo and supporting both Claude Code and Cursor plugin installs. The agentskills.io integration makes it easy for people to discover these.
ran your skills through
tessl skill reviewat work and found some targeted improvements forzuplo-guide. Here's the before/after:picked
zuplo-guidebecause it had the most headroom and it's the "front door" skill, the one users hit first for general Zuplo development.Changes made to
zuplo-guideroutes.oas.jsonsnippet withx-zuplo-route,urlForwardHandler, and inbound policy referencespolicies.jsonsnippet showing API key auth and rate limiting setup with realistic optionsnpx zuplo dev,npx zuplo test,npx zuplo deploy, andnpx zuplo listin the development workflow and error handling sectionsquick 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.