Chart Visualization
bytedance/deer-flow
Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.
Audit, lower, test, and preserve Codsen package Node.js engine floors.
MITAuto-check passed
Install Maintain Node Compatibility
$ npx skills add codsen/codsen --skill maintain-node-compatibility -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install codsen/codsen maintain-node-compatibility --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/codsen/codsen.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .claude/skills/maintain-node-compatibility && 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 "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .claude/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibilityType 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 codsen/codsen --skill maintain-node-compatibility -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install codsen/codsen maintain-node-compatibility --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .agents/skills/maintain-node-compatibility && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .agents/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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 codsen/codsen --skill maintain-node-compatibility -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install codsen/codsen maintain-node-compatibility --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .cursor/skills/maintain-node-compatibility && 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 "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .cursor/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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/codsen/codsen.git --path .agents/skills/maintain-node-compatibility--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 codsen/codsen --skill maintain-node-compatibility -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install codsen/codsen maintain-node-compatibility --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .gemini/skills/maintain-node-compatibility && 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 "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .gemini/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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 codsen/codsen maintain-node-compatibilityInstalls 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 codsen/codsen --skill maintain-node-compatibility -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .github/skills/maintain-node-compatibility && 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 "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .github/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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 codsen/codsen --skill maintain-node-compatibility -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install codsen/codsen maintain-node-compatibility --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/codsen/codsen.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/maintain-node-compatibility .opencode/skills/maintain-node-compatibility && 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 "maintain-node-compatibility" agent skill from https://github.com/codsen/codsen/tree/main/.agents/skills/maintain-node-compatibility into .opencode/skills/maintain-node-compatibility/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-node-compatibility", 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
maintain-node-compatibility- GitHub stars
- 214
- Token cost
- ~938 tokens
- SKILL.md length
- 478 words
- Files
- 2
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audit, lower, test, and preserve Codsen package Node.js engine floors.
- Works in 9 steps: Record the working tree and active… → Start with the package's declared floor.… → Run the package's direct unit script,… → …
- Changing package engines
- SKILL.md covers Workflow, Matrix orchestration, Raising a floor and Validation result
- Calls npm
What it does
Maintain Node Compatibility is an agent skill from codsen/codsen. Audit, lower, test, and preserve Codsen package Node.js engine floors. Use when changing package engines, runtime dependencies, esbuild targets, Node compatibility CI, CLI/library support, or investigating whether a package can support an older Node release.
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It works with Node.js. The repository describes itself as: a monorepo of npm packages. The licence is MIT.
When your agent uses it
- Changing package engines
- Runtime dependencies
- Esbuild targets
- Node compatibility CI
Example prompts
- “/maintain-node-compatibility”
Requirements
- Node.js
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Record the working tree and active node/npm versions. Preserve unrelated
- Start with the package's declared floor. For a new audit, test exact Node
- Run the package's direct unit script, bypassing root housekeeping, coverage,
- Test coupled CLI/library packages together and include every internal runtime
- Inspect the complete production dependency closure. Passing with an existing
- Set package.json#engines.node to the exact tested patch floor, for example
- Rebuild on the root-supported toolchain. Esbuild derives its Node target from
- Regenerate the root lockfile and verify manifest/lock engine parity.
- Run unit suites in CI on every configured even Node major at or above each
What it can do on your machine
Read from SKILL.md and the folder at commit e7e6df7. 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
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Maintain Node Compatibility loads about 938 tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 478 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
The full file from codsen/codsen at commit e7e6df7, republished under its MIT licence (© codsen). 478 words, ~938 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-node-compatibility/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- maintain-node-compatibility
- description
- Audit, lower, test, and preserve Codsen package Node.js engine floors. Use when changing package engines, runtime dependencies, esbuild targets, Node compatibility CI, CLI/library support, or investigating whether a package can support an older Node release.
Maintain Node Compatibility
Preserve Codsen's unusually broad Node support as a product advantage. Seek the lowest truthful and maintainable floor; never equate a dependency's newest major with best practice automatically.
Workflow
- Record the working tree and active
node/npmversions. Preserve unrelated changes and avoid concurrent global Node switches. - Start with the package's declared floor. For a new audit, test exact Node
18.20.8first, then the canonical exact patches of 20, 22, 24, and 26 fromops/helpers/nodeCompatibility.jsonly after a genuine failure. - Run the package's direct
unitscript, bypassing root housekeeping, coverage, and build tools whose own engine floor is unrelated to the published runtime. - Test coupled CLI/library packages together and include every internal runtime dependency in the audit.
- Inspect the complete production dependency closure. Passing with an existing
install is insufficient when a dependency's
engines.nodewould make a fresh engine-strict consumer install fail. Prefer a sound compatible dependency release when its API and behavior fit the package. - Set
package.json#engines.nodeto the exact tested patch floor, for example>=18.20.8, not>=18. Keep engines manifest-owned; never add engine policy tolect. - Rebuild on the root-supported toolchain. Esbuild derives its Node target from the manifest, so compare artifacts when lowering could change emitted code.
- Regenerate the root lockfile and verify manifest/lock engine parity.
- Run unit suites in CI on every configured even Node major at or above each package's floor. Also perform engine-strict packed-artifact installation and library-import or CLI-functional smokes.
Show full SKILL.md (232 more words)Show less
Matrix orchestration
- Build and pack all workspaces once under the root-supported Node toolchain.
- Use cumulative eligibility: on a given lane, test packages whose declared floor is less than or equal to that lane. Always run every configured even lane through the top version, even when no package starts at an intermediate major.
- In CI, run exact-version lanes in parallel and share the immutable packed artifacts from the build job.
- Locally, keep majors sequential by default and parallelize packages within a
lane. Resolve cached runtimes with
n whichor execute them withn exec; never mutate the global Node installation underneath the parent npm process. - Keep coverage, examples, lint, generated-file checks, and perf in a separate root-toolchain phase. Compatibility lanes run direct unit scripts plus packed install/import/CLI checks.
Run npm run test:compatibility for the local build-once, pack-once exact Node
matrix. Root npm test also runs the separate test:quality (turbo run devtest) phase and performance benchmarks.
Raising a floor
Raise a package only after reproducing a concrete source, runtime, or defensible dependency blocker on the lower major. Report the failing package, command, error, and the first exact newer runtime that passes. Do not use EOL status alone to erase deliberately supported compatibility.
Validation result
Summarize package counts by engine floor, exact runtime versions tested, unit pass/fail totals, dependency downgrades, packed-install results, and CI matrix coverage. Distinguish published runtime compatibility from root development toolchain requirements.
© codsen, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .agents/skills/maintain-node-compatibility of codsen/codsen.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e7e6df7
Compare with similar skills
Maintain Node Compatibility 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 |
|---|---|---|---|---|---|---|
| Maintain Node Compatibility this skillcodsen/codsen | 214 | — | ~938 | Automated safety check: Pass | MIT | |
| Chart Visualizationbytedance/deer-flow | 83k | 2 repos | ~840 | Automated safety check: Pass | MIT | |
| Web Access via Browser CDPeze-is/web-access | 9.1k | 4 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Knap Markdown Templateskepano/obsidian-skills | 49k | 2 repos | ~986 | Automated safety check: Pass | MIT | |
| Electron Multi-Process ArchitectureiOfficeAI/AionUi | 33k | 1 repos | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Chrome CDP Browser Controlzenstory-ai/oh-story-claudecode | 7.4k | 3 repos | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Web Access via Browser CDP
eze-is/web-access
Routes every web task, from searching to logged-in browsing, through a tiered choice of search, fetch, curl or a real Chrome or Edge session driven over CDP.
Knap Markdown Templates
kepano/obsidian-skills
Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.
Electron Multi-Process Architecture
iOfficeAI/AionUi
Tells the agent where new code belongs in an Electron multi-process project and which APIs each process may use, with rules for new bridges, services, agents and workers.
Chrome CDP Browser Control
zenstory-ai/oh-story-claudecode
Drives a Chrome window over the DevTools Protocol with the agent-browser CLI, so the agent can reuse your logged-in sessions, read pages and pull tokens.
DeerFlow Smoke Test
bytedance/deer-flow
Walks through an end-to-end smoke test of a DeerFlow deployment: pull the latest code, deploy with Docker or locally, verify services, run health checks and write a report.
More from codsen/codsen
Calculate The Perf Performance
codsen/codsen
Run, audit, and interpret the Codsen monorepo performance benchmarks.
Lint Repository Markdown
codsen/codsen
Keep the repository's linted Markdown passing npm run lint:markdown.
Related
Works with
Questions about Maintain Node Compatibility
What does Maintain Node Compatibility do?
Audit, lower, test, and preserve Codsen package Node.js engine floors. Maintain Node Compatibility is an agent skill from codsen/codsen.js engine floors.
When should I use Maintain Node Compatibility?
Maintain Node Compatibility fits situations like: changing package engines; runtime dependencies; esbuild targets; Node compatibility CI.
How do I install Maintain Node Compatibility in Claude Code?
Run `npx skills add codsen/codsen --skill maintain-node-compatibility -a claude-code`. Or copy the skill folder (.agents/skills/maintain-node-compatibility in codsen/codsen) into .claude/skills/maintain-node-compatibility in your project. Claude Code loads it when a task matches its description.
How do I install Maintain Node Compatibility in Codex?
Run `npx skills add codsen/codsen --skill maintain-node-compatibility -a codex`. Or copy the skill folder (.agents/skills/maintain-node-compatibility in codsen/codsen) into .agents/skills/maintain-node-compatibility in your project. Codex loads it when a task matches its description.
Can I use Maintain Node Compatibility 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 codsen/codsen --skill maintain-node-compatibility -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-node-compatibility, .gemini/skills/maintain-node-compatibility, .github/skills/maintain-node-compatibility and .opencode/skills/maintain-node-compatibility in your project.
What does Maintain Node Compatibility need to run?
Going by SKILL.md and its folder, Maintain Node Compatibility needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Maintain Node Compatibility access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Maintain Node Compatibility 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 Maintain Node Compatibility use?
Maintain Node Compatibility is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain Node Compatibility use?
About 938 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Maintain Node Compatibility?
Skills that share tags, products or a category with Maintain Node Compatibility: Chart Visualization (bytedance/deer-flow, 83k stars), Web Access via Browser CDP (eze-is/web-access, 9.1k stars), Knap Markdown Templates (kepano/obsidian-skills, 49k stars) and Electron Multi-Process Architecture (iOfficeAI/AionUi, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain Node Compatibility?
codsen (a GitHub organization) maintains it in codsen/codsen, which has 214 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on September 29, 2026.
Source: codsen/codsen on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.