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.
97
92%
Does it follow best practices?
Impact
100%
2.50xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that clearly defines a narrow, specific domain (Argentine bond data via BondTerminal API), provides rich trigger terms including both Spanish ('riesgo país') and English terms plus specific ticker examples, and explicitly states both what it does and when to use it. The description is concise yet comprehensive, with no fluff or vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: query BondTerminal API, pay $0.01 USDC per request, handle 402 → payment → retry cycle. Also specifies the domain (Argentine bond data) and specific capabilities (analytics, cashflows, history, riesgo país, ISIN/ticker lookups). | 3 / 3 |
Completeness | Clearly answers both 'what' (query BondTerminal API using x402 keyless payments, supports automatic 402 → payment → retry) and 'when' (explicit 'Use when users ask for Argentine bond data, analytics, cashflows, history, riesgo país, or ISIN/ticker lookups'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'Argentine bond data', 'analytics', 'cashflows', 'history', 'riesgo país', 'ISIN', 'ticker', and specific examples like 'AL30', 'GD30', 'US040114HS26'. Also includes technical terms like 'x402', 'BondTerminal' for more advanced users. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Argentine bonds via BondTerminal API with x402 payments on Base mainnet. Very unlikely to conflict with other skills given the specific domain (Argentine bonds), specific API (BondTerminal), and specific payment mechanism (x402/USDC). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that provides actionable, executable guidance for querying the BondTerminal API via x402 payments. The workflow is clearly sequenced with validation steps, and progressive disclosure is handled well with appropriate references to external files. Minor verbosity in explaining x402 mechanics and wallet requirements could be trimmed, but overall the content is strong and practical.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., the full description of how x402 works step-by-step is arguably something that could be shorter since the code already demonstrates it). The wallet requirements section restating 'no ETH for gas' and explaining EIP-3009 adds minor bloat. | 2 / 3 |
Actionability | Provides fully executable JavaScript code for the complete x402 payment flow, concrete install commands, specific endpoint table with methods and paths, and real example calls with actual tickers. The fetchBT function is copy-paste ready and handles the 402 → payment → retry cycle. | 3 / 3 |
Workflow Clarity | The multi-step process is clearly sequenced: install → configure signer → register client → fetch data. The x402 flow itself has explicit steps (call → get 402 → decode → sign → retry with v2 header → legacy fallback). The quick test section provides a validation checkpoint for both free and paid routes. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from overview to setup to usage. References external files appropriately (references/endpoints.md, references/signer-setup.md) at one level deep with clear signaling. Links to full external docs at bondterminal.com/developers without burying content in nested references. | 3 / 3 |
Total | 11 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.