agentleFS
alanalvestechalanalvestech/hitank/skills/n8n/SKILL.md

n8n

Skill38 starsChanged 8 months agoMITView on GitHub

Manage n8n workflows, executions and credentials via REST API

  • Reads credentials

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use albert-dm, new-client-system and 10 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.
  • yawningwhaleAISkill

    albert-dm

    Reply to DMs and messages the way Albert would. Use when the user asks "how would Albert reply to this", pastes a conversation and wants an Albert-style response, or asks you to draft/write a DM in Albert's voice. Albert sells AI voice agents / automations to local service businesses (Go High Level, lead follow-up, bookings).

    Also in 5 projects that use this

  • yawningwhaleAISkill

    new-client-system

    Scaffold a new client's full stack — Next.js 16 frontend dashboard + Trigger.dev backend worker — from the Shiney automations template. Use when the user says "new client", "onboard a client", "scaffold a client system", "set up <client-name>", or wants to start a fresh frontend+backend project styled and structured like the Shiney automations dashboard. Produces structure only; no automations are scaffolded — those are added later.

    Also in 6 projects that use this

  • xfstudioSkill

    trigger-dev

    Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.

    Also in 12 projects that use this

  • huyvpSkill

    cost-reducer

    Reduce cloud, infrastructure, and operational costs while maintaining performance. Use when writing database queries, configuring cloud resources, optimizing bundles, setting up caching, choosing between services, sizing instances, configuring CDN, managing storage, or reviewing code for cost inefficiencies. Covers AWS/GCP/Vercel pricing, database optimization, serverless tuning, image pipelines, observability costs, and FinOps practices.

    Also in 10 projects that use this

  • ffsshhttiikkSkill

    scalability

    Core foundational concepts and principles for Scalability

    Also in 10 projects that use this

  • RoxenRobloxSkill

    youtube-broll-maker

    Generate 10-second B-roll footage of yourself doing an action using the Higgsfield MCP (Seedance 2.0). Upload one photo of yourself, describe the action ("typing on laptop", "walking at night"), pick from 5 cinematography style presets, get an MP4. Use when the user wants B-roll, cutaway footage, "me doing X" video, YouTube B-roll, or any image-to-video of themselves performing an action.

    Also in 3 projects that use this

  • +4 more from yawningwhaleAI

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If the output is OK, proceed to the Flow section.

    line 34
  2. Very specific:

    If the output is SETUP_NEEDED, guide the user step by step.

    line 36
  3. Distinctive:

    If the script outputs an error, the API key or host is invalid.

    line 63

“Common” is measured: kept by at least 6 in 10 of the 21 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.

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

/n8n

Connect to the n8n REST API to manage workflows, executions and credentials. Works with self-hosted n8n instances and n8n Cloud. Pure Ruby, zero gems — stdlib only.

Structure

scripts/
├── auth.rb          # API key auth via X-N8N-API-KEY header + n8n_request helper (required by all scripts)
├── check_setup.rb   # Check if API key and host are configured (outputs OK or SETUP_NEEDED)
├── save_token.rb    # Save and validate API key + host URL
├── workflows.rb     # List all workflows
├── workflow.rb      # Get workflow details
├── activate.rb      # Activate a workflow
├── deactivate.rb    # Deactivate a workflow
├── executions.rb    # List executions (with optional filters)
├── execution.rb     # Get execution details
└── credentials.rb   # List credentials (no secrets shown)

Setup (check before using)

ruby ~/.claude/skills/n8n/scripts/check_setup.rb

If the output is OK, proceed to the Flow section.

If the output is SETUP_NEEDED, guide the user step by step. Present ONE step at a time, wait for the user to confirm before moving to the next.

Step 1 — Ask the user for their n8n host URL:

What is the URL of your n8n instance?

  • Self-hosted: typically http://localhost:5678
  • n8n Cloud: https://your-instance.app.n8n.cloud

Paste the base URL here (no trailing slash).

Step 2 — Ask the user to create an API key:

You need an n8n API key. Go to your n8n instance:

  1. Open Settings → API (or navigate to <your-host>/settings/api)
  2. Click Create an API key
  3. Copy the key and paste it here

If you don't see the API section, make sure the REST API is enabled in your n8n environment variables (N8N_PUBLIC_API_ENABLED=true).

Step 3 — When the user provides both values, save them:

ruby ~/.claude/skills/n8n/scripts/save_token.rb 'API_KEY' 'HOST_URL'

If the script outputs an error, the API key or host is invalid. Ask the user to double-check and try again.

If setup is not complete, DO NOT proceed to the Flow. Complete all steps first.

Flow

The argument $ARGUMENTS may contain a workflow ID.

Step 1: List workflows

ruby ~/.claude/skills/n8n/scripts/workflows.rb

Present the workflows to the user. If $ARGUMENTS matches a workflow ID, use that workflow. Otherwise ask which workflow to work with.

Step 2: Show workflow details

ruby ~/.claude/skills/n8n/scripts/workflow.rb WORKFLOW_ID

Present the workflow info (name, active status, nodes, connections) and ask what the user wants to do.

Step 3: Actions

Activate a workflow (requires user confirmation):

Show the workflow name and current status first, then ask: "Do you want to activate this workflow?" Only execute after a "yes".

ruby ~/.claude/skills/n8n/scripts/activate.rb WORKFLOW_ID

Deactivate a workflow (requires user confirmation):

Show the workflow name and current status first, then ask: "Do you want to deactivate this workflow?" Only execute after a "yes".

ruby ~/.claude/skills/n8n/scripts/deactivate.rb WORKFLOW_ID

List executions:

ruby ~/.claude/skills/n8n/scripts/executions.rb
ruby ~/.claude/skills/n8n/scripts/executions.rb --workflowId WORKFLOW_ID
ruby ~/.claude/skills/n8n/scripts/executions.rb --status error
ruby ~/.claude/skills/n8n/scripts/executions.rb --workflowId WORKFLOW_ID --status success

Get execution details:

ruby ~/.claude/skills/n8n/scripts/execution.rb EXECUTION_ID

List credentials (no secrets shown):

ruby ~/.claude/skills/n8n/scripts/credentials.rb

Notes

  • Pure Ruby, zero gems — stdlib only (json, net/http, uri, fileutils)
  • Auth via X-N8N-API-KEY header
  • Config files: ~/.config/n8n/api_key and ~/.config/n8n/host (outside the repo, never commit)
  • n8n can be self-hosted — the host URL is fully configurable (default: http://localhost:5678)
  • Activating and deactivating workflows require explicit user confirmation
  • The credentials endpoint only lists credential names and types — secrets are never exposed

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.