CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

1.82x
Quality

71%

Does it follow best practices?

Impact

91%

1.82x

Average score across 3 eval scenarios

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./data/skills-md/0xarcano/agent-skills/yellow-best-practices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with actionable code examples, but it over-explains domain background and references a non-existent rules/ directory, undermining progressive disclosure. Workflow clarity is capped because batch/destructive channel operations lack validation checkpoints.

Suggestions

Ship the referenced rules/ files (01-connection.md through 06-error-handling.md) or remove the broken links and inline only the rules that matter, so progressive-disclosure references resolve to real files.

Add an explicit end-to-end workflow with validation checkpoints (e.g. connect -> authenticate -> verify signature -> open session -> verify on-chain -> close), especially feedback loops for session close and settlement.

Trim the ASCII architecture diagram, 'What is Yellow Network?' feature bullets, and the SDK components table to reduce padding that restates context Claude can infer.

DimensionReasoningScore

Conciseness

Mostly efficient with tight code blocks, but the ASCII architecture diagram, the 'What is Yellow Network?' feature bullets, and the SDK components table re-explain domain/context Claude can infer, adding padding.

3 / 5

Actionability

Provides mostly executable, copy-paste-ready code (reconnection, EIP-712 auth, signing, app session creation) with minor gaps such as the commented-out auth_challenge handling and an ethers v5 signing snippet.

4 / 5

Workflow Clarity

Sections are organized by topic but there is no end-to-end sequenced workflow, and destructive/channel operations (session close, settlement) lack explicit validation checkpoints or feedback loops, capping this dimension at 3.

3 / 5

Progressive Disclosure

The body points to a 'rules/' directory with six referenced files (e.g. rules/01-connection.md), but that directory is absent from the bundle, so the signaled one-level-deep references are broken; inlined detail stands in for missing files.

2 / 5

Total

12

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that pairs a clear capability statement with an explicit, multi-trigger 'Use when' clause and a well-scoped niche. It is slightly jargon-heavy and could add a few natural-language synonyms, but otherwise scores highly across all dimensions.

DimensionReasoningScore

Specificity

Lists several concrete actions ('building apps with Yellow SDK, implementing state channels, connecting to ClearNodes, managing off-chain transactions, or working with application sessions'), with only minor coverage gaps around settlement/dispute handling.

4 / 5

Completeness

Clearly answers both 'what' ('development best practices for building state channel applications') and 'when' via an explicit 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural phrases users would say ('building apps', 'state channels', 'off-chain transactions') but the list leans on technical jargon (ERC-7824, ClearNodes, application sessions) and omits common synonyms.

4 / 5

Distinctiveness Conflict Risk

Targets a clearly defined niche (Yellow Network / Nitrolite state channels) with distinct triggers, creating minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 missing

Warning

Total

15

/

16

Passed

Repository
NeverSight/skills_feed
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.