actindo
Actindo integration. Manage data, records, and automate workflows. Use when the user wants to interact with Actindo data.
53
60%
Does it follow best practices?
Impact
—
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
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 a specific platform (Actindo) and including an explicit 'Use when' clause, which provides structural completeness. However, the actual capabilities described are extremely vague—'manage data, records, and automate workflows' could describe almost any integration tool. The description lacks concrete actions and domain-specific trigger terms that would help Claude confidently select this skill.
Suggestions
Replace vague actions with specific Actindo capabilities, e.g., 'Sync product catalogs, manage orders, update inventory levels, and automate fulfillment workflows in Actindo ERP.'
Add domain-specific trigger terms users would naturally say, such as 'ERP', 'order management', 'product information management', 'Actindo Core1', or specific entity types the skill handles.
Expand the 'Use when' clause with more specific triggers, e.g., 'Use when the user mentions Actindo, needs ERP integration, or wants to manage e-commerce orders and inventory through Actindo.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The actions listed ('manage data, records, and automate workflows') are extremely vague and generic. There are no concrete, specific actions like 'create orders', 'sync inventory', or 'update product catalogs'. These phrases could apply to virtually any integration platform. | 1 / 3 |
Completeness | The description does answer both 'what' (manage data, records, automate workflows) and 'when' ('Use when the user wants to interact with Actindo data'). While the content is vague, the structure explicitly addresses both questions with a clear 'Use when' clause. | 3 / 3 |
Trigger Term Quality | The term 'Actindo' is a strong, specific trigger keyword that users would naturally mention. However, beyond that, the terms 'data', 'records', and 'workflows' are overly generic and don't include natural variations or specific Actindo-related terms (e.g., 'ERP', 'order management', 'product information'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Actindo' provides some distinctiveness since it's a specific platform name. However, the generic terms 'manage data, records, and automate workflows' could easily overlap with other integration or workflow automation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides strong, actionable CLI-based workflows with clear sequencing and error handling for connecting to and interacting with Actindo via Membrane. However, it wastes significant tokens on explaining what Actindo is, listing 30+ entity types without context, and restating concepts Claude already knows. Trimming the introductory content and the entity list would substantially improve token efficiency.
Suggestions
Remove or drastically shorten the introductory paragraph explaining what Actindo/ERP is — Claude already knows this. A single line like 'Actindo is an e-commerce ERP platform.' suffices.
Remove the 30+ entity bullet list entirely, or replace it with a command like `membrane action list --connectionId=ID --json` to discover available entities dynamically.
Trim the best practices section to remove points that restate guidance already given in the workflow (e.g., 'Let Membrane handle credentials' is already implicit in the auth section).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what an ERP is and what Actindo does — information Claude already knows. The massive bullet list of 30+ entity types adds no actionable value. The best practices section restates things already covered. Significant token waste throughout. | 1 / 3 |
Actionability | Provides fully executable CLI commands for authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag descriptions and a useful options table. | 3 / 3 |
Workflow Clarity | The connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors) and feedback loops (poll until ready, handle client actions, re-check). The overall flow from install → auth → connect → discover → run is well-structured with branching logic. | 3 / 3 |
Progressive Disclosure | The content is reasonably structured with clear sections, but the 30+ entity bullet list is inline content that adds no value and could be removed entirely. No bundle files exist to offload detailed reference material. The skill is somewhat monolithic for its length. | 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
f484c82
- 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.