CtrlK
BlogDocsLog inGet started
Tessl Logo

optimizing-staking-rewards

Compare and optimize staking rewards across validators, protocols, and blockchains with risk assessment. Use when analyzing staking opportunities, comparing validators, calculating staking rewards, or optimizing PoS yields. Trigger with phrases like "optimize staking", "compare staking", "best staking APY", "liquid staking", "validator comparison", "staking rewards", or "ETH staking options".

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

An actionable, well-structured body with executable commands and good reference navigation, weakened by time-sensitive inline data and the absence of explicit validation/feedback loops in the workflow.

Suggestions

Move hard-coded dates and APY percentages out of the output sample into a clearly labelled example, or mark them as illustrative, to avoid time-sensitive noise that decays.

Add explicit validation checkpoints between workflow steps (e.g. verify API response before optimizing, confirm positions parsed before projecting yields) with a fix→retry loop rather than only delegating to errors.md.

Cross-link the examples.md reference from the Examples section so the one-level-deep navigation is consistent with errors.md and implementation.md.

DimensionReasoningScore

Conciseness

Mostly lean and free of concept over-explanation, but inline time-sensitive values (e.g. '2025-01-15 15:30 UTC', hard-coded APY percentages in the output block) add noise that does not earn its place.

2 / 3

Actionability

Fully executable, copy-paste-ready commands with concrete flags ('--asset ETH --amount 10', '--optimize --positions "10 ETH @ lido 4.0%..."') plus a specific sample output table.

3 / 3

Workflow Clarity

Steps are clearly numbered and sequenced, but there are no explicit validation checkpoints or fix→retry feedback loops; error handling is delegated to a reference file rather than inline.

2 / 3

Progressive Disclosure

SKILL.md is an overview that points to real one-level-deep references (errors.md, implementation.md) plus a Resources list, with content appropriately split and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that names concrete actions, provides natural trigger phrases, and explicitly covers both what and when. No over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Compare and optimize staking rewards across validators, protocols, and blockchains', 'risk assessment', 'comparing validators', 'calculating staking rewards', 'optimizing PoS yields' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Compare and optimize staking rewards...') and when ('Use when analyzing staking opportunities, comparing validators, calculating staking rewards, or optimizing PoS yields').

3 / 3

Trigger Term Quality

Strong natural keyword coverage a user would actually say: 'optimize staking', 'best staking APY', 'liquid staking', 'validator comparison', 'staking rewards', 'ETH staking options'.

3 / 3

Distinctiveness Conflict Risk

Clear PoS-staking-yield niche with distinct, specific triggers; unlikely to be selected for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.