pull-schemas
Skill18 starsChanged 43 days agoMITView on GitHub
Pull/update n8n node schemas for offline validation. Discovers node types from local workflows, fetches each via `npx n8nac skills node-info`, falls back to direct npm-package extraction for nodes n8nac does not index, then rebuilds `schemas/_index.json`. Run when schemas are stale, when validation reports "unknown node type", or when SessionStart hooks signal coverage gaps.
- Reads credentials
In this repository25 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-stack-v2Skill
- build-workflowSkill
- build-workflow-v2Skill
- check-mcpsSkill
- data-tablesSkill
- deploySkill
- feedbackSkill
- find-credentialSkill
- find-projectSkill
- init-repoSkill
- inventorySkill
- mirror-syncSkill
- n8nac-cheatsheetSkill
- n8nac-referenceSkill
- n8n-code-javascriptSkill
- n8n-code-pythonSkill
- n8n-modeSkill
- n8n-orchestration-patternsSkill
- n8n-structured-extractionSkill
- plugin-testingSkill
- session-envSkill
- stack-intakeSkill
- sync-credentialsSkill
- test-manualSkill
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
- Very specific: line 11
All work happens in scripts/run.sh (colocated in this skill).
- Distinctive: line 15
Always call the bundled orchestrator.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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.
Files
Pull Node Schemas
All work happens in scripts/run.sh (colocated in this skill). The skill body is short on purpose — read the script's --help for the full flag reference.
How to invoke
Always call the bundled orchestrator. Do not write ad-hoc loops or improvise around the CLI calls.
bash "$CLAUDE_PLUGIN_ROOT/skills/pull-schemas/scripts/run.sh" [flags]| Flag | Meaning |
| (none) | Discover all node types referenced in workflows/**/*.workflow.ts, fetch all, rebuild index |
--core-only | Skip community nodes (only n8n-nodes-base.*) |
--community-only | Skip core nodes |
--nodes <list> | Skip discovery, fetch this comma-separated list of node types |
--packages <list> | Skip Stage 1 entirely, jump straight to Stage 2 (npm extraction) for each package — what the SessionStart auto-reaction emits |
--workspace <dir> | Workspace root (default: current directory) |
--no-index | Skip the final index rebuild |
The script runs three stages internally:
- Stage 1 — for each discovered node type:
npx n8nac skills node-info <type> --json > schemas/nodes/<type>.json. If n8nac returns "not found", schedule the type's package for Stage 2. - Stage 2 — for any package n8nac did not cover (or any package passed via
--packages): install it into a temp dir together withn8n-workflow, instantiate each exported node class, write thedescriptionpayload toschemas/nodes/<pkg>.<node>.json(scoped packages get a per-scope subdir). - Stage 3 — walk
schemas/nodes/**and rebuildschemas/_index.jsonwithtype → {file, displayName, packageVersion}.
When to auto-trigger this skill
| Situation | Invocation |
npx n8nac skills node-info <type> returns empty/not-found mid-workflow | --packages <pkg-prefix> for that single package |
n8nac validation reports unknown node type | --packages <pkg-prefix>, then re-validate |
packageVersion: null in _index.json for a community node | --packages <pkg> to refresh the versioned schema |
SessionStart check-schema-versions.sh emits AUTOPILOT_ACTION_REQUIRED: /n8n-autopilot:pull-schemas --community-only --packages <list> | Run the literal command from the auto-reaction line |
In /n8n-autopilot:build-workflow — if Phase 0 skills node-info returns empty for a community node, invoke run.sh --packages <pkg> inline before proceeding. The gate "verified parameter names for every node" requires a valid schema.
Companion scripts
scripts/discover-types.sh— grep node types out ofworkflows/**/*.workflow.tsscripts/fetch-one.sh— fetch one indexed node via n8nac CLI (exit 1 = "not in n8nac index, try Stage 2")scripts/fetch-pkg.js— extract every exported node class from a published npm packagescripts/rebuild-index.js— rebuildschemas/_index.json
Each is callable on its own when you need to debug a single step. The skill body intentionally does not duplicate their logic — they are the source of truth.
Staleness + coverage check
These two diagnostics live as SessionStart hooks (plugin-wide) and can also be run manually:
bash "$CLAUDE_PLUGIN_ROOT/scripts/check-schema-versions.sh" # cached vs latest npm version
bash "$CLAUDE_PLUGIN_ROOT/scripts/check-installed-nodes.sh" # which installed community nodes lack a schemaThe coverage check queries /api/v1/community-packages on your n8n instance — only present on installations with community-package management enabled. On instances where the endpoint 404s, the check skips silently. Requires .env with N8N_API_URL and N8N_API_KEY.
Notes
- Schemas are committed to git — they persist across sessions and are part of the workspace.
- Existing schema files are overwritten on each run (intentional — fresh data each time).
packageVersionfield tracks which npm version was used; the staleness check reads it.- Stage 2 writes a
packageNamefield so the staleness/coverage checks know which npm package to query.
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
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.