agentleFS
neurawork-gitneurawork-git/n8n-autopilot/skills/inventory/SKILL.md

inventory

Skill18 starsChanged 43 days agoMITView on GitHub

Read-only inventory of local n8n workflows — aggregates node-type usage, LLM models, credentials, and trigger types into `docs/INVENTORY.md`. Use when planning new workflows, auditing instance consistency, or onboarding to an existing n8n project.

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    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:

    All work happens in scripts/aggregate.js (colocated).

    line 11
  2. Distinctive:

    Always call the bundled script.

    line 15

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

All work happens in scripts/aggregate.js (colocated). The skill body is short on purpose — read the script's --help for the full flag reference.

How to invoke

Always call the bundled script. Do not improvise grep/awk pipelines.

node "$CLAUDE_PLUGIN_ROOT/skills/inventory/scripts/aggregate.js" [flags]
FlagMeaning
(none)Aggregate everything in workflows/**/*.workflow.ts, write docs/INVENTORY.md
--json <path>Also write a machine-readable JSON twin (e.g. --json docs/inventory.json)
--dry-runPrint the markdown report to stdout, do not write files
--markdown <path>Override the markdown output path (default docs/INVENTORY.md)
--workspace <dir>Workspace root (default: current directory)

The script walks workflows/**/*.workflow.ts, extracts:

  • Node types (core n8n-nodes-base.*, community @scope/n8n-nodes-*, plain n8n-nodes-*)
  • Triggers (anything matching *Trigger, webhook, schedule, chatTrigger, formTrigger, mcpTrigger, manualTrigger, errorTrigger)
  • LLM models (literal value: 'gpt-…' / 'claude-…' / 'llama…' / 'gemini…' / 'mistral…' / 'o1…')
  • Credentials (credentials: { <type>: …)
  • Workflow names (from @workflow({ name: '…' }))

It best-effort calls npx n8nac list --json --include-archived to enrich the Summary header with remote counts; skips that section silently if n8nac is unbound or offline.

Output structure

# n8n Workflow Inventory

## Summary             — local file count + remote total/active/archived
## Trigger Distribution
## Node Usage — Core   — top 30 by count
## Node Usage — Community
## LLM Models          — provider + model + count
## Credentials         — type + count + 3 example workflow names

Companion scripts

  • scripts/aggregate.js — the only one. Self-contained Node script, no --strict --json deps, runs anywhere Node ≥ 18 does.

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.