token-unlock-treasury

Token unlock schedule analysis and project treasury tracking — vesting cliffs, linear unlocks, team/investor/ecosystem token releases, treasury diversification, and sell pressure forecasting.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/token-unlock-treasury/SKILL.md

Quality

Content

65%

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

The content is rich in domain-specific empirical data and complete executable code, making it highly actionable for token-unlock analysis. It is held back by verbose explanatory prose, the lack of explicit validation checkpoints in the workflow, and a monolithic structure with no progressive disclosure into separate files.

Suggestions

Trim prose that restates concepts Claude already knows (e.g. definitions of cliff vs linear unlocks, the overview's first-principles framing) so each remaining token adds novel empirical value.

Add an explicit analysis workflow with a sequence and a verification checkpoint — e.g. cross-check unlock amounts against circulating supply and daily volume before scoring impact, and flag data older than the source's last update.

Move the detailed protocol unlock calendar table and/or the full Python frameworks into a references/ file (e.g. REFERENCES.md) referenced one level deep from the body, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The empirical tables, multipliers, and complete functions earn their place, but prose such as the overview paragraph and restating what cliff/linear unlocks mean explains concepts Claude already knows and could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	2 / 3
Actionability	Multiple complete, executable Python functions (assess_unlock_impact, treasury_signal, emission_analysis) with full logic plus a concrete copy-paste output format template match the fully-executable top anchor.	3 / 3
Workflow Clarity	The output format acts as a structured checklist and sections are well ordered, but there is no explicit step sequence or validation/verification checkpoint for the analysis, fitting the 'sequence present but checkpoints missing' anchor.	2 / 3
Progressive Disclosure	The ~270-line body is well-sectioned but entirely monolithic with no external references, and content such as the full protocol calendar table and frameworks arguably belong in separate files, matching the 'content that should be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

82%

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

The description is specific, distinctive, and rich in natural trigger terms, clearly conveying the skill's domain and concrete actions. Its main weakness is the absence of an explicit 'when to use' clause, which leaves the trigger guidance implied rather than stated.

Suggestions

Add an explicit 'Use when…' clause naming user-facing triggers, e.g. 'Use when analyzing a token's upcoming unlocks, vesting schedules, or treasury health, or when the user mentions sell pressure from token releases.'

Include a few common phrasing variations users might say (e.g. 'token vesting', 'FDV dilution', 'token release calendar') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete actions — 'Token unlock schedule analysis', 'project treasury tracking', 'vesting cliffs', 'linear unlocks', 'treasury diversification', and 'sell pressure forecasting' — matching the anchor that lists multiple specific concrete actions.	3 / 3
Completeness	It clearly states what the skill does but contains no 'Use when…' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Natural, user-spoken crypto terms are well covered — 'token unlock', 'vesting cliffs', 'linear unlocks', 'treasury', and 'sell pressure forecasting' — which is the kind of coverage the top anchor calls for.	3 / 3
Distinctiveness Conflict Risk	The token-unlock/treasury niche is specific with distinct triggers ('vesting cliffs', 'sell pressure forecasting') and is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/token-unlock-treasury/SKILL.md
Commit: 8643fcd

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.