actindo
Actindo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actindo data.
72
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/actindo/SKILL.mdQuality
Discovery
67%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 correctly identifies the integration target (Actindo) and includes an explicit 'Use when' clause, which is good. However, the capabilities described are vague ('manage data, records, automate workflows') and could apply to almost any integration platform. The description would benefit from more specific Actindo-related actions and terminology.
Suggestions
Replace generic terms like 'manage data, records' with specific Actindo capabilities (e.g., 'manage product catalogs, process orders, sync inventory').
Add more natural trigger terms users might say, such as 'Actindo API', 'Actindo ERP', 'Actindo sync', or specific module names.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Actindo) and mentions some actions ('Manage data, records, and automate workflows'), but these are generic and not comprehensive - doesn't specify what types of data, records, or workflows. | 2 / 3 |
Completeness | Has explicit 'Use when...' clause that answers when to use it ('when the user wants to interact with Actindo data'), and describes what it does (manage data, records, automate workflows). Both components are present. | 3 / 3 |
Trigger Term Quality | Includes 'Actindo' as a key trigger term which is specific, but 'data', 'records', and 'workflows' are overly generic. Missing natural variations users might say like 'Actindo API', 'Actindo sync', or specific Actindo features. | 2 / 3 |
Distinctiveness Conflict Risk | 'Actindo' is a distinctive product name that reduces conflict risk, but 'manage data, records, and automate workflows' is generic enough to potentially overlap with other integration or automation skills. | 2 / 3 |
Total | 9 / 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 Actindo integration via Membrane, with good coverage of common operations. However, it wastes tokens on unnecessary ERP explanation and an unhelpful entity list, while lacking validation steps for connection and action workflows. The structure is adequate but could better leverage progressive disclosure.
Suggestions
Remove or drastically shorten the opening paragraph explaining what Actindo is - Claude knows what ERP systems are
Either remove the 30+ entity bullet list or replace it with a brief note that entities can be discovered via `membrane action list`
Add validation checkpoints: how to verify connection succeeded, how to confirm action ran correctly, what error responses look like
Add a troubleshooting section or link covering common failure modes (auth expired, invalid action ID, malformed input)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Actindo is wastes tokens on context Claude doesn't need. The long bullet list of 30+ entity types adds little value without explaining what actions are available for each. However, the CLI examples are reasonably concise. | 2 / 3 |
Actionability | Provides fully executable CLI commands with clear syntax for installation, authentication, connection setup, action discovery, and proxy requests. The flag reference table and JSON input examples are copy-paste ready. | 3 / 3 |
Workflow Clarity | The setup flow (install → login → connect) is clear, but lacks validation checkpoints. No guidance on verifying successful connection, handling failed auth, or confirming action execution succeeded. The 'first-time setup' vs 'existing connections' branching is helpful but could be more explicit. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the 30+ entity bullet list should either be removed or moved to a reference file. Links to official docs are provided but no internal file references for advanced topics like error handling or specific entity workflows. | 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 | |
- Repository
- membranedev/application-skills
- Commit
d19a82b
- 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.