Tessl • The management layer for AI agent skills

The body is a genuinely usable CLI integration guide with executable commands, a sensible install-to-run sequence, and good state-machine handling for connection readiness. Its main flaws are leftover placeholder content ('Aiia Overview', an empty 'Popular actions' section), duplicated discovery instructions, and broken step references ('Step 2', '1b'). No bundle files exist, so everything is inline, which is workable at this size but leaves no room for API detail to grow.

Suggestions

Delete the placeholder 'Aiia Overview' block ('Email/Draft/Contact' and 'Use action names and parameters as needed') — it is dead weight and confusing.

Populate 'Popular actions' with 3-5 concrete Aiia action examples (e.g. initiate payment, list accounts, get transactions) instead of repeating the discovery command, and merge it with 'Searching for actions' to remove the duplication.

Fix the step numbering: either label the later sections 'Step 2', 'Step 3', ... and rename '1b' to match a '1a', or drop the numbered-step references and use plain section names.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command-focused text, but the 'Aiia Overview' block ('Email', 'Draft', 'Contact', 'Use action names and parameters as needed') is pure placeholder padding, and 'Searching for actions' and 'Popular actions' duplicate the same discovery command with slightly different invocations. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened'.	3 / 5
Actionability	Concrete, executable commands appear throughout — 'membrane connection ensure "https://www.aiia.eu/" --json', the '--wait' polling command, 'membrane action run ... --input ... --json', and a full proxy flag table. Minor gaps keep it below 5: the 'Popular actions' section never lists an actual action, and the placeholder overview block provides nothing runnable.	4 / 5
Workflow Clarity	There is a clear sequence (install → login → connection ensure → poll for READY → handle CLIENT_ACTION_REQUIRED → search/run actions → proxy fallback) with state-based checkpoints and a re-poll feedback loop. Minor gaps: 'skip to Step 2' references a step that is never labeled, and '#### 1b.' appears with no '1a' or 'Step 2' counterpart, slightly muddying navigation.	4 / 5
Progressive Disclosure	The single file is well-sectioned with descriptive headers, but at ~140 lines there are no references or deeper navigation at all, and organization defects remain — the dead 'Aiia Overview' placeholder section and inconsistent step numbering. This matches 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	14 / 20 Passed

Description

50%Weight 40%Scale 1-5

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 is short and names its niche explicitly, which keeps conflict risk low, but it says almost nothing concrete about what Aiia does. The 'when' clause is present yet circular (it triggers only on the product name), and the action list is generic filler. Concrete capabilities (payment initiation, bank account/financial data access) and natural trigger phrases would materially improve it.

Suggestions

Replace the generic action list with concrete Aiia capabilities, e.g. 'Initiate account-to-account payments and access bank account and transaction data via Aiia's API'.

Add natural trigger terms users would actually say — 'bank payments', 'open banking', 'PISP', 'financial data', 'payment initiation' — to the 'Use when' clause.

Mention that interaction happens through the Membrane CLI/connection layer so users searching for 'Membrane' or 'Aiia connection' also find this skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Aiia integration') but the actions are pure generic verbs: 'Manage data, records, and automate workflows'. No concrete Aiia capability (payments, bank account access, financial data) is stated, matching the 'names the domain but actions are minimal or generic' anchor rather than any anchor with concrete actions.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Aiia data') are present, but the 'when' is generic and the 'what' is vague — matching 'has both what and when; when could be more explicit or specific'. Not 3 because the 'when' is explicitly stated rather than missing or merely implied.	4 / 5
Trigger Term Quality	The only meaningful keyword is the product name 'Aiia'; 'data', 'records', and 'workflows' are generic. It lacks the natural phrases a user would actually say (e.g. 'bank payments', 'open banking', 'account-to-account', 'financial data'), matching the 'one or two generic keywords; missing the natural phrases users say' anchor.	2 / 5
Distinctiveness Conflict Risk	The product name 'Aiia' carves out a clear niche with distinct triggers and minimal conflict risk, but the boilerplate 'Manage data, records, and automate workflows' phrasing overlaps with countless generic integration skills — matching 'mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	12 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/aiia/SKILL.md
Revision: f484c82

Reviewed: 16 days ago

Discovery Implementation Validation

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.

aiia

Table of Contents

Is this your skill?