aci-payon
ACI PAY.ON integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACI PAY.ON data.
73
67%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/aci-payon/SKILL.mdQuality
Discovery
57%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 benefits from naming the specific product (ACI PAY.ON) and including an explicit 'Use when' clause, but it is severely lacking in specificity about what the skill actually does. The actions described ('manage data, records, and automate workflows') are boilerplate phrases that provide no insight into the payment-related capabilities this skill presumably offers.
Suggestions
Replace generic phrases like 'manage data, records, and automate workflows' with concrete ACI PAY.ON actions such as 'process payments, manage transactions, configure payment methods, handle refunds'.
Add natural trigger terms users would actually say, such as 'payment processing', 'payment gateway', 'transactions', 'merchant', 'checkout', or 'PAY.ON API'.
Expand the 'Use when' clause with specific scenarios like 'Use when the user mentions ACI PAY.ON, payment processing, transaction management, or needs to configure payment gateway settings'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without listing any concrete actions specific to ACI PAY.ON. These are generic phrases that could apply to virtually any integration. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with ACI PAY.ON data), with an explicit 'Use when...' clause. However, both parts are quite shallow in detail. | 3 / 3 |
Trigger Term Quality | It includes the specific product name 'ACI PAY.ON' which is a useful trigger term, but lacks natural keywords users might say such as 'payment processing', 'transactions', 'payment gateway', or other domain-specific terms related to what ACI PAY.ON actually does. | 2 / 3 |
Distinctiveness Conflict Risk | The 'ACI PAY.ON' product name provides some distinctiveness, but 'manage data, records, and automate workflows' is so generic it could overlap with many other integration skills. Without payment-specific terminology, it could conflict with other data management skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid integration skill with excellent actionability and workflow clarity — every step has concrete CLI commands and state transitions are well-documented with error handling paths. The main weaknesses are some unnecessary introductory verbosity (explaining what ACI PAY.ON is) and an underdeveloped overview section that lists categories without linking to detailed content. The 'Popular actions' section is a missed opportunity that just repeats the discovery command.
Suggestions
Remove the introductory paragraph explaining what ACI PAY.ON is — Claude already knows this, and the skill description covers it.
Either populate the 'Popular actions' section with actual common action examples (with specific actionIds and input schemas) or remove it entirely to avoid the empty placeholder.
Remove or flesh out the Overview section listing Payment/Merchant/Transaction/Report — as-is it provides no actionable information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanatory content (e.g., 'ACI PAY.ON is a payment gateway that allows merchants to accept various payment methods online') that Claude already knows. The overview section listing Payment/Merchant/Transaction/Report adds little value without further detail. However, the CLI commands themselves are reasonably lean. | 2 / 3 |
Actionability | The skill provides concrete, copy-paste-ready CLI commands for every step: installation, authentication, connection management, action discovery, action creation, and action execution. Input parameters and flags are clearly specified with examples. | 3 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced: install CLI → authenticate → ensure connection → wait for ready state → search for actions → run actions. State handling includes explicit validation checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, error states) with clear instructions for each, and polling/retry loops are well-defined. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but it's somewhat monolithic — all content is inline in a single file. The 'Popular actions' section is essentially empty (just repeats the discovery command). The overview section listing Payment/Merchant/Transaction/Report hints at structure that isn't developed or linked to separate files. | 2 / 3 |
Total | 10 / 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 | |
- Repository
- membranedev/application-skills
- Commit
88db8c5
- 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.