sticky-note-to-workflow

Convert sticky note requirements into three-layer n8n workflow JSON.

84|23|Updated May 6, 2026
One-click install
npx skills add https://github.com/MorrisLu-Taipei/TigerAI-n8n-Skill-Pack --skill sticky-note-to-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sticky-note-to-workflow
Source: https://github.com/MorrisLu-Taipei/TigerAI-n8n-Skill-Pack/tree/main/skills/tigerai/sticky-note-to-workflow
Command: npx skills add https://github.com/MorrisLu-Taipei/TigerAI-n8n-Skill-Pack --skill sticky-note-to-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the effort of manually designing n8n workflows by converting a Layer 1 Sticky Note (DSL-formatted requirement or natural language) into an import-ready, three-layer workflow JSON.

Core Features & Use Cases

  • Sticky-note to workflow generation: Preserves the original intent (Layer 1), generates the execution plan (Layer 2), and writes AI commentary (Layer 3).
  • Natural language support via NL→DSL translation: Lets users describe what they want without writing DSL, then safely translates and confirms understanding.
  • n8n import readiness with guardrails: Enforces n8n JSON requirements (IDs, webhookId format, safe node naming), credential stub strategy for faster activation, and validations with repair on schema errors.

Quick Start

Paste your sticky note requirement (including any @trigger and @step tags, or plain text) and ask to generate the workflow, then import the returned JSON into n8n.

Frequently Asked Questions about sticky-note-to-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an n8n workflow from a sticky note or natural language request?

Yes, you can use natural language to generate n8n workflows. The system translates your plain text description into a safe DSL format, confirms the understanding, and then converts it into an import-ready n8n workflow JSON.

What is the three-layer structure used when converting DSL to an n8n workflow JSON?

The three-layer structure for n8n workflow JSON consists of Layer 1 for preserving the original sticky note intent, Layer 2 for the generated execution plan nodes, and Layer 3 for AI commentary explaining the workflow logic.

Does the generated n8n workflow JSON pass strict n8n import constraints?

Yes, the generated n8n workflow JSON satisfies strict import constraints by creating valid workflow IDs, formatting webhook node fields, applying safe node naming, and using credential stubs. It also validates via n8n-api-bridge with auto-repair for schema errors.

How do I handle credentials when building n8n workflows from text requirements?

When building n8n workflows from text requirements, credentials are handled via stubs. This strategy allows faster activation of the imported workflow JSON while ensuring the generated nodes meet n8n's strict validation requirements.