Name: safepay
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

safepay

Safepay integration. Manage data, records, and automate workflows. Use when the user wants to interact with Safepay 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/safepay/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 highly actionable with a well-validated connection workflow, but it carries unnecessary marketing/background prose and a placeholder overview section that dilute token efficiency, and its step numbering is slightly incoherent.

Suggestions

Cut the introductory marketing paragraph about what Safepay is and who uses it; Claude does not need that background to run CLI commands.

Remove or replace the placeholder 'Safepay Overview' bullets and the line 'Use action names and parameters as needed.' with concrete pointers to how actions are discovered.

Fix the step numbering so 'skip to Step 2' and '1b' refer to explicitly labeled, sequentially numbered steps in the connection setup.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands, but the opening marketing paragraph ('Safepay is a payment gateway that specializes in secure and fraud-free online transactions...') and the placeholder 'Safepay Overview' bullets plus 'Use action names and parameters as needed.' are unnecessary padding Claude does not need, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides copy-paste-ready commands for the full common path (install, login, connection ensure, connection get --wait, action list, action run, request proxy) with a flags table, covering the common cases with executable examples.	5 / 5
Workflow Clarity	The connection flow has explicit state-validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but the 'skip to Step 2' and '1b' labeling references steps that are not cleanly numbered, leaving a minor sequencing gap.	4 / 5
Progressive Disclosure	With no bundle files present, all content lives in SKILL.md under well-organized sections; the 'Searching for actions' and 'Popular actions' sections overlap and the placeholder Overview adds minor organization gaps, fitting 'good structure; minor organization gaps'.	4 / 5
	Total	16 / 20 Passed

Description

57%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 cleanly answers both what and when and anchors on the distinct Safepay niche, but its action vocabulary is generic and its trigger phrasing lacks synonyms or file-type-style variations a user might naturally say.

Suggestions

Replace generic verbs with concrete Safepay actions, e.g. 'Create and refund Safepay orders, retrieve transactions, and manage customer payment links' instead of 'Manage data, records, and automate workflows'.

Add natural trigger variations users would actually say, such as 'Use when the user mentions Safepay, Safepay payments, checkout links, refunds, or transaction records'.

Keep the explicit 'Use when...' clause but make the when-conditions enumerate the specific Safepay tasks rather than only 'interact with Safepay data'.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Safepay domain but the actions are minimal and generic rather than concrete, matching the 'Names the domain but actions are minimal or generic' anchor.	2 / 5
Completeness	It states both what ('Safepay integration. Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Safepay data'); the 'when' is explicit but could be more specific, matching the 'has both what and when; when could be more explicit' anchor rather than the fully concrete anchor 5.	4 / 5
Trigger Term Quality	It surfaces the natural keyword 'Safepay' and the trigger 'interact with Safepay data', but 'data', 'records', and 'workflows' are generic and common synonyms/variations are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific gateway 'Safepay' gives it a clear niche with minimal conflict risk, but the generic verbs ('manage data, records, automate workflows') leave minor overlap with other data-handling skills, fitting 'mostly distinct; minor overlap risk' rather than the zero-overlap anchor 5.	4 / 5
	Total	13 / 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/safepay/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.