feat: improve upgrade-stripe skill score (55% → 94%)#421
Open
yogesh-tessl wants to merge 1 commit into
Open
Conversation
Hey @stevekaliski-stripe 👋 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 | |-------|--------|-------|--------| | upgrade-stripe | 55% | 94% | +39% | | stripe-best-practices | 100% | 100% | — | | stripe-projects | 18% | 18% | — | Your `stripe-best-practices` skill already scores a perfect 100% — really well structured with the routing table and progressive disclosure into reference files. The `upgrade-stripe` skill had the most improvement headroom, so I focused there. **Note:** These skills are auto-generated from `docs.stripe.com` via `skills/sync.js`, so the next sync will overwrite these changes. I'd suggest applying similar improvements to the generation source on your docs side — particularly the description expansion and content trimming patterns described below. <details> <summary>Changes made to upgrade-stripe</summary> - **Expanded frontmatter description** — added specific SDK names (stripe-node, stripe-python, stripe-ruby, etc.), concrete actions (resolving breaking changes, migrating deprecated parameters), and a `Use when...` clause with six trigger scenarios. This lifted the description score from 22% → 100%. - **Trimmed explanatory content** — removed "Types of Changes" section (backward-compatible vs breaking definitions), removed redundant "Best Practice" code example, removed "Important Notes" section. These are concepts the LLM already understands — trimming them improves token efficiency without losing actionability. - **Added validation checkpoints** — step 5 in the upgrade checklist now includes explicit "fix before proceeding" guidance when API calls fail, and step 10 adds a rollback plan. - **Condensed mobile SDK section** — replaced verbose semver explanation with concise one-liners. - **Synced provider directories** — updated both providers/claude/ and providers/cursor/ copies to match. </details> I also stress-tested your `stripe-best-practices` skill against a few real-world task evals and it held up really well on PaymentIntent-to-Checkout-Session migration routing with dynamic payment methods. 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 🙏
yogesh-tessl
requested review from
jleong-stripe,
matv-stripe,
sgr-stripe and
stevekaliski-stripe
as code owners
|
|
|
|
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 @stevekaliski-stripe 👋
the way you've wired up the sync-skills workflow to pull directly from docs.stripe.com is really smart. Keeps the skills always fresh without manual updates. Spotted a few places in the SKILL.md files where we can tighten things up.
ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:your
stripe-best-practicesskill already scores a perfect 100%. Really well structured with the routing table and progressive disclosure into reference files. Theupgrade-stripeskill had the most improvement headroom, so I focused there.Changes made to upgrade-stripe
Use when...clause with six trigger scenarios. This lifted the description score from 22% → 100%.also stress-tested your
stripe-best-practicesskill against a few real-world task evals and it held up really well on PaymentIntent-to-Checkout-Session migration routing with dynamic payment methods. 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.