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
Quality
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 severely underdeveloped, appearing to be auto-generated boilerplate rather than a thoughtful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The only distinguishing element is the 'n8n' platform name.
Suggestions
Add specific actions the skill performs, e.g., 'Creates n8n workflow JSON files, designs automation sequences, connects API integrations, and generates node configurations'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about n8n, workflow automation, connecting apps, API integrations, or building automated pipelines'
Remove the duplicate trigger term and expand with variations users might actually say: 'n8n', 'workflow', 'automate', 'integration', 'connect services'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only says 'N8N Workflow Generator' and 'Business Automation' without describing any concrete actions. It doesn't explain what the skill actually does - no verbs describing capabilities like 'creates workflows', 'connects integrations', or 'automates tasks'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a duplicate trigger phrase. There's no explicit 'Use when...' clause or meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The 'Triggers on' field redundantly lists 'n8n workflow generator' twice, providing no variation. Missing natural terms users might say like 'automation', 'workflow', 'integrate', 'connect apps', 'automate tasks', or 'n8n'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'n8n' provides some specificity that distinguishes it from generic automation skills, but 'Business Automation' is very broad and could overlap with many 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 essentially an empty placeholder that provides no actual value. It describes what it claims to do without providing any concrete guidance, code examples, workflow patterns, or actionable instructions for n8n workflow generation. The entire content could be replaced with a single sentence and lose nothing of substance.
Suggestions
Add concrete, executable n8n workflow JSON examples showing common patterns (e.g., webhook triggers, HTTP requests, data transformations)
Include step-by-step workflow creation instructions with specific node configurations and connection patterns
Provide actual code snippets for n8n expressions, JavaScript code nodes, and common integrations
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual n8n workflows. The content only describes what the skill claims to do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are provided whatsoever. Despite claiming to provide 'step-by-step guidance,' the skill contains no actual steps, sequences, or validation checkpoints for creating n8n workflows. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization that would help Claude navigate to useful information. | 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
0c08951
- 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.