Name: n8nio
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

n8nio

N8n.io integration. Manage Workflows, Executions, Credentials. Use when the user wants to interact with N8n.io data.

Quality

65%

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/n8nio/SKILL.md

Quality

Content

57%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 action-dense with concrete Membrane CLI commands and a solid connection-state feedback loop, but it is held back by background/marketing prose, a low-value "No description" actions table, inconsistent step numbering, and a lack of destructive-action validation or external reference splitting.

Suggestions

Remove the n8n background sentence and the "focus on the integration logic rather than auth plumbing" prose, and drop or populate the Popular actions "No description" rows to cut padding.

Fix the step numbering (define Step 1a/1b and a clearly labeled Step 2) and add a validation checkpoint before destructive actions like delete-workflow (e.g., confirm the target ID and re-list to verify removal).

Move the full Popular actions / proxy flag reference into a separate reference file linked from SKILL.md so the overview stays lean.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command examples, but trimmable padding exists: the opener "N8n is a fair-code workflow automation platform. It allows developers and power users..." explains concepts Claude knows, marketing prose ("so you can focus on the integration logic rather than auth plumbing"), and a 20-row Popular actions table whose every row says "No description".	3 / 5
Actionability	Concrete copy-paste commands cover install, login, connection ensure/get with --wait, action list/run with --input, and proxy requests with a full flag table; minor gaps remain since the Popular actions table carries "No description" entries and commands rely on placeholders like CONNECTION_ID and <actionId>.	4 / 5
Workflow Clarity	The connection flow has good feedback loops (poll until state leaves BUILDING, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but step numbering is inconsistent ("skip to Step 2" and "#### 1b" with no 1a or labeled Step 2) and the destructive "Delete Workflow" action has no validation/verification step, capping this at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	The body has clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) but no bundle files and no external references; at ~160 lines with a large inline Popular actions table that would benefit from being a separate reference, it sits at anchor 3 rather than the well-split anchor 5.	3 / 5
	Total	13 / 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 names the N8n.io niche, lists the three core entity types, and includes an explicit "Use when..." trigger clause in third-person voice. It is strong on distinctiveness and trigger clarity but the action verb ("Manage") is generic and the trigger phrasing is singular rather than varied.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions, e.g. "Create, update, list, and delete Workflows, Executions, and Credentials".

Expand the trigger clause with more natural variations, e.g. "Use when the user wants to manage n8n workflows, inspect executions, or handle credentials."

Dimension	Reasoning	Score
Specificity	Quotes "Manage Workflows, Executions, Credentials" name the N8n.io domain and three concrete entity types, but a single generic verb ("Manage") applied to nouns is not multiple distinct concrete actions like extract/fill/convert, matching anchor 3 rather than the several-specific-actions anchor 4.	3 / 5
Completeness	It answers both what ("N8n.io integration. Manage Workflows, Executions, Credentials") and when ("Use when the user wants to interact with N8n.io data"); the "when" is explicit but a single general trigger rather than the multiple concrete trigger phrases of anchor 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with N8n.io data" plus the core nouns "Workflows, Executions, Credentials" give good keyword coverage a user would naturally say; not a 5 because it lacks synonym/extension variations.	4 / 5
Distinctiveness Conflict Risk	"N8n.io integration" targets a specific named platform with distinct triggers, giving a clear niche and minimal conflict risk, matching the anchor 5 example.	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/n8nio/SKILL.md
Commit: f484c82

Reviewed: 5 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.