n8n Code Node JavaScript
czlonkowski/n8n-skills
Guides writing JavaScript in n8n Code nodes: picking an execution mode, reading input data, returning items, using built-in helpers and avoiding common errors.
A skill your agent uses when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow…
Install Manor Workspace Architecture
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install manor-os/manor-ai manor-workspace-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .claude/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .claude/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install manor-os/manor-ai manor-workspace-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .agents/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .agents/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install manor-os/manor-ai manor-workspace-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .cursor/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .cursor/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/manor-os/manor-ai.git --path .agents/skills/manor-workspace-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install manor-os/manor-ai manor-workspace-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .gemini/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .gemini/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install manor-os/manor-ai manor-workspace-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .github/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .github/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install manor-os/manor-ai manor-workspace-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/manor-os/manor-ai.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/manor-workspace-architecture .opencode/skills/manor-workspace-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "manor-workspace-architecture" agent skill from https://github.com/manor-os/manor-ai/tree/main/.agents/skills/manor-workspace-architecture into .opencode/skills/manor-workspace-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "manor-workspace-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
manor-workspace-architecture- GitHub stars
- 162
- Token cost
- ~756 tokens
- SKILL.md length
- 379 words
- Files
- 4 (incl. references)
- Skills in repo
- 21
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow…
- Works in 5 steps: Read architecture.md completely. → Locate the requested change on one or… → Read the code entries and state owners… → …
- Testing Manor Workspace behavior
- SKILL.md covers Required reading, Change protocol, Boundary rules and Completion gate
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Manor Workspace Architecture is an agent skill from manor-os/manor-ai. Use when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow, automation, approval, artifact, Knowledge, credits, lifecycle, or Blueprint boundaries.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/architecture.md` and `references/node-test-checklist.md`).
It sits in Productivity & Automation, covering Workflow automation. The repository describes itself as: Source-available, self-hosted AI agent workspace for small businesses and lean teams — with BYOK, workflows, tools, and human approvals.
When your agent uses it
- Testing Manor Workspace behavior
- Especially when a change crosses chat
- Blueprint boundaries
Example prompts
- “/manor-workspace-architecture”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read architecture.md completely.
- Locate the requested change on one or more WS-xx nodes.
- Read the code entries and state owners listed for those nodes.
- Trace every outgoing edge from the changed nodes. State which edges are
- Use node-test-checklist.md to run the
What it can do on your machine
Read from SKILL.md and the folder at commit 140c09a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Manor Workspace Architecture loads about 756 tokens when it runs, and up to ~27k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 379 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 379 words (~756 tokens).
“A Workspace is an operating boundary over several runtimes. It is not a Task, a Workflow, a chat room, or a Blueprint. Any change must first identify which runtime node owns the behavior and which downstream contracts it affects.”
- name
- manor-workspace-architecture
Files
SKILL.md and 3 other files (references) in .agents/skills/manor-workspace-architecture of manor-os/manor-ai.
- SKILL.md
- agents/openai.yaml
- references/architecture.md
- references/node-test-checklist.md
Open the folder on GitHubat commit 140c09a
Compare with similar skills
Manor Workspace Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Manor Workspace Architecture this skillmanor-os/manor-ai | 162 | — | ~756 | Automated safety check: Pass | Custom licence | |
| n8n Code Node JavaScriptczlonkowski/n8n-skills | 6.4k | — | ~4.9k | Automated safety check: Pass | MIT | |
| GitHub Star Managercat-xierluo/legal-skills | 720 | — | ~2k | Automated safety check: Notes | MIT | |
| Windmill Workflow-as-Code Scriptswindmill-labs/windmill | 18k | — | ~7.9k | Automated safety check: Pass | Custom licence | |
| Stp AutomationJoelLewis/finance_skills | 206 | — | ~7.8k | Automated safety check: Pass | MIT | |
| Skyvern Browser AutomationSkyvern-AI/skyvern | 23k | 1 repos | ~2.9k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
GitHub Star Manager
cat-xierluo/legal-skills
Finds GitHub projects mentioned in articles or screenshots and stars them, tracks updates to your starred repos, and builds an HTML dashboard to browse them.
Windmill Workflow-as-Code Scripts
windmill-labs/windmill
Helps your agent write and edit Windmill workflow-as-code scripts built from workflow, task, step, sleep and approval calls, and then preview them locally.
Stp Automation
JoelLewis/finance_skills
Measure and raise straight-through processing (STP) rates in securities operations through zero-touch, exception-based processing.
Skyvern Browser Automation
Skyvern-AI/skyvern
Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.
- Official
Debugging Executions
n8n-io/n8n
Debug failed or wrong-output workflow executions using executions tools.
More from manor-os/manor-ai
All 21 skills in this repoPDF
manor-os/manor-ai
A skill your agent uses whenever the user wants to do anything with PDF files.
Manor Workspace Blueprint
manor-os/manor-ai
A skill your agent uses when creating, exporting, hand-authoring, installing, upgrading, reverting, reviewing, or debugging any Manor Workspace Blueprint, especially when Workspace behavior differs…
PPTX
manor-os/manor-ai
A skill your agent uses to generate high-quality editable PowerPoint/PPTX decks from user requirements, topic prompts, or provided text/Markdown.
Video Edit
manor-os/manor-ai
Default workflow for editing, composing, or creating a finished video from screenshots, UI captures, uploaded clips, images, audio, or a written brief.
Intro
manor-os/manor-ai
Public English guide to the Manor AI OSS self-hosted product, its visible capabilities, and end-user workflows.
Skill Creator
manor-os/manor-ai
Create, update, review, and evaluate reusable Manor Skills. An agent skill from manor-os/manor-ai.
Related
Categories
Questions about Manor Workspace Architecture
What does Manor Workspace Architecture do?
A skill your agent uses when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow…. Manor Workspace Architecture is an agent skill from manor-os/manor-ai. Use when changing, debugging, reviewing, documenting, or testing Manor Workspace behavior, especially when a change crosses chat, Strategist, Proposal, Task, Plan, Workflow, automation, approval, artifact, Knowledge, credits, lifecycle, or Blueprint boundaries.
When should I use Manor Workspace Architecture?
Manor Workspace Architecture fits situations like: testing Manor Workspace behavior; especially when a change crosses chat; blueprint boundaries.
How do I install Manor Workspace Architecture in Claude Code?
Run `npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a claude-code`. Or copy the skill folder (.agents/skills/manor-workspace-architecture in manor-os/manor-ai) into .claude/skills/manor-workspace-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Manor Workspace Architecture in Codex?
Run `npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a codex`. Or copy the skill folder (.agents/skills/manor-workspace-architecture in manor-os/manor-ai) into .agents/skills/manor-workspace-architecture in your project. Codex loads it when a task matches its description.
Can I use Manor Workspace Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add manor-os/manor-ai --skill manor-workspace-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/manor-workspace-architecture, .gemini/skills/manor-workspace-architecture, .github/skills/manor-workspace-architecture and .opencode/skills/manor-workspace-architecture in your project.
What does Manor Workspace Architecture need to run?
SKILL.md names no scripts, command-line tools or credentials: Manor Workspace Architecture is instructions for the agent only.
Does Manor Workspace Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Manor Workspace Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Manor Workspace Architecture use?
Manor Workspace Architecture has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Manor Workspace Architecture use?
About 756 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 26k tokens, read only when the agent opens those files.
What are the alternatives to Manor Workspace Architecture?
Skills that share tags, products or a category with Manor Workspace Architecture: n8n Code Node JavaScript (czlonkowski/n8n-skills, 6.4k stars), GitHub Star Manager (cat-xierluo/legal-skills, 720 stars), Windmill Workflow-as-Code Scripts (windmill-labs/windmill, 18k stars) and Stp Automation (JoelLewis/finance_skills, 206 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Manor Workspace Architecture?
manor-os (a GitHub organization) maintains it in manor-os/manor-ai, which has 162 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on September 7, 2026.
Source: manor-os/manor-ai on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.