alby-bitcoin-payments-agent-skill
Add bitcoin lightning wallet capabilities to your app using Nostr Wallet Connect (NIP-47), LNURL, and WebLN. Send and receive payments, handle payment notifications, fetch wallet balance and transaction list, do bitcoin to fiat currency conversions, query lightning addresses, conditionally settle payments (HOLD invoices), parse BOLT-11 invoices, verify payment preimages.
Install with Tessl CLI
npx tessl i github:getAlby/alby-agent-skill --skill alby-bitcoin-payments-agent-skill81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 a strong description with excellent specificity and comprehensive trigger terms covering the bitcoin lightning wallet domain. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about bitcoin payments, lightning network integration, wallet connectivity, or mentions NIP-47, LNURL, WebLN, or BOLT-11.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Send and receive payments, handle payment notifications, fetch wallet balance and transaction list, do bitcoin to fiat currency conversions, query lightning addresses, conditionally settle payments (HOLD invoices), parse BOLT-11 invoices, verify payment preimages.' | 3 / 3 |
Completeness | Clearly answers 'what does this do' with comprehensive capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'bitcoin', 'lightning wallet', 'Nostr Wallet Connect', 'NIP-47', 'LNURL', 'WebLN', 'payments', 'wallet balance', 'transaction list', 'fiat currency', 'lightning addresses', 'HOLD invoices', 'BOLT-11 invoices', 'payment preimages'. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused on bitcoin lightning wallet integration with specific protocols (NIP-47, LNURL, WebLN, BOLT-11). Unlikely to conflict with other skills due to highly specialized domain terminology. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at progressive disclosure and conciseness, serving as an effective index to detailed documentation. However, it would benefit from at least one quick-start code example showing a common operation (like sending a payment) and a clearer workflow for the typical integration path. The structure is sound but the main file is more of a table of contents than an actionable guide.
Suggestions
Add a 'Quick Start' section with a minimal executable code example showing wallet connection and a basic payment operation
Include a brief numbered workflow for the most common use case (e.g., 1. Create test wallet, 2. Connect with NWC, 3. Send payment, 4. Verify)
Add a simple code snippet demonstrating the preferred import pattern to reinforce the 'Do NOT import from dist' instruction
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides good structure and clear references to detailed documentation, but lacks any concrete code examples or executable snippets in the main file itself. Users must navigate to referenced files for actual implementation details. | 2 / 3 |
Workflow Clarity | The skill organizes capabilities into logical categories and mentions testing workflows, but lacks explicit step-by-step sequences for common tasks like setting up a wallet connection or processing a payment. No validation checkpoints are defined. | 2 / 3 |
Progressive Disclosure | Excellent use of one-level-deep references with clear signaling. The main file serves as a concise overview with well-organized links to NWC client, Lightning Tools, Bitcoin Connect, typings, and wallet documentation. | 3 / 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.
- 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.