Name: btcpay-server
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

btcpay-server

BTCPay Server integration. Manage data, records, and automate workflows. Use when the user wants to interact with BTCPay Server data.

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/btcpay-server/SKILL.md

Quality

Content

71%Weight 40%Scale 1-5

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

The content is highly actionable with concrete CLI commands and a strong, well-validated connection workflow. It is held back by some redundant prose and an inlined action catalog that would benefit from being moved to a separate reference file for better progressive disclosure.

Suggestions

Move the popular-actions table and proxy flag reference into a dedicated reference file (e.g. ACTIONS.md) and link to it from SKILL.md, keeping only a short quick-start inline.

Trim the BTCPay Server intro paragraph and Membrane marketing phrasing to reduce tokens on concepts Claude already understands.

Add a brief verification step after destructive actions (e.g. re-list stores or get the store to confirm a delete-store succeeded) to close the workflow validation gap.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient with concrete commands, but it includes some unnecessary explanation such as the introductory paragraph on what BTCPay Server is and the Membrane marketing line ('so you can focus on the integration logic rather than auth plumbing').	3 / 5
Actionability	The body provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a concrete table of popular actions with keys and descriptions.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with explicit state handling (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-retry feedback loop, but running destructive actions like delete-store lacks an explicit verify-after step.	4 / 5
Progressive Disclosure	The skill is a single ~165-line file with well-organized headers but no external reference files; the 20-row popular-actions catalog is API-reference material inlined directly in SKILL.md rather than split out.	3 / 5
	Total	15 / 20 Passed

Description

61%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description correctly targets a clear niche and includes an explicit Use-when clause, satisfying the what/when requirement. Its main weakness is generic, non-specific action language ('Manage data, records, and automate workflows') that undersells the concrete BTCPay operations the skill supports.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete BTCPay capabilities such as 'create and manage invoices, payment requests, stores, pull payments, and webhooks'.

Broaden trigger phrases to include natural synonyms users might say, e.g. 'Use when the user wants to accept Bitcoin payments, manage invoices, or interact with BTCPay Server data.'

Dimension	Reasoning	Score
Specificity	The description names the domain ('BTCPay Server integration') but its actions ('Manage data, records, and automate workflows') are generic rather than concrete BTCPay-specific operations like invoices, stores, or payment requests.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with BTCPay Server data') are present, though the 'when' trigger is somewhat generic.	4 / 5
Trigger Term Quality	It surfaces the natural product name 'BTCPay Server' in a Use-when clause, but lacks common synonyms or related phrases (e.g. 'Bitcoin payments', 'invoices', 'payment processor') that a user might say.	3 / 5
Distinctiveness Conflict Risk	'BTCPay Server' is a distinct, named product niche with explicit triggers, giving it minimal conflict risk against other skills.	5 / 5
	Total	14 / 20 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/btcpay-server/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.