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
Quality
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 well-structured skill description with explicit 'Use when' guidance and strong trigger terms specific to the Yellow Network ecosystem. The main weakness is that the capabilities section could be more concrete about specific actions (e.g., 'create state channels', 'handle channel disputes') rather than general development activities.
Suggestions
Add more concrete actions to the capabilities section, such as 'create and manage state channels', 'handle channel disputes', 'sign and verify state updates' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Yellow Network, Nitrolite/ERC-7824, state channels) and mentions some actions like 'building apps', 'implementing state channels', 'connecting to ClearNodes', but lacks concrete specific actions like 'create channels', 'sign states', or 'settle disputes'. | 2 / 3 |
Completeness | Clearly answers both what ('Yellow Network and Nitrolite development best practices for building state channel applications') and when ('Use when building apps 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 users would say: 'Yellow SDK', 'state channels', 'ClearNodes', 'off-chain transactions', 'application sessions', 'ERC-7824', 'Nitrolite'. These are specific technical terms that users working in this domain would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche with highly specific triggers like 'Yellow SDK', 'Nitrolite', 'ERC-7824', 'ClearNodes'. These are unique identifiers that would not conflict with generic blockchain or development skills. | 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 strong actionable guidance with executable code examples and good progressive disclosure through organized rule files. However, it includes some unnecessary conceptual explanation that Claude doesn't need, and the multi-step workflows (especially authentication) lack explicit validation checkpoints that would help catch errors early in state channel operations.
Suggestions
Remove or significantly condense the 'What is Yellow Network?' section - Claude doesn't need explanations of what state channels or chain abstraction are
Add explicit validation steps to the authentication flow (e.g., 'Verify JWT token received before proceeding', 'Check connection state before sending messages')
Include error recovery guidance in the authentication and session creation workflows (what to do if auth_challenge fails, how to handle session creation errors)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'What is Yellow Network?' section explaining concepts Claude could infer), but the code examples and patterns are reasonably efficient. The architecture diagram and feature list add bulk without being strictly necessary for actionable guidance. | 2 / 3 |
Actionability | Provides fully executable code examples for connection, authentication, message signing, and session management. Code is copy-paste ready with proper imports and complete implementations. The DO/DON'T lists give specific, concrete guidance. | 3 / 3 |
Workflow Clarity | Authentication flow mentions numbered steps but lacks explicit validation checkpoints. The connection pattern shows reconnection logic but doesn't include verification that authentication succeeded before proceeding. Multi-step processes like session creation lack explicit 'verify before continuing' steps. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview, well-signaled one-level-deep references to rules/ directory files, and organized sections. The SDK components table and additional resources are appropriately placed. Navigation is intuitive with categorized 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
5342bca
- 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.