Automated summary
A slash command that installs and builds the repository's development tooling: the Too Many Cooks MCP server, the VSCode extension, or Chromium/Playwright for website E2E testing.
Strengths
- Consolidates standard install procedures into one command (npm ci + build, vsix packaging, Playwright install)
- Includes the step that registers the MCP server with Claude Code via `claude mcp add`
- Documents ordering dependencies, such as building the MCP server before the VSCode extension
Limitations
- Directory paths (too-many-cooks, too_many_cooks_vscode_extension, website) are hardcoded to this repository
- Assumes Node/npm and the `code` CLI are already installed, with no pre-checks or error handling
- No uninstall or update path for the tools it installs
Use it when onboarding a machine or right after cloning the repo, to prepare the MCP server, VSCode extension, or Playwright test environment.
Avoid it if you need a portable installer for a different project, or if you just want to run the tests without reinstalling the tooling.
Security analysis
CautionThere is no destructive, obfuscated, or exfiltrating behavior: no curl|sh piping, no rm -rf, no credential or token handling, no network calls to arbitrary hosts. The risk profile comes from legitimate but powerful tooling — npm install scripts, npx fetching a remote package, and a Playwright install that escalates to the system package manager. That is typical of a dev-environment setup skill and warrants caution rather than a risky rating, but users should be aware the commands execute third-party code from the registry.
- •Uses Bash to run `npm ci`, which executes arbitrary install/postinstall lifecycle scripts from dependencies
- •Runs `npx @vscode/vsce` which downloads and executes a package from the npm registry at run time
- •`npx playwright install --with-deps` invokes the system package manager (often with sudo/root) to install OS-level libraries
- •No pinned versions or lockfile/dependency verification called out explicitly in the instructions
Examples
/setup mcp/setup playwright and then run the website test suite to confirm Chromium works/setup extension — build the server first, then package and install the .vsixname: setup-dev description: Install development tools (mcp | extension | playwright) disable-model-invocation: true allowed-tools: Bash
Setup Development Tools
Usage: /setup <tool>
mcp— Build the Too Many Cooks MCP serverextension— Build the VSCode extensionplaywright— Install Chromium and Playwright for website E2E testing
MCP Server Setup
cd too-many-cooks && npm ci && npm run build
Add to Claude Code:
claude mcp add --transport http too-many-cooks http://localhost:4040/mcp
VSCode Extension Setup
Build the MCP server first (above), then:
cd too_many_cooks_vscode_extension
npm ci
npm run compile
npx @vscode/vsce package
code --install-extension *.vsix
Playwright Setup
cd website && npm ci
cd website && npx playwright install --with-deps chromium
Run website tests:
cd website && npm test
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/setup-development-tools-mrwak9bn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/setup-development-tools-mrwak9bn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/setup-development-tools-mrwak9bn/download' --output '.skill-downloads/setup-development-tools-mrwak9bn/SKILL.md.part' && mv '.skill-downloads/setup-development-tools-mrwak9bn/SKILL.md.part' '.skill-downloads/setup-development-tools-mrwak9bn/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/setup-development-tools-mrwak9bn/SKILL.md' && test -s '.skill-downloads/setup-development-tools-mrwak9bn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/setup-dev' && cp -R '.skill-downloads/setup-development-tools-mrwak9bn' '.claude/skills/setup-dev'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/setup-development-tools-mrwak9bn'openskills read 'setup-development-tools-mrwak9bn'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/setup-development-tools-mrwak9bn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.