Unslop Text
JCarterJohnson/vibecoded-design-tells
Strips the cues that make prose read as AI-generated and forces a deliberate human voice instead of the model's default register.
One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you.
Install Kit Setup
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install chrisblattman/claudeblattman kit-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .claude/skills/kit-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .claude/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install chrisblattman/claudeblattman kit-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .agents/skills/kit-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .agents/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install chrisblattman/claudeblattman kit-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .cursor/skills/kit-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .cursor/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/chrisblattman/claudeblattman.git --path plugins/starter-kit/skills/kit-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install chrisblattman/claudeblattman kit-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .gemini/skills/kit-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .gemini/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install chrisblattman/claudeblattman kit-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .github/skills/kit-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .github/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add chrisblattman/claudeblattman --skill kit-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install chrisblattman/claudeblattman kit-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisblattman/claudeblattman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/starter-kit/skills/kit-setup .opencode/skills/kit-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "kit-setup" agent skill from https://github.com/chrisblattman/claudeblattman/tree/main/plugins/starter-kit/skills/kit-setup into .opencode/skills/kit-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kit-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
kit-setup- GitHub stars
- 463
- Token cost
- ~1.2k tokens
- SKILL.md length
- 635 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you.
- Works in 2 steps: Engines → Personalize (optional; offer once)
- Tasks that involve Project scaffolding
- SKILL.md covers Phase 1 — Engines, Phase 2 — Personalize…, Finish — report in plain… and Re-running
- Calls bash
What it does
Kit Setup is an agent skill from chrisblattman/claudeblattman. One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you. Safe to re-run anytime.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Project scaffolding. The repository describes itself as: Claude Code for academics — skills, agents, and setup guides. The licence is MIT.
When your agent uses it
- Tasks that involve Project scaffolding
Example prompts
- “/kit-setup”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 12e14d4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Kit Setup loads about 1.2k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 635 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from chrisblattman/claudeblattman at commit 12e14d4, republished under its MIT licence (© chrisblattman). 635 words, ~1,239 tokens.
Download SKILL.mdSave it as
.claude/skills/kit-setup/SKILL.md (or your agent's skills folder).- name
- kit-setup
- description
- One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you. Safe to re-run anytime.
Kit Setup
Everything in this kit works on Claude alone. This skill records which optional extra engines exist on this machine, so other kit skills can offer second opinions. Detect, then confirm. Never ask the user what subscriptions or plans they have, and never list, describe, or ask about tools that weren't detected.
Phase 1 — Engines
1. Detect
One Bash call:
command -v codex; command -v gemini; date +%Y-%m-%dFor each CLI found, run a quick <tool> --version; if that fails, say it looks installed but isn't currently working, record it as unavailable, and move on — don't troubleshoot here. Version output only means "detected," not "usable."
2. Confirm each FOUND tool, in plain language
One short yes/no question per tool that was found — and nothing about tools that weren't:
- codex: "I found the Codex CLI installed — want me to use it for second opinions and research? (yes/no)"
- gemini: "I found the Gemini CLI installed — want me to use it for second opinions and very long documents? (yes/no)"
If nothing was found, skip the questions entirely. Either way, close Phase 1 with one line: "If you later install the Codex or Gemini CLI, run /kit-setup again."
3. Smoke-test each accepted tool
For each detected tool the user accepts, create one private temp directory with mktemp -d, then run one tiny smoke test through the shipped wrapper:
smoke_dir="$(mktemp -d)"
printf 'Reply with exactly: starter-kit-ok\n' | bash "${CLAUDE_PLUGIN_ROOT}/scripts/codex-run.sh" "$smoke_dir/codex.txt" light
printf 'Reply with exactly: starter-kit-ok\n' | bash "${CLAUDE_PLUGIN_ROOT}/scripts/gemini-run.sh" "$smoke_dir/gemini.txt"If the wrapper succeeds and the output is non-empty, mark the engine available: true. If it fails, mark it unavailable but preserve what happened, for example { "available": false, "detected": true, "auth_unverified": true }. Keep the user-facing message plain: "I found Codex/Gemini, but it did not answer a test prompt yet. Everything still works on Claude."
4. Write the config
Target: ~/.claude/starter-kit/engines.json. Run mkdir -p ~/.claude/starter-kit first. If the file already exists, Read it and preserve any fields you don't recognize — newer kit versions may have added some. Schema (full contract: ${CLAUDE_PLUGIN_ROOT}/references/engines-contract.md):
{
"schema_version": 1,
"codex": { "available": true },
"gemini": { "available": false },
"oracle": { "available": false },
"paste_loop": ["chatgpt", "gemini"],
"updated": "<today, YYYY-MM-DD>"
}available: trueonly if the CLI was detected, the user said yes, and the smoke test returned a non-empty answer.- If the user says no to an installed tool, write
{ "available": false, "user_declined": true }so a re-run doesn't quietly switch it back on. paste_loop: write the default shown above on first write; keep any existing value on re-runs.oracle: always write{ "available": false }— the field is reserved for a future release; this version doesn't probe or enable it.
Show full SKILL.md (250 more words)Show less
Phase 2 — Personalize (optional; offer once)
Ask once: "Want to spend two minutes personalizing how I write for you? Five quick questions — totally skippable."
If yes, ask one at a time, conversationally:
- What kind of work will you mostly use this for — and what's your role or field?
- How do you like answers — short and direct, or thorough and explained?
- What annoys you in AI writing? (buzzwords, bullet overload, hedging…)
- How formal should drafts be by default?
- Anything I should always do — or never do?
Then write ~/.claude/starter-kit/my-preferences.md: start from the template at ${CLAUDE_PLUGIN_ROOT}/references/prompt-preferences-TEMPLATE.md and fill it in from their answers. If the template is missing, write a simple file with one short section per question. If they skip, say they can run /kit-setup again anytime — and don't offer a second time this run.
Finish — report in plain language
Two or three sentences, no jargon, no JSON. Pattern:
"You're set up. Everything runs on Claude — that's the normal setup and it all works."
Add one sentence per enabled engine (e.g. "Codex is also connected, so you can ask it for second opinions with /codex.") and one if preferences were saved. If nothing extra was found, the first sentence is the whole report.
Re-running
Safe anytime. Re-detect and update engines.json: a newly installed tool gets confirmed (Phase 1, step 2) and added; a removed one gets marked unavailable; unknown fields and paste_loop are preserved. If my-preferences.md already exists, offer to update it rather than starting over.
© chrisblattman, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/starter-kit/skills/kit-setup of chrisblattman/claudeblattman.
Open the folder on GitHubat commit 12e14d4
Compare with similar skills
Kit Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Kit Setup this skillchrisblattman/claudeblattman | 463 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Unslop TextJCarterJohnson/vibecoded-design-tells | 508 | — | ~3.5k | Automated safety check: Pass | Custom licence | |
| Gapgraph-robots/graph-as-policy | 155 | — | ~3.3k | Automated safety check: Pass | MIT | |
| Nodejs CLI Best Practiceslirantal/nodejs-cli-apps-best-practices | 4.1k | — | ~2k | Automated safety check: Pass | CC-BY-SA-4.0 | |
| Scaffoldcodewithmukesh/dotnet-claude-kit | 751 | — | ~1.7k | Automated safety check: Pass | MIT | |
| Codegen TransformComfy-Org/ComfyUI_frontend | 2.1k | — | ~2k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Gap
graph-robots/graph-as-policy
Program robots with GaP (graph-as-policy) — compile natural-language tasks into typed, verified robot skill graphs and run them on simulators or real robots.
Nodejs CLI Best Practices
lirantal/nodejs-cli-apps-best-practices
Guide and audit Node.js CLI application development against 41 established best practices covering UX, distribution, interoperability, accessibility, testing, error handling, development setup…
Scaffold
codewithmukesh/dotnet-claude-kit
Architecture-aware feature scaffolding for .NET 10 projects.
Codegen Transform
Comfy-Org/ComfyUI_frontend
Transforms raw Playwright codegen output into ComfyUI convention-compliant tests.
Hier Config New Driver
netdevops/hier_config
A skill your agent uses when adding hierconfig support for a new network platform or operating system — creating a platform driver, registering a new Platform enum member, or scaffolding driver…
More from chrisblattman/claudeblattman
All 10 skills in this repoAsk Agents
chrisblattman/claudeblattman
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said.
Council
chrisblattman/claudeblattman
Dispatch a small panel of critic agents in parallel on a plan, draft, or decision, then synthesize their raw critiques in a separate fresh-context pass.
Prompt
chrisblattman/claudeblattman
Turn a rough request into a clear, structured prompt, show it, then run it.
Prompt
chrisblattman/claudeblattman
Turn a rough, dictated, or ambiguous request into a clear, structured task, then carry it out.
Review Plan
chrisblattman/claudeblattman
Review a proposed plan with a single-pass structured critique and a clear verdict.
Review Plan
chrisblattman/claudeblattman
Stress-test a plan before acting on it. An agent skill from chrisblattman/claudeblattman.
Related
Categories
Questions about Kit Setup
What does Kit Setup do?
One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you. Kit Setup is an agent skill from chrisblattman/claudeblattman. One-time starter-kit setup: detects optional AI engines (Codex, Gemini), confirms each with you, writes the engines config, and optionally personalizes how Claude writes for you.
When should I use Kit Setup?
Kit Setup fits situations like: tasks that involve Project scaffolding.
How do I install Kit Setup in Claude Code?
Run `npx skills add chrisblattman/claudeblattman --skill kit-setup -a claude-code`. Or copy the skill folder (plugins/starter-kit/skills/kit-setup in chrisblattman/claudeblattman) into .claude/skills/kit-setup in your project. Claude Code loads it when a task matches its description.
How do I install Kit Setup in Codex?
Run `npx skills add chrisblattman/claudeblattman --skill kit-setup -a codex`. Or copy the skill folder (plugins/starter-kit/skills/kit-setup in chrisblattman/claudeblattman) into .agents/skills/kit-setup in your project. Codex loads it when a task matches its description.
Can I use Kit Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add chrisblattman/claudeblattman --skill kit-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kit-setup, .gemini/skills/kit-setup, .github/skills/kit-setup and .opencode/skills/kit-setup in your project.
What does Kit Setup need to run?
Going by SKILL.md and its folder, Kit Setup needs the command-line tools its instructions call (bash).
Does Kit Setup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Kit Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Kit Setup use?
Kit Setup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Kit Setup use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Kit Setup?
Skills that share tags, products or a category with Kit Setup: Unslop Text (JCarterJohnson/vibecoded-design-tells, 508 stars), Gap (graph-robots/graph-as-policy, 155 stars), Nodejs CLI Best Practices (lirantal/nodejs-cli-apps-best-practices, 4.1k stars) and Scaffold (codewithmukesh/dotnet-claude-kit, 751 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kit Setup?
chrisblattman (a GitHub user) maintains it in chrisblattman/claudeblattman, which has 463 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on June 14, 2026.
Source: chrisblattman/claudeblattman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.