yellow-best-practices
Yellow Network and Nitrolite (ERC-7824) development best practices for building state channel applications. Use when building apps with Yellow SDK, implementing state channels, connecting to ClearNodes, managing off-chain transactions, or working with application sessions.
86
81%
Does it follow best practices?
Impact
91%
1.82xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies a specific technology niche (Yellow Network/Nitrolite/ERC-7824) and includes an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that the capabilities described are somewhat high-level ('development best practices') rather than listing specific concrete actions the skill enables. The domain-specific terminology makes it highly distinctive and unlikely to conflict with other skills.
Suggestions
Replace 'development best practices' with specific concrete actions, e.g., 'Opens and closes state channels, signs and validates off-chain states, deploys adjudicator contracts, handles channel disputes.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Yellow Network, Nitrolite/ERC-7824, state channels) and mentions some actions like 'building state channel applications', 'implementing state channels', 'connecting to ClearNodes', 'managing off-chain transactions', but these are more like topic areas than concrete specific actions (e.g., no mention of specific operations like 'open/close channels', 'sign states', 'deploy contracts'). | 2 / 3 |
Completeness | Clearly answers both 'what' (development best practices for building state channel applications with Yellow Network and Nitrolite) and 'when' (explicit 'Use when' clause covering building with Yellow SDK, implementing state channels, connecting to ClearNodes, managing off-chain transactions, or working with application sessions). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms a developer would use: 'Yellow SDK', 'state channels', 'ClearNodes', 'off-chain transactions', 'application sessions', 'ERC-7824', 'Nitrolite'. These are the specific terms someone working in this domain would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with very specific technology references (Yellow Network, Nitrolite, ERC-7824, ClearNodes, Yellow SDK) that are unlikely to conflict with any other skill. This is a clear niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides good actionable code examples and excellent progressive disclosure with clear references to detailed rule files. However, it could be more concise by trimming conceptual explanations Claude already knows, and the workflow clarity suffers from an incomplete authentication flow and missing validation/error recovery steps in the multi-step processes.
Suggestions
Remove or significantly trim the 'What is Yellow Network?' section and architecture diagram - Claude doesn't need conceptual background; focus on what's unique to implementation
Complete the authentication flow with executable code for all three steps, including error handling and a validation checkpoint after auth_verify
Add an explicit end-to-end workflow sequence (connect → authenticate → create session → transact → close session) with validation checkpoints at each stage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is Yellow Network?' section explains concepts Claude doesn't need spelled out (what state channels are, what 'non-custodial' means). The architecture diagram and bullet points add some value but the conceptual overview is unnecessarily verbose. The DO/DON'T lists also contain some obvious guidance (don't expose private keys, don't skip error handling). | 2 / 3 |
Actionability | The skill provides fully executable JavaScript code examples for connection, authentication, message signing, and app sessions. The code is copy-paste ready with real imports from the SDK, concrete class implementations, and specific function calls. | 3 / 3 |
Workflow Clarity | The authentication flow shows steps 1 and 2 but step 3 is just a comment ('Store JWT token for reconnection') with no code. The overall workflow from connection → auth → session creation → usage → session closure is implied but not explicitly sequenced with validation checkpoints. No error recovery feedback loops are shown for the multi-step auth process. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview in the main file and well-signaled one-level-deep references to the rules/ directory with priority labels (Critical/High/Medium). Additional resources are cleanly listed. Content is appropriately split between the overview and detailed rule files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.