Name: alumio
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

alumio

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

Quality

74%

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

75%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 content is highly actionable with copy-paste CLI commands and a clear connection-readiness feedback loop, and it is well-structured into navigable sections. Its weaknesses are conciseness (a redundant "Popular actions" section and marketing-style filler) and a broken "Step 2" reference that slightly undermines workflow sequencing.

Suggestions

Remove or merge the "Popular actions" section, which only repeats the `action list` command already shown under "Searching for actions".

Fix the broken "skip to Step 2" reference by labeling the workflow steps (Step 1 install/auth/connect, Step 2 search/run actions) or rewording to a non-numeric pointer.

Trim the marketing-style opener ("Alumio is an integration platform as a service that helps businesses connect...") to a one-line factual summary, since the rest of the skill already demonstrates what Alumio does.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes padding: the marketing-style Alumio intro paragraph ("helps businesses connect different software systems"), "This is the fastest way to get a connection", and a redundant "Popular actions" section that repeats the `action list` discovery command already shown in "Searching for actions". This matches anchor 3 (mostly efficient, some unnecessary explanation) rather than 4.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands for every stage — `npm install -g @membranehq/cli@latest`, `membrane connection ensure ... --json`, `membrane action run <actionId> --connectionId=... --input ...`, and a complete proxy options table — covering the common install/auth/connect/run/proxy cases, matching anchor 5.	5 / 5
Workflow Clarity	There is a clear Install → Auth → Connect → Search → Run → Proxy sequence, and the connection-readiness section includes an explicit state-checking feedback loop (poll until READY; after CLIENT_ACTION_REQUIRED, re-poll), matching anchor 4. It is not a 5 because the body references "skip to Step 2" with no labeled Step 2, and the action/run/proxy tail is not presented as an explicit numbered checklist.	4 / 5
Progressive Disclosure	The body is a single self-contained file with no bundle files (references/scripts/assets are empty) and well-organized section headers for easy navigation, matching anchor 4. It is not a 5 because the redundant "Popular actions" section and the bare 16-item entity list muddy the structure, and the skill exceeds the ~50-line threshold the simple-skill exception relaxes.	4 / 5
	Total	16 / 20 Passed

Description

73%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 cleanly answers both what and when around a distinct, brand-specific niche, with an explicit and natural trigger phrase. Its main weakness is specificity — the listed actions ("manage data, records", "automate workflows") are generic rather than concrete operations.

Suggestions

Replace generic verbs with concrete Alumio operations, e.g. "Manage data, records, and automate workflows" → "sync records, map fields, and automate workflows".

Broaden the "when" clause to cover the workflow-automation use case, e.g. "Use when the user wants to interact with Alumio data or automate Alumio workflows."

Add a couple of natural synonyms/variants users might say (e.g. "connect to Alumio", "sync Alumio data") to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Alumio domain plus a couple of actions, but the actions are generic rather than concrete (compare anchor 3 "Processes PDF files and extracts content"). It is above a 2 because more than one action is listed, but below a 4 because none are specific concrete operations like "sync records" or "map fields".	3 / 5
Completeness	It states a "what" ("Alumio integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Alumio data"), matching anchor 4. It is not a 5 because the "when" only covers interacting with Alumio data and omits the workflow-automation trigger implied by the "what".	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Alumio data" plus "Alumio integration" and "automate workflows" give good natural keyword coverage centered on the product name. It is below 5 because there are no synonyms or use-case variants (e.g. sync, connect), and above 3 because the trigger phrase is natural and explicit rather than jargon.	4 / 5
Distinctiveness Conflict Risk	"Alumio" is a distinct named product and the trigger "interact with Alumio data" carves a clear niche with minimal overlap risk, matching anchor 5. Despite the generic "manage data" phrasing, the brand-specific trigger keeps conflict risk low.	5 / 5
	Total	16 / 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
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

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.