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.
95
88%
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 explicit trigger guidance with natural user terms, and includes distinctive identifiers that minimize conflict risk. The description is concise yet comprehensive, covering the what, when, and how without unnecessary verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: query API, pay per request via x402, look up bond data/analytics/cashflows/history, ISIN/ticker lookups, and automatic 402 payment retry. Very specific about the mechanism and data types. | 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'. These are terms a user working with Argentine bonds would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Argentine bond data via a specific API (BondTerminal) with a specific payment mechanism (x402/USDC on Base). Very unlikely to conflict with other skills given the narrow domain and specific triggers like 'riesgo país', 'AL30', 'GD30'. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with clear executable code and a well-structured workflow for the x402 payment flow. The API endpoint table and fetchBT helper function are immediately usable. Minor weaknesses include some unnecessary protocol explanation that Claude could infer, and referenced bundle files (signer-setup.md, endpoints.md) are not provided, making progressive disclosure harder to fully evaluate.
Suggestions
Trim the 'How x402 Works' section to 2-3 lines or move it to a reference file — the fetchBT code already demonstrates the flow concretely.
Provide the referenced bundle files (references/signer-setup.md, references/endpoints.md) so the progressive disclosure structure is complete and verifiable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary explanation (e.g., the 'How x402 Works' section explains protocol internals Claude could infer from the code, and the wallet requirements section restates what's already implied). The API table and code examples are well-structured, but the overall content could be tightened by ~20%. | 2 / 3 |
Actionability | Provides fully executable JavaScript code for the complete x402 payment flow including install commands, client setup, the fetchBT helper with 402 handling and legacy fallback, and concrete usage examples. The API endpoint table with specific paths, methods, and identifier formats is immediately usable. | 3 / 3 |
Workflow Clarity | The multi-step x402 flow is clearly sequenced: install → configure signer → register client → fetch with automatic 402 → payment → retry. The fetchBT function embeds the validation/retry loop (check 402, create payment, retry with v2 header, fallback to legacy header, throw on failure). The quick test section provides explicit verification of both free and paid paths. | 3 / 3 |
Progressive Disclosure | References to `references/endpoints.md` and `references/signer-setup.md` are well-signaled, and external docs are linked. However, no bundle files were provided, so these references are unverifiable. The main content includes some detail (like the full x402 protocol explanation) that could be offloaded to a reference file, and the signer setup is split awkwardly between inline guidance and a missing reference file. | 2 / 3 |
Total | 10 / 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
aa009ea
- 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.