New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Repo Healthcheck Node

by commercetools in commercetools/ui-kit

Verify a Node.js/TypeScript repo's development environment is correctly set up.

MITAuto-check: notesFrontend & Design

Install Repo Healthcheck Node

skills CLI
$ npx skills add commercetools/ui-kit --skill repo-healthcheck-node -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install commercetools/ui-kit repo-healthcheck-node --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/commercetools/ui-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-healthcheck-node .claude/skills/repo-healthcheck-node && rm -rf skills-src

Use ~/.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/

Facts

Skill name
repo-healthcheck-node
GitHub stars
154
Token cost
~1.6k tokens
SKILL.md length
738 words
Files
1
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Verify a Node.js/TypeScript repo's development environment is correctly set up.

  • Works in 3 steps: Read Repo Configuration → Run Checks → Report Results
  • Troubleshooting CI failures
  • SKILL.md covers Arguments, Process, Guidelines and RFC 2119 Key Words
  • Calls pnpm, node and nvm

What it does

Repo Healthcheck Node is an agent skill from commercetools/ui-kit. Verify a Node.js/TypeScript repo's development environment is correctly set up. Checks Node.js version, pnpm version, dependency installation, and build success. Use when onboarding, troubleshooting CI failures, or verifying a fresh clone.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Failing and flaky tests and Design systems. It works with Node.js, pnpm, TypeScript and npm. The licence is MIT.

When your agent uses it

  • Troubleshooting CI failures
  • Verifying a fresh clone

Example prompts

  • “/repo-healthcheck-node”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Bash, Grep, Glob, Read

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Read Repo Configuration
  2. Run Checks
  3. Report Results

What it can do on your machine

Read from SKILL.md and the folder at commit 62ca335. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Grep
    • Glob
    • Read

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm
    • node
    • nvm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm and 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

Repo Healthcheck Node loads about 1.6k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 738 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Grep, Glob, Read

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 commercetools/ui-kit at commit 62ca335, republished under its MIT licence (© commercetools). 738 words, ~1,588 tokens.

