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

61%

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

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 content is substantive and actionable with executable Python frameworks and a clear output template, but it is a monolithic single-file skill with some prose padding and no externalized references or explicit stepwise workflow.

Suggestions

Externalize the detailed protocol unlock calendar table and/or the Python frameworks into a references/ file and link to it from SKILL.md to reduce inline bulk.

Trim prose that restates widely known crypto concepts and remove code comments that merely restate threshold logic.

Add a short numbered analysis procedure (e.g. 1. gather tokenomics → 2. assess unlocks → 3. treasury health → 4. emission → 5. forecast) so the workflow is explicit rather than implied by the output template.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with dense tables and substantive code, but includes some unnecessary explanation Claude already knows (e.g. 'Token unlocks are one of the most predictable and high-impact supply-side events in crypto') and code comments that restate obvious threshold logic.	3 / 5
Actionability	Provides three fully executable Python functions with real thresholds and return values, empirical data tables, concrete data-source URLs, and a complete output-format template, with only minor gaps (input data structures like `token.monthly_unlock` are referenced but not defined).	4 / 5
Workflow Clarity	There is no explicit numbered procedure; the Output Format section acts as an implicit checklist and the analysis sequence (tokenomics → unlocks → treasury → emission → forecast) is only implied, with no explicit validation checkpoints.	3 / 5
Progressive Disclosure	The body is a monolithic ~270-line single file with no bundle references; all detail (taxonomy, three Python frameworks, protocol calendar, output template) is inlined, though it is organized into clear ## sections.	3 / 5
	Total	13 / 20 Passed

Description

66%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.

The description is specific and well-targeted to a clear crypto niche with strong natural keywords, but it omits an explicit 'Use when...' trigger clause, which limits its completeness score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks about token vesting schedules, upcoming unlocks, treasury health, or sell pressure forecasting.'

Include common synonyms users might say (e.g. 'tokenomics', 'vesting schedule', 'FDV', 'cliff unlock') to broaden trigger coverage.

Replace generic verbs ('analysis', 'tracking') with more concrete actions like 'forecast', 'assess', 'quantify' where applicable.

Dimension	Reasoning	Score
Specificity	Names concrete sub-domains ('vesting cliffs, linear unlocks, team/investor/ecosystem token releases, treasury diversification, and sell pressure forecasting') but relies on only two generic verbs ('analysis', 'tracking'), so coverage is strong yet the actions themselves are not maximally specific.	4 / 5
Completeness	Provides a clear 'what' (analysis and tracking of unlocks/treasury) but lacks any explicit 'Use when...' trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural-language keyword coverage ('token unlock', 'vesting cliffs', 'linear unlocks', 'treasury', 'sell pressure'), but omits common synonyms a user might say like 'tokenomics', 'vesting schedule', or 'FDV'.	4 / 5
Distinctiveness Conflict Risk	The token-unlock/treasury niche is distinct with low conflict risk, though it could marginally overlap with broader crypto market-analysis or tokenomics skills.	4 / 5
	Total	15 / 20 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: 1907e47

Reviewed: 1 day 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.