Name: pay-with-bolt
Rating: 55.2 (1 reviews)
Author: membranedev

pay-with-bolt

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

Quality

62%

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/pay-with-bolt/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, executable commands and a well-sequenced connection workflow with state-based feedback. It loses points for some redundant prose and for inlining reference-style material rather than splitting it into bundle files with clear navigation.

Suggestions

Trim redundant prose such as re-explaining what Membrane handles and consolidating the duplicated action-list instructions into one place.

Add an explicit validation checkpoint (e.g. 'Only proceed to action run once state is READY') to close the workflow's feedback loop.

Move the verbose connection-state reference and proxy flag table into a separate references/ file, leaving SKILL.md as a concise overview with a clearly signaled link.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-pasteable commands, but includes padded prose explaining what Membrane does ('handles authentication and credentials refresh automatically'), restates the install/login flow, and duplicates the action-list command across sections.	3 / 5
Actionability	It provides fully executable, copy-paste-ready membrane CLI commands with concrete flags (--json, --connectionId, --intent, --wait) and a clear options table covering method, headers, body, and query/path params.	5 / 5
Workflow Clarity	The connection setup is a clear sequenced flow with explicit state-polling feedback (BUILDING -> READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and re-poll guidance, though it stops short of an explicit 'only proceed when READY' validation gate after the action step.	4 / 5
Progressive Disclosure	Content is organized into clear sections but there are no bundle/reference files (references/, scripts/, assets/ absent) and the only external pointer is a bare docs URL; the inlined connection-state reference and proxy options could plausibly live in separate reference files.	3 / 5
	Total	15 / 20 Passed

Description

53%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 is in correct third person and includes an explicit 'Use when' trigger, satisfying the minimum completeness bar. However, its action language is generic and it lacks concrete keywords tied to Bolt's payments/checkout domain.

Suggestions

Replace generic verbs ('manage data, records, automate workflows') with concrete Bolt capabilities such as 'fetch orders, list payment methods, and process refunds'.

Add domain-specific trigger keywords users would naturally say, e.g. 'checkout', 'payments', 'orders', or 'Pay with Bolt transactions'.

Sharpen the 'when' clause to reference specific intents (e.g. 'Use when retrieving Bolt orders or payment methods') to reduce overlap with generic data skills.

Dimension	Reasoning	Score
Specificity	It names the Pay with Bolt domain but the actions ('Manage data, records, and automate workflows') are generic verbs with no concrete capabilities like 'fetch orders', 'list transactions', or 'process refunds'.	2 / 5
Completeness	It states both what ('Pay with Bolt integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Pay with Bolt data'), though the 'when' is fairly generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural phrase 'interact with Pay with Bolt data' and a 'Use when' clause, but offers few keyword variations or synonyms a user would actually say (e.g. 'checkout', 'payments', 'orders').	3 / 5
Distinctiveness Conflict Risk	The 'Pay with Bolt' niche is somewhat distinct, but 'manage data, records, and automate workflows' is broad enough that it could overlap with other generic data-management skills.	3 / 5
	Total	12 / 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/pay-with-bolt/SKILL.md
Commit: f484c82

Reviewed: 5 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.