agentleFS
rasulshaikhrasulshaikh/fde-desk/.claude/skills/n8n-flow-scaffold/SKILL.md

n8n-flow-scaffold

Skill0 starsChanged 48 days agoMITView on GitHub

Produce a paste-ready n8n flow outline before anyone clicks nodes for an hour. New webhook, scheduled Clay sync, enrichment fan-out, or CRM mirror that non-engineers may edit later.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write ops/<slug>/automation/n8n-<flow-slug>.md with the outline and required credentials checklist.

    line 15
  2. Distinctive:

    Only then build in the n8n UI.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: n8n-flow-scaffold

Produce a paste-ready n8n flow outline before anyone clicks nodes for an hour.

When to use

New webhook, scheduled Clay sync, enrichment fan-out, or CRM mirror that non-engineers may edit later.

Steps

  1. State the job in one sentence and the success metric (rows updated, events processed).
  2. Draw the node list in order: Trigger -> Validate -> Enrich/Call -> Branch -> Write -> Notify.
  3. For each node: input fields, credential name (not secret value), failure path.
  4. Define idempotency (dedupe key) and rate limits toward Clay or outbound tools.
  5. Write ops/<slug>/automation/n8n-<flow-slug>.md with the outline and required credentials checklist.
  6. Only then build in the n8n UI; export scrubbed JSON if the team wants it in a private repo.

Anti-patterns

  • One flow that enriches, emails, and updates CRM with no branches
  • Committing workflow JSON that still contains tokens
  • Activating send/enroll nodes without the desk send fence

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.