Download SKILL.mdSave it as .claude/skills/repo-healthcheck-node/SKILL.md (or your agent's skills folder).
name
repo-healthcheck-node
description
Verify a Node.js/TypeScript repo's development environment is correctly set up. Checks Node.js version, pnpm version, dependency installation, and build success. Use when onboarding, troubleshooting CI failures, or verifying a fresh clone.
allowed-tools
Bash, Grep, Glob, Read
disable-model-invocation
false
argument-hint
[--fix]
scope
node, maintenance

Repo Healthcheck — Node.js

Verify that a Node.js/TypeScript repository's development environment is correctly set up. Reads AGENTS.md and CLAUDE.md (if present) for repo-specific version requirements and build commands, then runs each check and reports a clear pass/fail summary.

Arguments

  • --fix (optional): Attempt to auto-fix failures where possible (e.g. run pnpm install if dependencies are missing). Without this flag, the skill only reports — it does not modify the environment.

Process

1. Read Repo Configuration

Read the following sources in priority order (later sources override earlier):

  1. AGENTS.md — repo-specific commands and version requirements
  2. CLAUDE.md (if present) — may contain additional or overriding requirements
  3. .nvmrc or .node-version (if present) — authoritative Node.js version
  4. package.json engines field — authoritative pnpm/node version constraints

Look for:

  • Expected Node.js version — check .nvmrc / .node-version first, then package.json engines.node, then patterns in AGENTS.md/CLAUDE.md like node 24, node: 24.13, or explicit version statements.
  • Expected pnpm version — check package.json engines.pnpm first, then patterns in AGENTS.md/CLAUDE.md like pnpm 10, pnpm: 10.29.3, or explicit version statements.
  • Install command — default pnpm install. Override if the docs specify a different command (e.g. pnpm install --frozen-lockfile).
  • Build command — default pnpm build. Override if the docs specify something different (e.g. pnpm build:packages, pnpm run compile).

If no version or command overrides are found, use the defaults and note that expectations came from defaults, not from repo configuration.

2. Run Checks

Run each check in order. Capture the result (pass/fail), the actual value, and the required value for the summary table.

Critical checks are Node.js and pnpm version. If either critical check fails, you MUST skip the dependent checks (install and build) and note the reason in the output.

Check 1 — Node.js Version
bash
node --version
  • If an expected version was found: compare using prefix matching (see Guidelines). Pass if they match; fail with actual vs expected.
  • If no expected version was found: report the installed version as informational (no pass/fail judgment).
  • Fix command (if --fix and failing): nvm install (reads from .nvmrc automatically, if present).
Check 2 — pnpm Version
bash
pnpm --version
  • If pnpm is not installed: MUST skip checks 3 and 4, report as missing.
  • If an expected version was found: compare using prefix matching (see Guidelines). Pass if they match; fail with actual vs expected.
  • If no expected version was found: report the installed version as informational (no pass/fail judgment).
  • Fix command (if --fix and failing): npm install -g pnpm@latest.
Check 3 — Dependency Installation

Only run if checks 1 and 2 did not produce critical failures.

Use the install command from step 1 (default: pnpm install).

bash
pnpm install 2>&1
  • Pass if exit code is 0.
  • Fail with the last 20 lines of output if exit code is non-zero.
  • If --fix was passed and the default frozen-lockfile variant failed, retry without --frozen-lockfile and report whether the retry succeeded.
Show full SKILL.md (286 more words)Show less
Check 4 — Build

Only run if check 3 passed.

Run the build command from step 1 (default: pnpm build).

  • Pass if exit code is 0.
  • Fail with the last 30 lines of output if exit code is non-zero.
3. Report Results

Output a summary table showing actual version vs required version for each check:

markdown
## 🏥 Repo Healthcheck — Node.js

| Check             | Status                     |
| ----------------- | -------------------------- |
| Node.js >= 24.0.0 | ✅ v24.13.0                |
| pnpm >= 10.0.0    | ✅ v10.29.3                |
| pnpm install      | ✅                         |
| Build             | ❌ Exit code 1 (see below) |

Status format:

  • Pass with version: ✅ vX.X.X
  • Pass without version: ✅
  • Fail with version mismatch: ❌ vX.X.X (requires >= Y.Y)
  • Fail with error: ❌ <short reason>
  • Skipped: ⏭ Skipped (Node.js check failed)
  • Informational (no expected version): ℹ vX.X.X

Follow the table with the full output for any failed checks so the user can diagnose the issue.

Issues Found

If any checks failed, add an Issues Found section with copy-pasteable fix commands:

markdown
### ❌ Issues Found

- **Node.js**: Run `nvm install` to install the required version
- **Build**: Run `pnpm build` and review the output above
Success

If ALL checks pass, add a success message with next steps:

markdown
### ✅ All Systems Go!

Environment is ready. Start the dev server with:

\`\`\`bash
pnpm start
\`\`\`

Guidelines

  • You MUST read AGENTS.md and CLAUDE.md before running any checks — repo configuration takes precedence over defaults.
  • You MUST always show the full results table even if some checks fail.
  • You MUST skip install and build checks if a critical check (Node.js or pnpm) fails, since those checks depend on correct tooling.
  • You SHOULD provide clear, copy-pasteable fix commands for any failures.
  • Version comparison is prefix-based: if the expected version is 24, match any 24.x.y; if the expected version is 24.13, match any 24.13.y.
  • Do not fail a version check when no expected version is found — report informational only.
  • Only use --fix behaviour when the flag is explicitly passed.
  • Keep output concise: show only the last N lines of command output on failure, not the full log.

RFC 2119 Key Words

  • MUST / REQUIRED — Absolute requirement
  • MUST NOT — Absolute prohibition
  • SHOULD / RECOMMENDED — Should do unless there is a valid reason not to
  • MAY / OPTIONAL — Truly optional

© commercetools, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/repo-healthcheck-node of commercetools/ui-kit.

Open the folder on GitHubat commit 62ca335

Compare with similar skills

Repo Healthcheck Node 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.

Repo Healthcheck Node compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Repo Healthcheck Node this skillcommercetools/ui-kit154—~1.6kAutomated safety check: NotesMIT
NodeHsienW/chat-gun143—~1.6kAutomated safety check: PassCustom licence
Parse Error Logsmaslennikov-ig/claude-code-orchestrator-kit260—~1.5kAutomated safety check: PassCustom licence
Create Docsvictorgarciaesgi/nuxt-typed-router4132 repos~2.8kAutomated safety check: PassMIT
Migrate to Denodenoland/skills100—~2.2kAutomated safety check: WarnMIT
Quill CodePostHog/code179—~1.1kAutomated safety check: PassMIT

Similar skills

  • Node

    HsienW/chat-gun

    Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging…

    143 GitHub stars~1.6k tokensUpdated 6 days ago
    Testing & QAAuto-check passed

  • Parse Error Logs

    maslennikov-ig/claude-code-orchestrator-kit

    Parse build errors, test failures, type-check output, and validation logs into structured data.

    260 GitHub stars~1.5k tokensUpdated 7 mo ago
    Testing & QAAuto-check passed

  • Create Docs

    victorgarciaesgi/nuxt-typed-router

    Create complete documentation sites for projects. An agent skill from victorgarciaesgi/nuxt-typed-router.

    413 GitHub starsUsed in 2 repos~2.8k tokens
    Frontend & DesignAuto-check passed

  • Migrate to Deno

    denoland/skills

    Official

    Moves a Node.js, npm, Yarn, pnpm or Bun project to Deno in reversible steps, starting with Deno as the package manager and changing no code unless needed.

    100 GitHub stars~2.2k tokensUpdated 2 mo ago
    DevelopmentAuto-check: warnings

  • Quill Code

    PostHog/code

    Official

    Edit the @posthog/quill design system locally and consume the change in this repo (posthog-code) before it is published to npm.

    179 GitHub stars~1.1k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed

  • Agentic UI Development

    antdigital-ai/agentic-ui

    Guides development workflow, design system, scripts, and component inventory for @ant-design/agentic-ui.

    224 GitHub stars~555 tokensUpdated today
    Frontend & DesignAuto-check passed

More from commercetools/ui-kit

All 11 skills in this repo

  • Agent Restore Context

    commercetools/ui-kit

    Manage restore context files so skills can survive /clear and /compact.

    154 GitHub stars~944 tokensUpdated 7 days ago
    Auto-check: notes

  • Agent Restore Context Setup

    commercetools/ui-kit

    Set up the restore-context hook so skills can resume workflows after /clear and /compact.

    154 GitHub stars~1.4k tokensUpdated 7 days ago
    Auto-check: notes

  • PR Review Navigator

    commercetools/ui-kit

    Generate AI-assisted navigation aids to help humans start reviewing a pull request more efficiently.

    154 GitHub stars~1.3k tokensUpdated 7 days ago
    Auto-check: notes

  • Remember

    commercetools/ui-kit

    Persist guidelines, conventions, and architectural decisions into the repository's knowledge base.

    154 GitHub stars~2k tokensUpdated 7 days ago
    Auto-check: notes

  • Renovate Review

    commercetools/ui-kit

    Review Renovate dependency upgrade PRs to assess safety and effort.

    154 GitHub stars~907 tokensUpdated 7 days ago
    Auto-check: notes

  • Repo Maintenance Node

    commercetools/ui-kit

    Perform a broad Node/TypeScript repository health sweep — formatting, linting, type errors, dead code, dependency hygiene, and open Renovate PRs.

    154 GitHub stars~3k tokensUpdated 7 days ago
    Auto-check: notes

Works with

Categories

Questions about Repo Healthcheck Node

What does Repo Healthcheck Node do?

Verify a Node.js/TypeScript repo's development environment is correctly set up. Repo Healthcheck Node is an agent skill from commercetools/ui-kit.js/TypeScript repo's development environment is correctly set up.

When should I use Repo Healthcheck Node?

Repo Healthcheck Node fits situations like: troubleshooting CI failures; verifying a fresh clone.

How do I install Repo Healthcheck Node in Claude Code?

Run `npx skills add commercetools/ui-kit --skill repo-healthcheck-node -a claude-code`. Or copy the skill folder (.agents/skills/repo-healthcheck-node in commercetools/ui-kit) into .claude/skills/repo-healthcheck-node in your project. Claude Code loads it when a task matches its description.

How do I install Repo Healthcheck Node in Codex?

Run `npx skills add commercetools/ui-kit --skill repo-healthcheck-node -a codex`. Or copy the skill folder (.agents/skills/repo-healthcheck-node in commercetools/ui-kit) into .agents/skills/repo-healthcheck-node in your project. Codex loads it when a task matches its description.

Can I use Repo Healthcheck Node 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 commercetools/ui-kit --skill repo-healthcheck-node -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/repo-healthcheck-node, .gemini/skills/repo-healthcheck-node, .github/skills/repo-healthcheck-node and .opencode/skills/repo-healthcheck-node in your project.

What does Repo Healthcheck Node need to run?

Going by SKILL.md and its folder, Repo Healthcheck Node needs the command-line tools its instructions call (pnpm, node, nvm and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash, Grep, Glob, Read.

Does Repo Healthcheck Node 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 Repo Healthcheck Node safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Repo Healthcheck Node use?

Repo Healthcheck Node 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 Repo Healthcheck Node use?

About 1.6k tokens (SKILL.md is roughly 6.4k 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 Repo Healthcheck Node?

Skills that share tags, products or a category with Repo Healthcheck Node: Node (HsienW/chat-gun, 143 stars), Parse Error Logs (maslennikov-ig/claude-code-orchestrator-kit, 260 stars), Create Docs (victorgarciaesgi/nuxt-typed-router, 413 stars) and Migrate to Deno (denoland/skills, 100 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Repo Healthcheck Node?

commercetools (a GitHub organization) maintains it in commercetools/ui-kit, which has 154 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 3, 2026.

Source: commercetools/ui-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.