How do I install the Skillset Smoke Test skill?

Run npx skillmds add majiayu000/skillset-smoke-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Skillset Smoke Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Skillset Smoke Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Skillset Smoke Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Skillset Smoke Test?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Skillset Smoke Test by majiayu000 — Agent Skill

Name: Skillset Smoke Test
Rating: 4.2 (5 reviews)
Author: majiayu000

Skillset Smoke Test

Run and evaluate the Skillset smoke test (aliases, sets, and skill invocation) and interpret its JSON reports. Use this when validating $skill/$set behavior or checking Claude Code/Codex headless runs.

majiayu000 5a94210 2 files · 3.1 KB Updated Sep 9, 2026 567 repo stars

File contents

Skillset Smoke Test Runner

Keep this skill self-contained. If you need more detail, read REFERENCE.md.

Prereqs

Ensure bun is available.
For full runs, ensure claude and codex CLIs are installed and authenticated.
Run from the repo root so the smoke test can find scripts/skillset-smoke.ts.

Run the smoke test

Prefer the repo script so results are structured and gitignored.
Quick smoke (hook-only):
- bun run test:smoke:ci
Hook-only (CLI mode):
- bun run test:smoke:cli
Full run (hook + Claude + Codex):
- bun run test:smoke

Options

--tools hook,claude,codex to limit which tools run.
--hook-mode ci|cli to choose the hook path (repeatable or comma-separated).
--no-clean to preserve the sandbox workspace and XDG dirs.
--clean-all to wipe all smoke test artifacts (workspace + reports).
--strict to exit non-zero if any step fails.

Environment overrides

SKILLSET_SMOKE_CLAUDE_CMD (default: claude)
SKILLSET_SMOKE_CLAUDE_ARGS (extra args)
SKILLSET_SMOKE_CODEX_CMD (default: codex)
SKILLSET_SMOKE_CODEX_ARGS (extra args)

Interpret results

Reports live under .skillset-smoke/reports/<runId>/report.json.
Check steps[*].status and steps[*].details.evidence for sentinel hits.
When a step fails, inspect its stdoutPath/stderrPath for errors.
- Hook steps are labeled hook-ci and hook-cli.
- The smoke test cleans by default; re-run with --no-clean to keep state for debugging.

Triage checklist

Use this checklist in order when a run fails or evidence is missing:

Open the report JSON and find the first steps[*].status !== "ok".
If stdoutPath/stderrPath exist, read them for the error message.
Confirm the workspace and XDG paths in the report (they must be under .skillset-smoke/).
If a tool step is skipped, verify the CLI is installed and auth is valid.
If hook evidence is missing for a set, confirm the set resolves in set-load and re-run --tools hook to isolate hook output issues.
If sentinels are missing for skills, confirm the smoke test created fixtures in .skillset-smoke/workspace/.claude/skills.
Re-run with --tools hook to isolate local resolution issues before retrying full runs.

Notes

Outputs are stored under .skillset-smoke/ and are gitignored.
If the .codex/skills symlink is missing, re-create it to mirror this skill.

---name: skillset-smoke-testdescription: Run and evaluate the Skillset smoke test (aliases, sets, and skill invocation) and interpret its JSON reports. Use this when validating $skill/$set behavior or checking Claude Code/Codex headless runs.--- # Skillset Smoke Test Runner Keep this skill self-contained. If you need more detail, read `REFERENCE.md`. ## Prereqs - Ensure `bun` is available. - For full runs, ensure `claude` and `codex` CLIs are installed and authenticated. - Run from the repo root so the smoke test can find `scripts/skillset-smoke.ts`. ## Run the smoke test - Prefer the repo script so results are structured and gitignored. - Quick smoke (hook-only): - `bun run test:smoke:ci` - Hook-only (CLI mode): - `bun run test:smoke:cli` - Full run (hook + Claude + Codex): - `bun run test:smoke` ## Options - `--tools hook,claude,codex` to limit which tools run. - `--hook-mode ci|cli` to choose the hook path (repeatable or comma-separated). - `--no-clean` to preserve the sandbox workspace and XDG dirs. - `--clean-all` to wipe all smoke test artifacts (workspace + reports). - `--strict` to exit non-zero if any step fails. ## Environment overrides - `SKILLSET_SMOKE_CLAUDE_CMD` (default: `claude`) - `SKILLSET_SMOKE_CLAUDE_ARGS` (extra args) - `SKILLSET_SMOKE_CODEX_CMD` (default: `codex`) - `SKILLSET_SMOKE_CODEX_ARGS` (extra args) ## Interpret results - Reports live under `.skillset-smoke/reports/<runId>/report.json`. - Check `steps[*].status` and `steps[*].details.evidence` for sentinel hits. - When a step fails, inspect its `stdoutPath`/`stderrPath` for errors. - Hook steps are labeled `hook-ci` and `hook-cli`. - The smoke test cleans by default; re-run with `--no-clean` to keep state for debugging. ## Triage checklist Use this checklist in order when a run fails or evidence is missing: 1. Open the report JSON and find the first `steps[*].status !== "ok"`. 2. If `stdoutPath`/`stderrPath` exist, read them for the error message. 3. Confirm the workspace and XDG paths in the report (they must be under `.skillset-smoke/`). 4. If a tool step is `skipped`, verify the CLI is installed and auth is valid. 5. If `hook` evidence is missing for a set, confirm the set resolves in `set-load` and re-run `--tools hook` to isolate hook output issues. 6. If sentinels are missing for skills, confirm the smoke test created fixtures in `.skillset-smoke/workspace/.claude/skills`. 7. Re-run with `--tools hook` to isolate local resolution issues before retrying full runs. ## Notes - Outputs are stored under `.skillset-smoke/` and are gitignored. - If the `.codex/skills` symlink is missing, re-create it to mirror this skill.

Frequently asked questions