Skip to content

Guide · Agent skill

How to use the Verify Setup Health Check agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The Verify Setup Health Check skill is an agent skill for AI coding agents. When you ask the agent to run the verify-setup command, it runs the project's infrastructure health-check script and then repairs the problems that script reports as failing. After reading this guide you will know what the skill changes, how to install it, how to trigger it with plain requests, and what to check before letting an agent edit your config files.

Verify Setup Health Checkdiet103/claude-code-infrastructure-showcase · MIT

Quick start

  1. 1Download the ZIP. Download the skill ZIP file from this page.
  2. 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for all projects, or into the project's .claude/skills/ folder for one project. In the Claude apps, upload it under Settings → Capabilities → Skills instead.
  3. 3Confirm the project files exist. Make sure .Codex/scripts/verify-setup.sh is present in the project root, and that bash and Node.js with npm are installed.
  4. 4Ask the agent in plain words. Request that the agent run the verify-setup health check and fix what fails.
  5. 5Review the warnings. Read the [WARN] items the agent summarizes and decide whether you want the optional features they describe.
  6. 6Re-run until clean. Confirm the agent re-ran the script until it reported 0 failed, and review the final report of what changed.

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file with instructions that an AI coding agent reads when a request matches the skill. This skill is named source-command-verify-setup and is described as running the infrastructure health check and fixing anything that fails.

Its instructions tell the agent to run the Codex infrastructure health check from the project root, apply the printed fix for every [FAIL] line, re-run the script until it reports 0 failed, and then report what was broken and what was fixed.

  • Installs missing Node dependencies in the hooks folder
  • Makes hook scripts executable
  • Repairs syntax errors such as trailing commas in .Codex/settings.json or .Codex/skills/skill-rules.json without changing any settings values
  • Asks you before copying missing hook scripts from the showcase repository or removing dead registrations
  • Summarizes [WARN] lines about optional features instead of acting on them

Install the skill on Claude Code or the Claude apps

Download the ZIP file for this skill from this page. Then choose one of the methods below.

For Claude Code, unzip the download into ~/.claude/skills/ to make it available in all your projects, or into a project's .claude/skills/ folder to limit it to that project.

In the Claude apps, open Settings, go to Capabilities, and upload the skill under Skills.

  • Personal install: unzip into ~/.claude/skills/
  • Project install: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload

Check the requirements before you run it

The skill expects a specific project layout. It needs the Codex infrastructure files, including the script .Codex/scripts/verify-setup.sh. If that file is missing, the skill will fail immediately, so check for it before you start.

The environment also needs bash, and Node.js with npm for installing hook dependencies.

  • bash
  • Node.js and npm (for installing hook dependencies)
  • The project's .Codex infrastructure files, including .Codex/scripts/verify-setup.sh
bash .Codex/scripts/verify-setup.sh

How do you trigger the skill with a natural request?

The skill is written to run when a user asks to run the migrated source command verify-setup. You do not need to type the file name or a special syntax. Describe what you want in plain words, such as asking the agent to check that your setup is healthy and fix anything broken.

The agent will then run the health check first. It does not make changes until it has seen which lines are failing.

  • Run the verify-setup check and fix anything that fails.
  • Check that my Codex infrastructure setup is healthy and get it green.
  • My hook scripts broke after cloning, can you run the setup health check?
  • Run verify-setup and tell me which warnings are only optional features.

What fixes does the agent apply, and what does it leave alone?

The skill applies the fixes printed by the health check and a few common repairs listed in its instructions. For a failing settings file, it is told to read the file, find the syntax error, and repair it without changing values.

Warnings are handled differently. The skill does not install API keys or system packages on your behalf. Warnings cover optional features such as session intelligence, jq-based file tracking, and AI classification keys, and the agent is told to explain each one and let you decide.

  • Dependencies missing: cd .Codex/hooks && npm install
  • Scripts not executable: chmod +x .Codex/hooks/*.sh
  • Invalid JSON: repair syntax, usually a trailing comma
  • Missing hook scripts: ask whether to copy them from the showcase repository or remove the registration
  • Warnings: summarized, not installed
cd .Codex/hooks && npm install chmod +x .Codex/hooks/*.sh

Safety notes before you let an agent edit your project

This skill runs a script and changes files. It edits settings JSON, runs npm install, and runs chmod on your project. It also uses the network, both for npm install and for the option of copying hook scripts from the showcase repository, which the skill mentions by URL.

If you do not want an agent changing config files without review, run the script yourself first to read the output, or review the diff after the agent finishes. Keep your project under version control so you can revert any change.

  • Runs scripts: yes
  • Uses network: yes
  • Edits .Codex/settings.json and .Codex/skills/skill-rules.json when they contain syntax errors
  • Runs npm install in .Codex/hooks and chmod on .Codex/hooks/*.sh

What people use it for

  • Getting a freshly cloned Codex infrastructure project to pass its health check
  • Repairing a settings.json file that stopped loading after a manual edit with a trailing comma
  • Restoring hook scripts that lost their executable permission
  • Reinstalling hook dependencies after moving a project to a new machine

Frequently asked questions

Is the Verify Setup Health Check skill free to use?

The skill is released under the MIT licence. The source does not state any price, so check the licence text on the repository before you redistribute it.

What do I need to run the verify-setup skill?

You need bash, Node.js and npm, and the project's Codex infrastructure files, including .Codex/scripts/verify-setup.sh. Without that script the skill fails immediately.

How do I install this agent skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps, upload it under Settings → Capabilities → Skills.

Will the skill change my project files?

Yes. It can edit settings JSON to fix syntax errors, run npm install in the hooks folder, and run chmod on hook scripts. It is told not to change settings values or install API keys or system packages.

Why does the verify-setup check say a warning but not fail?

[WARN] lines flag optional features such as session intelligence, jq-based file tracking, and AI classification keys. The skill summarizes them and leaves the decision to you.

Can I use this skill with a project that does not have verify-setup.sh?

No. The source says that projects without the .Codex/scripts/verify-setup.sh file will fail immediately, so the skill is not suitable for them.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

This skill suits developers using the Claude Code infrastructure showcase setup, and teams whose hook scripts and settings files break after edits or cloning. It is a poor fit if your project lacks verify-setup.sh or if you do not want an agent editing config files and running npm install without review.

Download the skill