Name: proabono
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

proabono

ProAbono integration. Manage Users, Organizations. Use when the user wants to interact with ProAbono data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/proabono/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 copy-paste-ready Membrane CLI commands and a well-validated connection workflow, but it opens with unnecessary background on ProAbono and has a minor structural inconsistency in its step labeling.

Suggestions

Trim the introductory paragraph explaining what ProAbono is and who uses it; assume Claude knows subscription billing.

Fix the 'skip to Step 2' reference by explicitly labeling the Searching/Running actions sections as Step 2.

Add a brief validation note for action results (e.g. check the output/error fields before proceeding) to close the workflow gap.

Dimension	Reasoning	Score
Conciseness	The bulk is lean command reference, but the opening paragraph ('ProAbono is a subscription management and recurring billing platform. It helps businesses automate invoicing, payment collection, and customer management...') and the overview list explain what ProAbono is and who uses it, which Claude already knows, matching the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	Commands are copy-paste ready and cover the common cases (install, login incl. headless, connection ensure, wait-for-ready, action list/run, proxy with a full flags table), with placeholders clearly marked, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow has explicit validation checkpoints and feedback loops (poll --wait, state-based READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR branching, re-poll after user action), but the body references a 'Step 2' that is not clearly labeled and the action-running section lacks result validation, capping it below 5.	4 / 5
Progressive Disclosure	The single file is well-organized with clear section headers and no nested references, and no bundle files exist to require splitting; it sits at the good-structure anchor rather than 5 which expects well-signaled one-level-deep references and content split across files.	4 / 5
	Total	16 / 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 answers both what and when and is anchored to a specific named platform, but its action verbs are generic and its trigger terms miss the core billing/subscription vocabulary users would naturally say.

Suggestions

Replace the generic 'Manage' with concrete actions, e.g. 'Create and list Users, manage Organizations and Subscriptions'.

Expand the 'Use when' clause with natural trigger terms like subscriptions, billing, invoices, and customers.

Add file-format or entity synonyms (e.g. 'subscriptions', 'recurring billing') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('ProAbono integration') and two target entities ('Manage Users, Organizations'), but 'Manage' is a generic verb rather than concrete actions like create/list/update, matching the anchor that lists domain and 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both 'what' ('ProAbono integration. Manage Users, Organizations.') and 'when' ('Use when the user wants to interact with ProAbono data.') are present, but the 'when' clause is generic rather than listing concrete trigger phrases, so it does not reach the explicit-concrete anchor of 5.	4 / 5
Trigger Term Quality	Contains 'ProAbono', 'Users', and 'Organizations' but misses the natural terms users would say for a billing platform (subscriptions, billing, invoices, customers), fitting the anchor with some relevant keywords but missing common variations.	3 / 5
Distinctiveness Conflict Risk	The named platform 'ProAbono' gives it a clear niche with minimal conflict risk, though the generic 'interact with ProAbono data' trigger leaves minor overlap potential with other subscription/billing skills.	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/proabono/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.