aci-payon
ACI PAY.ON integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACI PAY.ON data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill aci-payon61
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description relies heavily on the product name 'ACI PAY.ON' for identification but fails to describe what the skill actually does in concrete terms. The generic phrases 'manage data, records, and automate workflows' provide no meaningful information about payment-specific capabilities. While it includes a 'Use when' clause, the trigger condition is too vague to help Claude distinguish this from other data management skills.
Suggestions
Replace vague actions with specific payment operations like 'Process payments, handle refunds, query transaction history, manage merchant accounts'
Add natural trigger terms users would say: 'payment processing', 'transactions', 'payment gateway', 'PAY.ON API', 'merchant payments'
Expand the 'Use when' clause with specific scenarios: 'Use when processing payments, checking transaction status, or integrating with ACI PAY.ON payment gateway'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'Manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what specific operations can be performed with ACI PAY.ON (e.g., process payments, handle refunds, query transactions). | 1 / 3 |
Completeness | Has a 'Use when' clause which addresses the 'when' question, but the 'what' is extremely vague ('manage data, records, and automate workflows' could apply to almost any integration). The trigger condition 'interact with ACI PAY.ON data' is present but generic. | 2 / 3 |
Trigger Term Quality | Includes 'ACI PAY.ON' as a specific product name which is a good trigger term, but lacks natural variations users might say like 'payment processing', 'transactions', 'payment gateway', or common abbreviations. | 2 / 3 |
Distinctiveness Conflict Risk | The specific product name 'ACI PAY.ON' provides some distinctiveness, but the generic actions ('manage data, records, automate workflows') could easily overlap with other integration skills. Only the product name prevents a score of 1. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for integrating with ACI PAY.ON via Membrane, with good coverage of common operations. However, it includes unnecessary introductory explanation, lacks validation/error handling guidance in workflows, and the overview section adds little value. The best practices section is helpful but the skill would benefit from explicit verification steps.
Suggestions
Remove the introductory paragraph explaining what ACI PAY.ON is - Claude already knows this
Either expand the Overview section with actionable links/context or remove it entirely
Add validation steps after key operations (e.g., 'Verify connection succeeded: membrane connection list --json | grep CONNECTION_ID')
Include error handling guidance for common failures like authentication timeout or invalid credentials
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanation (e.g., 'ACI PAY.ON is a payment gateway that allows merchants...') that Claude already knows. The overview section listing Payment/Merchant/Transaction/Report adds little value without context. However, the CLI commands and examples are reasonably efficient. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection creation, action discovery, and proxy requests are all copy-paste ready with clear syntax and flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No guidance on verifying successful connection, handling failed authentication, or confirming action execution succeeded. The workflow is sequential but missing error recovery feedback loops. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the overview bullet list (Payment, Merchant, Transaction, Report) is unexplained and doesn't link anywhere useful. No references to external detailed documentation for advanced use cases beyond the official docs link. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Reviewed
Table of Contents
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.