CtrlK
BlogDocsLog inGet started
Tessl Logo

bond-futures-basis

Analyze the bond futures basis by pricing futures, identifying the cheapest-to-deliver, and comparing with yield curves to assess delivery option value and basis trading opportunities. Use when analyzing bond futures, computing the basis, identifying CTD bonds, calculating implied repo rates, or evaluating basis trades.

76

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A well-structured, actionable analysis skill with concise tool routing and a clearly sequenced workflow. The main gap is the absence of explicit validation checkpoints and error-recovery feedback loops in the workflow.

Suggestions

Add explicit validation/sanity-check steps — e.g., confirm the CTD returned by bond_future_price is successfully priced by bond_price, and verify implied repo values fall within plausible market bounds before assigning a Rich/Fair/Cheap assessment.

Include error-recovery guidance for tool failures (e.g., what to do if bond_price returns no data for the CTD, or if the interest_rate_curve list step fails) so the workflow has a feedback loop rather than an implicit happy path.

Give the optional credit_curve step (step 6) a clear decision checkpoint noting when sovereign credit context materially changes the basis assessment, so the optional branch has an explicit gate.

DimensionReasoningScore

Conciseness

The body is lean with no basic-concept padding — it jumps straight to tool capabilities, a numbered workflow, and compact output tables, with the 'Core Principles' paragraph providing routing logic rather than filler.

3 / 3

Actionability

Names exact MCP tools, specifies inputs ('Call bond_future_price with the contract RIC'), the fields to extract at each step, and concrete output tables — fully actionable instruction-style guidance with no pseudocode gaps.

3 / 3

Workflow Clarity

The 6-step sequence is clearly ordered with explicit data chaining (CTD from step 1 feeds step 2), but there are no explicit validation checkpoints or error-recovery feedback loops; checkpoints like the implied-repo comparison are only implicit.

2 / 3

Progressive Disclosure

A single self-contained file (~60 lines) with well-organized sections and no external bundle files or nested references; per the simple-skill note, clean organization without external references warrants a 3.

3 / 3

Total

11

/

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 states concrete capabilities and provides explicit, natural trigger terms covering both the what and the when. It is concise, distinct, and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'pricing futures, identifying the cheapest-to-deliver, and comparing with yield curves' and 'computing the basis, identifying CTD bonds, calculating implied repo rates' — matching the level-3 anchor for specific concrete actions.

3 / 3

Completeness

Explicitly answers both 'what' (analyze basis via pricing, CTD, yield curves) and 'when' ('Use when analyzing bond futures, computing the basis…') with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers natural domain terms a user would say — 'bond futures, computing the basis, CTD bonds, implied repo rates, basis trades' — with good variation rather than jargon-only phrasing.

3 / 3

Distinctiveness Conflict Risk

The bond-futures-basis niche is specific with distinct triggers ('implied repo rates', 'CTD bonds', 'basis trades'), making overlap with other skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
anthropics/financial-services
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.