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.
Install with Tessl CLI
npx tessl i github:NeverSight/skills_feed --skill bondterminal-x402100
Quality
100%
Does it follow best practices?
Impact
100%
2.50xAverage score across 6 eval scenarios
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 specialized niche (Argentine bond data via x402 payments), provides comprehensive trigger terms including domain-specific vocabulary ('riesgo país') and concrete examples (AL30, GD30), and explicitly states when to use it. The description is concise yet thorough, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Query BondTerminal API', 'pay $0.01 USDC per request', 'automatic 402 → payment → retry'. Specifies the domain (Argentine bond data) and technical details (Base mainnet, x402 keyless payments). | 3 / 3 |
Completeness | Clearly answers both what (query BondTerminal API with x402 payments) and when (explicit 'Use when users ask for...' clause with comprehensive trigger scenarios including bond data, analytics, and specific ticker examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Argentine bond data', 'analytics', 'cashflows', 'history', 'riesgo país', 'ISIN/ticker lookups', and specific examples like 'AL30, GD30, US040114HS26'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche combining Argentine bonds, x402 payments, and specific tickers (AL30, GD30). Very unlikely to conflict with other skills due to the specialized domain and payment mechanism. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that efficiently teaches Claude how to interact with the BondTerminal API using x402 payments. It provides complete, executable code examples, clear workflow steps, and appropriate progressive disclosure through external references. The content respects Claude's intelligence while providing all necessary implementation details.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what APIs are or how HTTP works). Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable JavaScript code with proper imports, complete function implementations, and copy-paste ready examples. The setup steps are concrete with specific npm packages and code snippets. | 3 / 3 |
Workflow Clarity | The x402 flow is clearly sequenced (1-5 steps), setup has numbered steps, and the code includes error handling with a fallback mechanism for legacy headers. The quick test section provides validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate use of tables for endpoint reference, and explicit references to external files (references/endpoints.md, references/signer-setup.md) for detailed content. Links to full docs provided. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.