aiia
Aiia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aiia data.
68
61%
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/aiia/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 having an explicit 'Use when...' clause and naming the specific integration (Aiia), but it is otherwise very generic. The capabilities listed—managing data, records, and automating workflows—are vague and could describe almost any integration tool. The description would be significantly improved by listing specific Aiia capabilities and more natural trigger terms.
Suggestions
Replace vague terms like 'manage data, records, and automate workflows' with specific Aiia capabilities (e.g., 'create payment initiations, retrieve account balances, manage bank connections').
Expand trigger terms to include specific Aiia-related keywords users might naturally say, such as specific feature names, data types, or common use cases.
Add more detail to the 'Use when...' clause with specific scenarios, e.g., 'Use when the user mentions Aiia, payment initiation, bank account data, or open banking workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying any concrete actions. What kind of data? What records? What workflows? These are abstract terms that don't describe specific capabilities. | 1 / 3 |
Completeness | It does answer both 'what' (manage data, records, automate workflows) and 'when' (Use when the user wants to interact with Aiia data), with an explicit 'Use when...' clause. However, both parts are quite shallow in detail. | 3 / 3 |
Trigger Term Quality | It includes 'Aiia' as a specific product name which is a useful trigger term, and 'data', 'records', 'workflows' are somewhat relevant but generic. It lacks specific Aiia-related terminology or natural phrases users might say (e.g., specific Aiia features, API operations, or domain-specific terms). | 2 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could overlap with many integration or data management skills. The 'Aiia' brand name provides some distinctiveness, but the rest of the description could apply to dozens of different integrations. | 2 / 3 |
Total | 8 / 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.
The skill provides solid, actionable CLI commands for integrating with Aiia via Membrane, covering the full lifecycle from installation to running actions. However, it includes unnecessary explanatory content about what Aiia is, has a confusing and seemingly incomplete 'Aiia Overview' section, and could benefit from a clearer end-to-end workflow with explicit validation steps.
Suggestions
Remove the opening paragraph explaining what Aiia is — Claude already knows this, and the official docs link suffices for context.
Clarify or remove the 'Aiia Overview' section with Email/Draft/Contact bullets — it's cryptic and doesn't connect to any actionable guidance.
Add a concise numbered end-to-end workflow summary (e.g., 1. Install → 2. Auth → 3. Connect → 4. Discover actions → 5. Run/Create) with explicit validation checkpoints after key steps like connection creation and action execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explaining what Aiia is (PISP, bank accounts, etc.) is unnecessary context Claude already knows. The 'Aiia Overview' section with Email/Draft/Contact bullet points is cryptic and adds no value. Some sections are reasonably tight but there's room to trim. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connecting, searching actions, creating actions, polling, and running actions with input parameters. Commands are copy-paste ready with clear placeholder conventions. | 3 / 3 |
Workflow Clarity | The workflow steps are present and sequenced (install → auth → connect → discover → create/run), but there's no explicit validation or error-handling feedback loop for running actions. The action creation section has a good polling pattern with state checks, but the overall flow lacks a clear numbered sequence tying everything together. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with headers, but everything is inline in one file. For a skill of this length (~100 lines of substantive content), it's acceptable, but the 'Aiia Overview' section with Email/Contact bullets is poorly organized and disconnected from the rest. No references to external files for advanced topics. | 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
56d7336
- 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.