Name: shieldpay
Rating: 59.2 (1 reviews)
Author: membranedev

shieldpay

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

Quality

68%

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/shieldpay/SKILL.md

Quality

Content

75%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 body is an efficient, actionable guide with a well-sequenced connection workflow and validation feedback loops. Main improvements are normalizing the CLI invocation, fixing step numbering, and moving the verbose clientAction-state detail into a reference file.

Suggestions

Normalize CLI invocation: pick either 'membrane' or 'npx @membranehq/cli@latest' consistently across all examples to avoid confusion.

Fix the step numbering so 'Step 1' and 'Step 2' are explicitly labeled rather than jumping to '1b' and referencing an unlabeled 'Step 2'.

Consider moving the detailed clientAction state handling and proxy flag table into a reference file, leaving SKILL.md as a tighter overview with a one-level-deep pointer.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with concrete commands and flags, with only minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' that could be trimmed.	4 / 5
Actionability	It provides concrete, copy-paste-ready commands (install, login, connection ensure, action list/run, proxy) with a detailed flag table; minor gaps come from inconsistent 'membrane' vs 'npx @membranehq/cli' invocation and unresolved placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	A clear install→authenticate→connect→poll→search/run sequence with validation checkpoints (poll until READY, inspect clientAction/error) and a feedback loop (re-poll after user action); step numbering is slightly confusing ('1b' and a referenced 'Step 2' without a labeled Step 1).	4 / 5
Progressive Disclosure	Content is organized into clear, well-labeled sections with no nested references; with no bundle files present everything is inline, and at ~140 lines it sits just outside the simple-skill exception that would allow a 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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 covers the essentials with an explicit trigger clause and a distinct named platform, but its action language and trigger terms are generic. Tightening the 'what' and adding natural user synonyms would raise it.

Suggestions

Replace generic verbs with concrete Shieldpay-specific actions (e.g., 'create and track transactions, manage counterparties, release held funds').

Add natural trigger terms users actually say, such as 'payments', 'transactions', 'escrow', or 'held funds', not just 'Shieldpay data'.

Make the 'Use when' clause more specific, e.g., 'Use when the user wants to create or track Shieldpay transactions, manage counterparties, or release held funds.'

Dimension	Reasoning	Score
Specificity	Names the Shieldpay domain and a few action phrases ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete and comprehensive.	3 / 5
Completeness	It answers both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with Shieldpay data'), though the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	The core term 'Shieldpay' and 'Shieldpay data' appear, but natural synonyms a user might say (payments, transactions, escrow, funds) are missing.	3 / 5
Distinctiveness Conflict Risk	The named Shieldpay platform gives it a clear niche with minimal conflict risk, but the generic action verbs leave minor overlap with other data-management skills.	4 / 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/shieldpay/SKILL.md
Commit: f484c82

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