Name: apaya
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

apaya

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

Quality

60%

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

Quality

Content

71%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 well-structured and actionable with executable commands and a real polling feedback loop for connection readiness; its main weaknesses are the absence of progressive disclosure via separate reference files and a sparse overview section.

Suggestions

Move the proxy-request flag table and action-discovery reference detail into a separate REFERENCE.md and link to it from the body to enable one-level-deep progressive disclosure.

Expand or remove the skeletal "Apaya Overview" section (Merchant/Payment Request/Customer) so every section carries substantive guidance.

Add a brief validation/checklist step after running an action (e.g. confirm the `output` field and expected shape before reporting success) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands and section headers; only minor explanatory prose (e.g. "so you can focus on the integration logic rather than auth plumbing") could be trimmed, fitting the "efficient; minor instances of over-explanation" anchor.	4 / 5
Actionability	Concrete, copy-paste-ready bash commands cover install, login, connection ensure/get, action list/run, and proxy requests with a clear options table; minor gaps remain (placeholders like CONNECTION_ID and omitted sample output), keeping it just below fully comprehensive.	4 / 5
Workflow Clarity	A clear sequence (install → authenticate → connect → poll to READY → search → run) is present with an explicit connection-state feedback loop (READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-poll), but there is no validation/checkpoint after running actions, a minor gap.	4 / 5
Progressive Disclosure	No bundle files exist and all content is inline in SKILL.md with reasonable section headers, but there are no one-level-deep references to split out the proxy/action reference detail, and the sparse "Apaya Overview" section shows organization gaps.	3 / 5
	Total	15 / 20 Passed

Description

48%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 has an explicit trigger clause and a distinct platform niche, but the capability statement is generic rather than concrete, which caps both specificity and completeness.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Apaya capabilities such as managing subscriptions, recurring billing, payment requests, and customer records.

Broaden the trigger phrase with natural variations, e.g. "Use when the user wants to query subscriptions, handle recurring billing, or interact with Apaya customer/payment data."

Ensure the 'what' reads as third-person concrete actions tied to Apaya entities to lift specificity above the minimal/generic anchor.

Dimension	Reasoning	Score
Specificity	Names the domain ("Apaya integration") but the actions — "Manage data, records, and automate workflows" — are generic verbs rather than concrete Apaya-specific capabilities, matching the anchor for minimal/generic actions.	2 / 5
Completeness	Both a 'what' (manage data, records, automate workflows) and an explicit 'Use when...' trigger are present, but the 'what' is vague and generic, so it does not reach the explicit/concrete level required for a 4.	3 / 5
Trigger Term Quality	"Use when the user wants to interact with Apaya data" supplies a relevant trigger phrase, but coverage is limited to one phrasing with no synonyms or natural variations, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	The named platform (Apaya) and Apaya-specific trigger ("interact with Apaya data") carve a clear niche with low overlap risk, though the generic action verbs leave minor overlap with general data-management skills.	4 / 5
	Total	12 / 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/apaya/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.