Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

alumio

Alumio integration. Manage data, records, and automate workflows. Use when the user wants to interact with Alumio data.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/alumio/SKILL.md

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers strong, executable CLI guidance with genuine validation checkpoints for connection state handling. Its main defects are padding in the marketing-style intro, a duplicated action-discovery section, and a workflow that references a nonexistent "Step 2", which breaks the otherwise solid sequence.

Suggestions

Fix the broken workflow numbering: either label the subsequent sections (Step 1a/1b, Step 2: search actions, Step 3: run actions) or remove the "skip to Step 2" and "1b" references.

Trim the opening paragraph to one line (drop who uses Alumio and the product menu listing) and merge "Popular actions" into "Searching for actions" to remove the duplicated command.

Standardize on one CLI invocation ("membrane" vs "npx @membranehq/cli@latest") and consider moving the proxy flags table and clientAction state reference into a reference file to slim the main body.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands, but the opening paragraph explaining who uses Alumio ("It's used by e-commerce companies, retailers, and other organizations...") and the product menu listing are unnecessary padding, and the action-list command appears twice ("Searching for actions" and "Popular actions").	3 / 5
Actionability	Concrete, mostly copy-paste-ready commands throughout (install, login, connection ensure, --wait polling, action run --input, proxy request with a flags table), held back from 5 by minor gaps: inconsistent CLI invocation ("membrane" vs "npx @membranehq/cli") and unresolved QUERY/CONNECTION_ID placeholders without a worked example.	4 / 5
Workflow Clarity	The connection flow has real validation checkpoints (state polling, clientAction handling, error states), but the sequence is broken by dangling references: "skip to Step 2" and a "#### 1b" heading exist with no Step 2 or 1a anywhere in the document, making the multi-step process incoherent.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inline, but the skill is well-organized with clear section headers and most content is appropriately placed; the proxy flags table and clientAction reference could arguably move to a reference file, keeping it at anchor 4 rather than 5.	4 / 5
	Total	14 / 20 Passed

Description

52%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 safely distinctive thanks to the Alumio brand name and includes a "Use when" clause, but it fails to convey what the skill concretely does. Its actions are generic buzz phrasing and its trigger guidance is circular, so a user mentioning related concepts (iPaaS, app integration, ERP sync) would not naturally surface this skill.

Suggestions

Replace the generic action list with concrete Alumio capabilities, e.g., "Manage Alumio entities: data schemas, mappings, attributes, incoming/outgoing queues, tasks, cronjobs, and access tokens."

Expand the "Use when" clause with natural trigger phrases users would actually say, e.g., "Use when the user mentions Alumio, iPaaS, syncing data between ERP/CRM/webshops, or wants to inspect Alumio entities or records."

Avoid the circular "interact with Alumio data" phrasing — state the specific interactions (list, search, create, update records) so the "what" answers itself without restating the domain.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Alumio domain but the actions are entirely generic, with no concrete operations (e.g., create data schemas, run mappings, monitor queues) that would lift it to anchor 3's "1-2 concrete actions".	2 / 5
Completeness	Both a "what" and an explicit "Use when the user wants to interact with Alumio data" clause are present, but the "what" is vague and the "when" is circular (restating "Alumio integration"), placing it between anchors 3 and 4, closer to 3.	3 / 5
Trigger Term Quality	The only distinctive keyword is "Alumio" itself; supporting terms ("data", "records", "workflows", "integration") are generic, and natural synonyms users might say (iPaaS, connect ERP/CRM, sync data between apps) are absent — matching anchor 3 but not anchor 4's good coverage.	3 / 5
Distinctiveness Conflict Risk	"Alumio" is a clear niche product name serving as a distinct trigger; there is virtually no overlap risk with other skills, matching anchor 5.	5 / 5
	Total	13 / 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/alumio/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.

alumio

Table of Contents

Is this your skill?