n8n-workflow-generator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill n8n-workflow-generatorN8N Workflow Generator - Auto-activating skill for Business Automation. Triggers on: n8n workflow generator, n8n workflow generator Part of the Business Automation skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped and appears to be auto-generated boilerplate. It lacks any concrete description of capabilities, has redundant trigger terms, and provides no guidance on when Claude should use this 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 app 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, building integrations, or automating business processes'
Include common variations users might say: 'n8n', 'workflow', 'automation', 'integrate apps', 'automate tasks', 'no-code automation'
| 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' clause is just a duplicate trigger term rather than meaningful guidance. There is no 'Use when...' clause explaining when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'n8n workflow generator' repeated twice. This misses natural variations users might say like 'automation', 'workflow', 'n8n', 'automate process', 'integration', or 'connect apps'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'N8N' provides some specificity to a particular automation platform, which helps distinguish it from generic automation skills. However, 'Business Automation' is vague and could overlap with many other workflow or automation tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content. It describes what a skill should do without providing any actionable guidance for n8n workflow generation. There are no code examples, no workflow patterns, no node configurations, and no concrete instructions that would help Claude assist with n8n tasks.
Suggestions
Add concrete n8n workflow JSON examples showing common patterns (e.g., webhook trigger → HTTP request → Slack notification)
Include specific node configuration examples with actual field values and connection patterns
Provide a step-by-step workflow for creating and testing n8n workflows: 1. Define trigger, 2. Add nodes, 3. Configure connections, 4. Test with sample data, 5. Activate
Reference n8n documentation or include a quick reference for common node types and their required parameters
| 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 | Contains zero concrete guidance, no code examples, no commands, no specific steps. Every section describes what the skill does abstractly rather than instructing how to do anything with n8n workflows. | 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 | No structure beyond generic headings. No references to detailed documentation, no examples file, no API reference. The content is both shallow and poorly organized with no path to deeper information. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.