feat: improve ai-sdk skill score (89% → 95%)#80
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @johnlindquist 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements for the `ai-sdk` skill. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | ai-sdk | 89% | 95% | +6% | <details> <summary>Changes made</summary> - **Tightened description for distinctiveness**: Added "with the AI SDK" and "through AI SDK provider packages" anchors so generic trigger terms (streaming, embeddings, etc.) are scoped to the SDK context and less likely to collide with other skills - **Quoted the description string**: Switched to standard YAML quoted format - **Consolidated the verification section**: Renamed "Critical: Do Not Trust Internal Knowledge" → "Always Verify Against Source" — same safety message, fewer tokens. Reduced 9 numbered steps to 6 by merging related points and removing duplication - **Removed inline curl command**: The long `curl | jq` command for fetching model IDs was already documented in `references/ai-gateway.md` — pointing there instead of duplicating it saves ~50 tokens per injection - **Merged prerequisites paragraph**: Combined the two-paragraph prerequisites into one sentence without losing any guidance </details> I also stress-tested your `ai-sdk` skill against a few real-world task evals and it held up really well on v5-to-v6 migration scenarios with `useChat` transport rewiring and `generateObject` → `Output.object()` conversion. 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 🙏
Melkeydev
approved these changes
May 16, 2026
Collaborator
|
Please Commits must have verified signatures - then I will merge |
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 @johnlindquist 👋
truly impressive work. 26 skills covering everything from the AI SDK to Vercel Firewall, this is one of the most comprehensive plugin repos I've come across. The relational knowledge graph approach in vercel.md is a really thoughtful way to tie it all together.
ran your skills through
tessl skill reviewat work and found some targeted improvements for theai-sdkskill. Here's the before/after:Changes made
curl | jqcommand for fetching model IDs was already documented inreferences/ai-gateway.md- pointing there instead of duplicating it saves ~50 tokens per injectionalso stress-tested your
ai-sdkskill against a few real-world task evals and it held up really well on v5-to-v6 migration scenarios withuseChattransport rewiring andgenerateObject→Output.object()conversion. 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.