How do I install the Check Prereqs skill?

Run npx skillmds@latest add thettwe/check-prereqs 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 Check Prereqs safe to use?

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

Which AI agents work with Check Prereqs?

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 Check Prereqs free to use?

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

Who published Check Prereqs?

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

Check Prereqs by thettwe — Agent Skill

Name: Check Prereqs
Author: thettwe

Check Prereqs

Survey the machine and report which nyann features are usable right now. TRIGGER when the user says "is my machine ready for nyann", "what do I need to install", "check my setup", "do I have the right tools", "check prereqs", "audit my environment", "new machine, what's missing", "I'm on a new machine", "install nyann prereqs", "/nyann:check-prereqs". Do NOT trigger on general "what is nyann" questions — those want a docs pointer, not a machine survey. Do NOT trigger when the user is already mid-bootstrap — let the bootstrap-project skill handle that case and emit its own skip records for missing stack tools.

thettwe 990e97b 2.0 KB Updated Sep 17, 2026

File contents

check-prereqs

Read-only environment survey. Never installs anything; never mutates the filesystem. Flow:

Run bin/check-prereqs.sh. Default output is a human-readable table showing every prereq nyann touches, classified as hard (nyann exits 1 without it) or soft (feature-gated skip).
If the user passes the word json / "machine-readable" / similar, add --json so output is structured for scripting.
Exit code from the script is the signal:
- 0 → all hard prereqs present. Soft misses are informational.
- 1 → at least one hard prereq is missing. Tell the user explicitly that nyann cannot run yet, and point them at the install hint from the table.

What to do after

Soft misses aren't blockers, but each gates a specific feature. Offer to explain which feature needs which tool. Don't install anything on the user's behalf — just read the hint column back and let them decide.
If the user asks "install these for me", decline politely — nyann doesn't bulk-install system packages. Direct them to the copy-pasteable install lines in the hint column.

When to hand off

User asks "OK, now bootstrap this repo" → route to the bootstrap-project skill.
User asks "what does do in nyann?" → explain the feature(s) it gates (README has a table per soft dep).

---name: check-prereqsdescription: Survey the machine and report which nyann features are usable right now. TRIGGER when the user says "is my machine ready for nyann", "what do I need to install", "check my setup", "do I have the right tools", "check prereqs", "audit my environment", "new machine, what's missing", "I'm on a new machine", "install nyann prereqs", "/nyann:check-prereqs". Do NOT trigger on general "what is nyann" questions — those want a docs pointer, not a machine survey. Do NOT trigger when the user is already mid-bootstrap — let the bootstrap-project skill handle that case and emit its own skip records for missing stack tools.---# check-prereqsRead-only environment survey. Never installs anything; never mutates thefilesystem. Flow:1. Run `bin/check-prereqs.sh`. Default output is a human-readable table showing every prereq nyann touches, classified as **hard** (nyann exits 1 without it) or **soft** (feature-gated skip).2. If the user passes the word `json` / "machine-readable" / similar, add `--json` so output is structured for scripting.3. Exit code from the script is the signal: - `0` → all hard prereqs present. Soft misses are informational. - `1` → at least one hard prereq is missing. Tell the user explicitly that nyann cannot run yet, and point them at the install hint from the table.## What to do after- Soft misses aren't blockers, but each gates a specific feature. Offer to explain which feature needs which tool. Don't install anything on the user's behalf — just read the `hint` column back and let them decide.- If the user asks "install these for me", decline politely — nyann doesn't bulk-install system packages. Direct them to the copy-pasteable install lines in the `hint` column.## When to hand off- User asks "OK, now bootstrap this repo" → route to the `bootstrap-project` skill.- User asks "what does <tool> do in nyann?" → explain the feature(s) it gates (README has a table per soft dep).

Frequently asked questions