bondterminal-x402

Query BondTerminal API using x402 keyless payments. No API key needed — pay $0.01 USDC per request on Base mainnet. Use when users ask for Argentine bond data, analytics, cashflows, history, riesgo país, or ISIN/ticker lookups (e.g. AL30, GD30, US040114HS26). Supports automatic 402 → payment → retry.

2.50x

Quality

—

Does it follow best practices?

Impact

100%

2.50x

Average score across 6 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

Concise, actionable, and clearly sequenced content with executable examples and a verification step. The main weakness is progressive disclosure: two referenced bundle files are cited but not present in the skill bundle.

Suggestions

Create the missing `references/endpoints.md` and `references/signer-setup.md` files referenced in the body, or remove the references and inline the needed endpoint/signer details.

Reduce minor redundancy: the $0.01 cost, identifier D/C-suffix format, and PAYMENT-RESPONSE metadata each appear in both the main sections and the Notes — state once.

Consolidate the legacy `X-PAYMENT` fallback explanation, which is described in 'How x402 Works' step 4 and again in the `fetchBT` code, into one place.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — an endpoint table, a 5-step protocol summary, and copy-paste code, with no padding about what bonds, USDC, or EIP-3009 are; assumes Claude's competence.	3 / 3
Actionability	Provides fully executable code: concrete `npm install` commands, a complete `fetchBT` function implementing the 402 → pay → retry flow, and verified export names (`ExactEvmScheme`).	3 / 3
Workflow Clarity	The x402 flow is sequenced as five explicit steps and implemented with retry/legacy-fallback feedback loops, plus a 'Quick Test' section that validates both free and paid routes.	3 / 3
Progressive Disclosure	The body is well-sectioned and clearly signals `references/endpoints.md` and `references/signer-setup.md`, but those referenced files and the `references/` directory do not exist, so navigation does not resolve.	2 / 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, specific description with concrete actions, natural trigger terms, an explicit 'Use when…' clause, and a clear niche. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — querying the API, paying $0.01 USDC per request, and listing analytics, cashflows, history, riesgo país, and ISIN/ticker lookups — rather than vague language.	3 / 3
Completeness	Explicitly states what it does ('Query BondTerminal API using x402 keyless payments') and when to use it via an explicit 'Use when users ask for…' trigger clause.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'Argentine bond data, analytics, cashflows, history, riesgo país, or ISIN/ticker lookups (e.g. AL30, GD30, US040114HS26)' — with concrete ticker/ISIN examples.	3 / 3
Distinctiveness Conflict Risk	Targets a narrow niche (Argentine bonds via x402 keyless payments) with distinctive triggers unlikely to overlap with other skills.	3 / 3
	Total	12 / 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
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: NeverSight/skills_feed
Commit: ff6a653

Reviewed: about 17 hours 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.