aiia
Aiia integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aiia data.
58
67%
Does it follow best practices?
Impact
—
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 natural phrases users might say, such as specific Aiia features, entity types, or common use cases (e.g., 'bank payments, open banking, account information').
Add more detail to the 'Use when...' clause with specific scenarios, e.g., 'Use when the user mentions Aiia, open banking, payment initiation, or account data retrieval.'
| 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
77%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 guidance with executable CLI commands and a well-structured connection workflow with explicit state handling. However, it suffers from some unnecessary verbosity (explaining what Aiia is, what a PISP is) and a confusing 'Aiia Overview' section that lists Email/Draft/Contact without context. The content could benefit from trimming introductory explanations and better organizing reference material.
Suggestions
Remove the introductory paragraph explaining what Aiia and PISP are — Claude already knows this and can reference the linked docs if needed.
Clarify or remove the 'Aiia Overview' section listing Email/Draft/Contact — it's cryptic and provides no actionable guidance.
Consider extracting the proxy request flags table and detailed connection state documentation into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what Aiia is and what a PISP is — concepts Claude already knows or can infer. The 'Aiia Overview' section listing Email/Draft/Contact is cryptic and adds little value. Some sections like proxy request flags are useful but the overall content could be tightened. | 2 / 3 |
Actionability | The skill provides fully executable CLI commands for every step: installation, authentication, connection setup, action discovery, action execution, and proxy requests. Commands are copy-paste ready with clear flag explanations and JSON output options. | 3 / 3 |
Workflow Clarity | The multi-step connection workflow is clearly sequenced with explicit state checks (READY, BUILDING, CLIENT_ACTION_REQUIRED, errors), polling instructions, and conditional branching. The flow from install → auth → connect → discover → run is well-structured with validation at each state transition. | 3 / 3 |
Progressive Disclosure | The content is a single monolithic file with no references to supporting documents. While the structure uses headers and sections reasonably well, the proxy request table and detailed connection state documentation could be split into reference files. The 'Aiia Overview' section with Email/Contact bullets is poorly organized and unclear. | 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
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.