feat: add quick-start code examples to solana-dev skill#36
Open
popey wants to merge 1 commit intosolana-foundation:mainfrom
Open
feat: add quick-start code examples to solana-dev skill#36popey wants to merge 1 commit intosolana-foundation:mainfrom
popey wants to merge 1 commit intosolana-foundation:mainfrom
Conversation
Hullo @solana-foundation 👋 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 | |-------|--------|-------|--------| | solana-dev | 93% | 100% | +7% | The skill was already in great shape — the description scored a perfect 100%. The content score moved from 85% to 100% by addressing the two specific gaps the evaluator flagged. <details> <summary>Changes made</summary> ### `solana-dev` skill **Added a "Quick-start patterns" section** with two minimal, executable code snippets: 1. **framework-kit wallet + provider (Next.js)** — a copy-paste ready `SolanaProvider` setup using `@solana/react-hooks` and `@solana/client`, matching the stack decisions already documented in the skill. 2. **web3-compat boundary adapter** — a concrete example showing `toAddress()` / `toPublicKey()` conversions from `@solana/web3-compat`, reinforcing the "web3.js only at boundaries" architectural rule the skill already recommends. Both snippets are drawn directly from your existing reference files (`frontend-framework-kit.md` and `kit-web3-interop.md`), so they're consistent with the patterns you've already documented. The evaluator specifically called out the lack of inline executable examples as the only gap — these additions close it without adding bulk. </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 - [@popey](https://github.com/popey) - 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
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.
Hullo @solana-foundation 👋
I ran your skills through
tessl skill reviewat work and found some targeted improvements. Here's the full before/after:The skill was already in great shape — the description scored a perfect 100%. The content score moved from 85% to 100% by addressing the two specific gaps the evaluator flagged.
Changes made
solana-devskillAdded a "Quick-start patterns" section with two minimal, executable code snippets:
framework-kit wallet + provider (Next.js) — a copy-paste ready
SolanaProvidersetup using@solana/react-hooksand@solana/client, matching the stack decisions already documented in the skill.web3-compat boundary adapter — a concrete example showing
toAddress()/toPublicKey()conversions from@solana/web3-compat, reinforcing the "web3.js only at boundaries" architectural rule the skill already recommends.Both snippets are drawn directly from your existing reference files (
frontend-framework-kit.mdandkit-web3-interop.md), so they're consistent with the patterns you've already documented. The evaluator specifically called out the lack of inline executable examples as the only gap — these additions close it without adding bulk.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 - @popey - if you hit any snags.
Thanks in advance 🙏