Name: icepay
Rating: 61.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

icepay

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

Quality

72%

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/icepay/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 a strong, command-driven integration guide with excellent actionability and a clear authenticated-connection workflow including polling checkpoints. Its main weaknesses are minor verbosity (a redundant 'Popular actions' section and a non-essential intro) and slightly loose step numbering.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands and a compact flag table, with only minor over-explanation such as the opening 'ICEPAY is a payment gateway...' sentence and the 'Popular actions' section repeating the already-shown action-list command, so it lands at efficient-with-trimmable-bits rather than a 5.	4 / 5
Actionability	It provides copy-paste-ready commands for the full path — install, login (including headless completion), connection ensure/wait, action list, action run with JSON input, and proxy requests with a complete flag table — covering the common cases with executable, concrete guidance.	5 / 5
Workflow Clarity	The install → authenticate → connect → search → run/proxy sequence is clear and includes a polling feedback loop for connection states (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but the step labels are loose — it references 'Step 2' that is never labeled and a '1b' with no explicit '1a' — which is a minor checkpoint/labeling gap.	4 / 5
Progressive Disclosure	No bundle files exist, so all guidance lives in one ~150-line file, but it is well-organized under clear section headers (Authentication, Connecting, Searching, Proxy, Best practices) making navigation easy; it stays a 4 rather than 5 because the file is over the simple-skill line and some reference-worthy detail (the proxy flag table, clientAction spec) is inlined rather than split out.	4 / 5
	Total	17 / 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 correctly pairs a 'what' with an explicit 'Use when' clause and anchors on a distinct proper noun, but its action vocabulary and trigger terms are generic. Adding concrete payment-domain actions and natural user phrases (payments, transactions) would lift specificity and trigger quality.

Suggestions

Replace generic actions with concrete ICEPAY capabilities, e.g. 'Process payments, fetch transaction records, and manage merchants via ICEPAY.'

Expand the trigger clause with natural user phrases: 'Use when the user wants to process ICEPAY payments, look up transactions, or manage merchant/report data.'

Drop the boilerplate 'Manage data, records, and automate workflows' since it adds no distinctiveness and overlaps with other Membrane skills.

Dimension	Reasoning	Score
Specificity	The description names the ICEPAY domain and lists several actions ('Manage data, records, and automate workflows'), but those actions are generic abstractions rather than concrete capabilities like 'process payments' or 'fetch transaction records', so it sits at the domain-plus-actions-but-not-comprehensive level rather than a 4.	3 / 5
Completeness	Both halves are present — the 'what' ('ICEPAY integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with ICEPAY data.') — but the trigger phrase is generic, so it matches the 'both present, when could be more specific' anchor rather than the concrete-trigger anchor at 5.	4 / 5
Trigger Term Quality	It surfaces the proper noun 'ICEPAY' and the phrase 'interact with ICEPAY data', but omits the natural terms a user would actually say for a payment gateway (payments, transactions, checkout, refunds), leaving common variations and synonyms missing.	3 / 5
Distinctiveness Conflict Risk	Tying the trigger to the unique proper noun 'ICEPAY' gives it a clear niche with low conflict risk, but the generic 'manage data, records, automate workflows' boilerplate could overlap with sibling Membrane integration skills using the same template, keeping it just below a 5.	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/icepay/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.