Open
Conversation
Hey @ishaan-jaff 👋 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 | |-------|--------|-------|--------| | add-team | 82% | 100% | +18% | | add-model | 87% | 100% | +13% | | delete-model | 87% | 100% | +13% | | add-key | 82% | 94% | +12% | | view-usage | 92% | 97% | +5% | <details> <summary>What changed</summary> - **Added explicit "Use when..." clauses** to all 5 skill descriptions — helps Claude (and other agents) know exactly when to select each skill - **Expanded trigger terms** in `add-model` and `delete-model` descriptions (e.g. "register", "deploy", "configure", "remove", "unregister") so natural user phrasing matches better - **Standardised description format** from YAML block scalars (`>`) to quoted strings across all 5 skills - **Added verification steps** to `add-key` (GET `/key/info` to confirm creation) and `add-team` (GET `/team/info` to confirm creation) - **Added explicit error handling** with specific HTTP status codes (401, 400) and remediation steps to `add-key`, `add-team`, and `view-usage` - **Aligned variable names** in `add-key` and `add-team` — added `BASE=$LITELLM_BASE_URL` / `KEY=$LITELLM_API_KEY` assignment lines so the curl commands are consistent with the Setup section </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 @ishaan-jaff 👋
21 skills covering the full CRUD surface of the LiteLLM proxy API - users, teams, keys, orgs, models, MCP servers, and agents with a clean one-folder-per-skill layout. Really like how each SKILL.md walks the user through setup and API calls interactively rather than just documenting endpoints. Wanted to tighten up a few of these skill files.
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:What changed
add-modelanddelete-modeldescriptions (e.g. "register", "deploy", "configure", "remove", "unregister") so natural user phrasing matches better>) to quoted strings across all 5 skillsadd-key(GET/key/infoto confirm creation) andadd-team(GET/team/infoto confirm creation)add-key,add-team, andview-usageadd-keyandadd-team— addedBASE=$LITELLM_BASE_URL/KEY=$LITELLM_API_KEYassignment lines so the curl commands are consistent with the Setup sectionHonest 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.
I also added a lightweight GitHub Action that auto-reviews any skill.md changed in a PR (includes min permissions, uses a pinned action version, only posts a review comment).
This means that it gives you and your contributors an instant quality signal before you have to review yourself (no signup, no tokens needed).
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 🙏