n8n-workflow-generator
N8N Workflow Generator - Auto-activating skill for Business Automation. Triggers on: n8n workflow generator, n8n workflow generator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
97%
0.98xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/n8n-workflow-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely thin and formulaic, reading more like auto-generated metadata than a useful skill description. It fails to describe any concrete capabilities, lacks natural trigger terms beyond the skill name repeated, and provides no explicit guidance on when Claude should select this skill. The only saving grace is that 'n8n' is a specific enough tool name to provide some distinctiveness.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates n8n workflow JSON configurations, designs node connections, sets up triggers, webhooks, and integrations between services.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about n8n workflows, automation pipelines, connecting apps, n8n nodes, or building no-code automations.'
Remove the duplicate trigger term ('n8n workflow generator' is listed twice) and expand with varied natural language terms users might actually say, such as 'automate tasks', 'n8n integration', 'workflow automation', or 'connect services'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('n8n workflow generator', 'Business Automation') but does not describe any concrete actions. There are no specific capabilities listed such as 'creates workflows', 'configures triggers', 'sets up integrations', etc. | 1 / 3 |
Completeness | The 'what' is extremely vague (just 'N8N Workflow Generator') and the 'when' is only implied through the repeated trigger phrase. There is no explicit 'Use when...' clause or meaningful description of what the skill does or when to invoke it. | 1 / 3 |
Trigger Term Quality | The only trigger term is 'n8n workflow generator' repeated twice. It misses natural variations users might say like 'n8n automation', 'workflow', 'automate', 'n8n nodes', 'n8n integration', or 'business process automation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'n8n' specifically is a fairly distinct niche that wouldn't overlap with most other skills. However, 'Business Automation' is generic enough to potentially conflict with other automation-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell—a placeholder that describes what it would do without actually doing anything. It contains no actionable instructions, no code examples, no n8n workflow JSON, and no concrete guidance for generating or configuring n8n workflows. It reads like auto-generated boilerplate with no substantive content.
Suggestions
Add concrete n8n workflow JSON examples showing at least one complete workflow (e.g., a webhook trigger → HTTP request → spreadsheet update pipeline) that Claude can adapt.
Include specific n8n node configurations, connection patterns, and common credential setup instructions rather than abstract descriptions of capabilities.
Define a clear step-by-step workflow for generating n8n workflows: gather requirements → select nodes → configure connections → validate JSON → test execution, with validation checkpoints.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching Claude how to perform the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is almost entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or configurations. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete, executable guidance. No n8n workflow JSON, no API calls, no node configurations, no commands—just vague descriptions like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow steps are defined at all. Despite claiming to provide 'step-by-step guidance,' the skill contains no steps, no sequences, and no validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of meta-descriptions with no references to detailed files, no structured navigation, and no separation of overview from detailed content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
4dee593
- 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.