Name: nuapay
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

nuapay

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

Quality

61%

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

Quality

Content

61%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 CLI commands and a solid connection-state feedback loop, but it loses points for a redundant action-list command, missing validation before destructive action/proxy calls, and slightly broken step numbering. Adding a verify step and de-duplicating the discovery command would notably improve it.

Suggestions

Add a validation/verification checkpoint before running actions or proxy requests (e.g. dry-run or confirm destructive operations and check the response state).

Remove the duplicate action-list command in "Popular actions" or fold it into "Searching for actions" to avoid redundancy.

Fix the step numbering: define "Step 1" and "Step 2" headers or relabel "1b" so the cross-references resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and a flags table, but the intro paragraph explains what Nuapay is and the "Popular actions" section repeats the action-list command already shown in "Searching for actions," so it could be tightened, matching score 3 over 4.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection, polling, action search/run, and proxy requests plus a flags table, with only minor placeholder gaps (CONNECTION_ID, agentType), fitting score 4 rather than a fully comprehensive 5.	4 / 5
Workflow Clarity	The connection flow has a real feedback loop (poll until READY, re-poll after client action), but running actions and proxy requests can be destructive yet lack any validation checkpoint, which caps workflow clarity at 3; the broken "Step 2" / "1b" numbering also weakens sequencing.	3 / 5
Progressive Disclosure	No bundle files exist and the single body is organized into clear headed sections with no need for external references, giving good structure; the thin "Popular actions" section and minor organization gaps keep it at 4 rather than 5.	4 / 5
	Total	14 / 20 Passed

Description

61%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 is highly distinct due to the named product, but its capability list is generic ("manage data, records") rather than concrete. Tightening the actions and adding natural payment-domain keywords would raise specificity and trigger quality.

Suggestions

Replace generic verbs with concrete Nuapay capabilities, e.g. "Manage beneficiaries, payments, and reports; automate direct debit and open banking workflows."

Add natural trigger keywords users would say, such as "payments," "direct debit," "open banking," or "Nuapay API."

Sharpen the when clause to specific intents, e.g. "Use when the user wants to query Nuapay accounts, beneficiaries, payments, or reports."

Dimension	Reasoning	Score
Specificity	The description names the Nuapay domain but the actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities, matching the score-2 anchor.	2 / 5
Completeness	Both a "what" (Nuapay integration, manage data/records/workflows) and an explicit "when" ("Use when the user wants to interact with Nuapay data") are present, though the when clause could be more specific, matching score 4 rather than 5.	4 / 5
Trigger Term Quality	"Nuapay" and "interact with Nuapay data" are relevant natural terms, but common variations or synonyms (payments, direct debit, open banking) are missing, fitting the score-3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product Nuapay with a distinct trigger ("interact with Nuapay data") gives it a clear niche with minimal conflict risk against other skills, matching the score-5 anchor.	5 / 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/nuapay/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.