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

66%

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

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 highly actionable with executable code and concrete API guidance, but it is a monolithic single file with some tightening possible and lacks explicit validation/feedback checkpoints for its risky trading workflows. Adding verification steps and splitting detail into a reference file would improve the two weaker dimensions.

Suggestions

Add explicit validation checkpoints to the risky workflows — e.g. verify funding-rate sign and basis before entering a carry trade, and a re-check before closing each leg.

Move the detailed API reference and/or the historical-pattern statistics into a separate reference file referenced from SKILL.md to reduce monolithic bulk.

Trim the duplicated units-convention explanation to a single concise note to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with tight tables and executable snippets, but includes some explanation that could be tightened (e.g. the repeated units-convention block and conceptual framing of funding mechanics), fitting the 'mostly efficient but could be tightened' anchor rather than the fully lean one.	2 / 3
Actionability	Provides fully executable Python functions (funding_regime, annualized_basis, carry_trade_pnl, oi_funding_matrix), concrete OKX API endpoints, specific numeric examples, and a numbered execution recipe — copy-paste ready, matching the top anchor.	3 / 3
Workflow Clarity	A numbered carry-trade execution sequence and a structured output format exist, but there are no explicit validation/verification checkpoints or feedback loops for risky operations (carry trades carry stated liquidation/execution risk), which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	No bundle files exist, so this scores against the actual single-file structure: it is well-organized with clear sections but is a ~250-line monolithic SKILL.md with no split-out reference, fitting the 'some structure but content that could be separate is inline' anchor.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 occupies a clear niche, but it lacks an explicit 'Use when...' trigger clause and its trigger terms lean technical, which caps completeness and trigger-term quality. Adding natural-language trigger guidance would lift the two weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when analyzing perpetual funding rates, building cash-carry or basis trades, or comparing cross-exchange funding spreads.'

Add natural user phrasing alongside the technical terms (e.g. 'perp funding', 'funding arbitrage', 'basis trade') so the description matches how users actually request the skill.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions ('funding rate regimes, annualized basis signals, carry trade construction, and funding rate arbitrage between exchanges'), matching the anchor for listing several specific concrete actions rather than naming a domain with only partial actions.	3 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2 rather than 3.	2 / 3
Trigger Term Quality	Terms like 'funding rate', 'cash-carry basis trading', and 'carry trade' are relevant domain keywords a crypto trader would say, but they skew technical and miss common natural variations, fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	The perpetual-funding/basis-trading niche is specific and unlikely to overlap with unrelated skills, matching the clear-niche anchor; voice is third person so no specificity penalty applies.	3 / 3
	Total	10 / 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/perp-funding-basis/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.