perp-funding-basis

Perpetual futures funding rate analysis and cash-carry basis trading — funding rate regimes, annualized basis signals, carry trade construction, and funding rate arbitrage between exchanges.

Quality

78%

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/perp-funding-basis/SKILL.md

Quality

Content

82%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 highly actionable with executable code, concrete API endpoints, and well-organized sections, scoring strongly across all dimensions. Minor gains are available by trimming editorial prose and making validation checkpoints explicit.

Suggestions

Tighten or remove editorial framing sentences (e.g. 'the single most important microstructure indicator') that restate knowledge Claude already has.

Add explicit validation checkpoints in the carry-trade and arbitrage workflows (e.g. 'Confirm net delta = 0 before collecting funding') to lift workflow clarity to 5.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight code blocks and tables with little padding, though occasional editorial prose (e.g. 'the single most important microstructure indicator in crypto derivatives') and basic funding mechanics could be trimmed. It does not reach score 5 because a few sentences over-explain context Claude already knows.	4 / 5
Actionability	Provides fully executable Python functions (funding_regime, annualized_basis, carry_trade_pnl, oi_funding_matrix), concrete OKX API endpoints, and specific numeric thresholds covering the common analytical cases — copy-paste ready.	5 / 5
Workflow Clarity	The carry-trade execution is laid out as a clear numbered sequence and the analytical framework is well structured, but validation/feedback checkpoints for risky operations (e.g. entry/exit, liquidation distance) are present only implicitly rather than as explicit verify steps, keeping it just below 5.	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with a cleanly signaled reference to load_skill("okx-market"). It is a single cohesive file rather than split across references, which is appropriate for this length but leaves minor organization room versus a fully decomposed structure.	4 / 5
	Total	17 / 20 Passed

Description

75%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 distinctive with strong domain keywords, but it omits an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when...' sentence would raise the score.

Suggestions

Add an explicit trigger clause such as 'Use when the user asks about funding rates, basis trades, carry trades, or perpetual futures positioning.'

Include natural synonyms and variations users might say, e.g. 'perps', 'perpetuals', or 'funding arbitrage'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'funding rate analysis', 'cash-carry basis trading', 'carry trade construction', and 'funding rate arbitrage between exchanges' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clearly stated but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Strong natural domain terms like 'funding rate', 'basis trading', and 'carry trade' are present, but common synonyms users might say (e.g. 'perps', 'perpetuals', 'funding arbitrage') are not explicitly enumerated.	4 / 5
Distinctiveness Conflict Risk	The description carves out a clear niche (perpetual funding rates, basis, and carry trades) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/perp-funding-basis/SKILL.md
Commit: 99e84ab

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.