find-project
Skill18 starsChanged 43 days agoMITView on GitHub
List all n8n projects visible on the active instance, showing which one the workspace is pinned to. Use whenever the user asks "which projects exist", "list n8n projects", "show projects on instance", or before pinning a workspace to a different project. Derives projects from `credential list` + `workspace status` — works without Enterprise REST `/projects` endpoint.
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
- 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
- pull-schemasSkill
- session-envSkill
- stack-intakeSkill
- sync-credentialsSkill
- test-manualSkill
The file
Files
Find Project
Multi-project visibility for the active n8n instance.
node "$CLAUDE_PLUGIN_ROOT/skills/find-project/scripts/list.js" "$ARGUMENTS"What it does
- Reads
npx n8nac workspace status --json→ active project pin. - Reads
npx n8nac credential list --json→ derives the set of projects that own any credential (n8n public API does not expose/projectsdirectly outside Enterprise). - Prints a table of all visible projects with counts, marks the active one.
- Surfaces the commands to switch the workspace pin.
Output shape
Active project pin: Personal (BFOi3Ip4tIRPFnMg)
Projects visible on https://n8n.example.com:
ID Name Credentials Active pin?
---------------- ------------------ ----------- -----------
BFOi3Ip4tIRPFnMg Personal 14 ← active
NhVwnjvOp5c5687N Shared Project 21
abcDEF1234567890 Marketing Ops 7
To switch the active project on the current environment:
npx n8nac env update <env> --project-name "Shared Project"
npx n8nac env update <env> --project-id "NhVwnjvOp5c5687N"
After switching, re-run /n8n-autopilot:check-mcps to verify the new scope.Why this skill exists
A common class of incidents: agents reference credentials from the wrong project because they cannot enumerate projects via the n8n public API. workspace status only shows the active pin, not the alternatives. This skill derives the full project set from credential ownership and surfaces the exact switch command.
Exit codes
0— listing printed1— workspace not bound / n8nac CLI failure
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.

