agentleFS
season179season179/season-claude-plugins/n8n-workflow-builder/Skill.md

n8n-workflow-builder

Skill1 starsChanged 11 months agoNo licenceView on GitHub

Use when user asks to create, configure, or troubleshoot n8n workflows, nodes, or automation tasks. Provides current n8n documentation and node configuration guidance.

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use competitor-finder, copywriting-first-touch and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • l3mpireSkill

    competitor-finder

    Conduct competitive analysis to identify direct and indirect competitors, map their positioning, surface strengths and weaknesses, and generate differentiation angles for outbound messaging. Use when asked "who are our competitors", "competitive analysis for [company]", "how do we compare to X", "find alternatives to [product]", "competitive positioning", "battlecard", "how to beat [competitor]", "what do competitors offer", or "differentiate from X in outreach". Always use this skill before writing competitive positioning or handling competitor objections.

    Also in 3 projects that use this

  • l3mpireSkill

    copywriting-first-touch

    Writes a high-converting first touch cold email — either as a standalone message or as the opening email of a sequence. Use this skill whenever the user wants to write the first email to a cold prospect, says "write me a first email", "draft a cold email", "write my first touch", "how do I open with this prospect", or asks for a single outreach email without prior context. Works for any industry, any product, any seniority level. Always produces one polished first-touch email with subject line, body, and a sequence bridge if needed.

    Also in 3 projects that use this

  • +8 more from l3mpire

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.