Back to table of contents

18. Prerequisites and installation

To use ywc-* Skills reliably, a few tools need to be in place beforehand. Installing via the Plugin marketplace or Codex plugin handles file copying and registration automatically, but when a Skill actually runs, it needs the tools below available on your system. The order is: ① install the required tools → ② install ywc-agent-toolkit itself (Claude Code / Codex) — everything below that is an optional tool you prepare as needed.

#Required tools

Of these, only uv is Claude Code–only — the rest are required for both Claude Code and Codex.

Installing gh isn't enough on its own — it must be authenticated before Skills that handle PRs (ywc-create-pr, ywc-handle-pr-reviews, ywc-merge-dependabot, etc.) work correctly.

$gh auth login
gh auth setup-git
gh auth status

Environment variables (only when you need them)

Everything works with the defaults; the following are optional overrides for when you want to change a location or behavior.

#Installing ywc-agent-toolkit

Pick the tab for the tool you use. Neither path has any prerequisites.

Method 1 — Plugin marketplace (recommended)

/plugin marketplace add yongwoon/ywc-agent-toolkit

/plugin install ywc-agent-toolkit@ywc-agent-toolkit

$codex plugin marketplace add yongwoon/ywc-agent-toolkit

$codex plugin add ywc-agent-toolkit@ywc-agent-toolkit

The first command registers the marketplace source, and the second actually installs ywc-agent-toolkit. If you've already added the marketplace in Codex, run codex plugin marketplace upgrade ywc-agent-toolkit to pull the latest snapshot.

Method 2 — Bash script fallback

In environments where a plugin install is hard, clone the repository and use the fallback script. You can check the list of installable skills/agents below.

$bash scripts/install.sh --list

$bash scripts/install.sh --cc

$bash scripts/install.sh --cc-agents

$bash scripts/install.sh --codex

$bash scripts/install.sh --codex-agents

If you use both Claude Code and Codex, install both at once.

$bash scripts/install.sh --all

#Optional tools — Local CI-level validation (recommended for contributors / maintainers)

If you want to validate at the same level as GitHub Actions locally before opening a PR, install the following. These are not required to use the Skills themselves.

$brew install shellcheck
npm install -g markdownlint-cli2

node, npm, and npx are needed to run markdownlint-cli2, Playwright, and JS/TS cleanup tools — installing them via a version manager (nvm, volta, etc.) is easier to maintain.

$node --version
npm --version
npx --version
shellcheck --version
markdownlint-cli2 --version

#Optional tools — Preparing design-related Skills

If you plan to use design-related Skills often, install impeccable first. Skills such as ywc-design-renew and ywc-ui-ux-review work better when the project already has design context and anti-pattern detection rules available.

$npx impeccable install

After installation, reopen Claude Code or Codex. For a new project, run /impeccable init first so later design-related Skills can use that design context.

#Optional tools — Situational language/domain tools

You don't need to install the tools below globally for every project. Prepare them only when you use the relevant language or Skill frequently.

$npx knip
npx depcheck
npx ts-prune
ruff check .
mypy .
pyright
go install golang.org/x/tools/cmd/deadcode@latest
npx playwright install --with-deps chromium

#Verification commands

Before running a Skill for the first time, you can check that the required tools are all recognized at once.

$git --version
bash --version
jq --version
python3 --version
gh auth status
curl --version
uv --version
rg --version

If you plan to work with PR-based Skills, it's worth checking gh status once more separately.

$gh auth status
gh repo view --json nameWithOwner --jq .nameWithOwner
gh pr checks --watch

Previous: 17. Full Skill Reference · Back to table of contents »