Name: bridgepay-network-solutions
Rating: 64.8 (1 reviews)
Author: membranedev

bridgepay-network-solutions

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

Quality

78%

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/bridgepay-network-solutions/SKILL.md

Quality

Content

82%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 highly actionable with executable CLI commands and a strong connection-state validation loop, organized into clear sections. Minor conciseness padding and a couple of navigation gaps (dangling Step 2 reference) keep it just short of top marks.

Suggestions

Define and label "Step 2" explicitly (or remove the "skip to Step 2" / "1b" cross-references) so the workflow sequence is unambiguous.

Trim the introductory "is a payment gateway that facilitates..." paragraph and the auth-plumbing marketing line to save tokens.

Consider moving the proxy flags table and "Popular actions" detail into a reference file to keep SKILL.md a leaner overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with copy-paste CLI commands, but includes minor padding (the "is a payment gateway that facilitates..." intro, "Use action names and parameters as needed", and the auth-plumbing marketing line); below 5 because these could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready CLI commands (install, login, connection ensure, action list/run, request) plus a comprehensive flags table cover the common cases.	5 / 5
Workflow Clarity	Clear sequence from install through action execution with an explicit validation/polling loop for connection states (BUILDING/READY/CLIENT_ACTION_REQUIRED); below 5 because of the dangling "skip to Step 2" reference with no labeled Step 2 and the orphaned "1b" numbering.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no nested references; all content is inline in a single file with no external bundle files, which is acceptable since none are needed, but at ~157 lines some detail could be split out.	4 / 5
	Total	17 / 20 Passed

Description

73%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 clearly identifies the niche and provides an explicit "Use when" trigger, but its capability verbs ("manage data, records, automate workflows") are generic rather than concrete. Strong on distinctiveness, moderate on specificity.

Suggestions

Replace generic verbs with concrete actions, e.g. "query transactions, manage merchants and terminals, run reports".

Add natural synonyms or aliases users might say (e.g. "BridgePay", "payment gateway") to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the BridgePay domain and a few actions ("Manage data, records, and automate workflows"), but the verbs are generic rather than concrete like "extracts content"; below 4 because actions lack specificity.	3 / 5
Completeness	Explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with BridgePay Network Solutions data"); below 5 because the "what" is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"BridgePay Network Solutions" is exactly the phrase a user would naturally say, giving good keyword coverage for a single-vendor skill; below 5 because there are no synonyms or extensions.	4 / 5
Distinctiveness Conflict Risk	Targets a specific branded integration ("BridgePay Network Solutions") with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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/bridgepay-network-solutions/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.