agentsclimarketplace

Setup

Skill vpaivag/skills/skills/setup

Configure where plan suites live and whether the plans directory is gitignored. Writes `.claude/plans-config.json` with `plansDir` (default `.claude/plans`) and `gitignore` (default `true`) keys. The planning skills (`/blueprint`, `/build`, `/qa`) read this config to resolve the plans directory, falling back to `.claude/plans` when the config is absent. Use when the user invokes `/setup`, asks to "configure the plans directory", "change where plans live", "set up the plans skill config", or wants to opt in/out of gitignoring the plans directory.From its SKILL.md

Install
npx -y skills add vpaivag/skills --skill setup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.2 KB, as published. Nobody here has run it

/setup

Write a small JSON config that the planning skills consult to find the plans directory and decide whether to manage .gitignore. This skill writes at most two files: .claude/plans-config.json and (optionally) .gitignore.

Asking questions

This skill prefers the AskUserQuestion tool for interactive prompts. If AskUserQuestion is not available (older Claude Code versions, restricted environments), fall back to plain text: print the question, list the options as a numbered list with the recommended option marked (Recommended), and wait for the user's reply (a number or the option label). The skill proceeds normally in either mode — every call site below that says "call AskUserQuestion" follows this fallback rule.

Operating mode

  • Two writes max. .claude/plans-config.json and (only if needed) an append to .gitignore. No other writes.
  • Read-only on code. This skill does not touch any source file.
  • Non-destructive on .gitignore. Never remove or rewrite existing .gitignore lines. Only append when missing.
  • Defaults are the historical path. plansDir defaults to .claude/plans; gitignore defaults to true. Users who never run /setup get the same behavior as before.

Config file contract

.claude/plans-config.json:

{
  "plansDir": ".claude/plans",
  "gitignore": true
}
  • plansDir: string, relative or absolute path. Default .claude/plans. Relative paths resolve against the project root (the repository), never the user's home ~/.claude/. Absolute paths are allowed (some users keep plans outside the repo).
  • gitignore: boolean. If true, skills ensure plansDir is in .gitignore. If false, skills do not touch .gitignore.

Phases

Phase 1 — Detect existing config

Read .claude/plans-config.json if it exists. If present:

  1. Show the current values.
  2. Ask via AskUserQuestion: "Config already exists. Reconfigure or keep as-is?" with options "Keep" (Recommended) and "Reconfigure".
  3. If "Keep", end the turn after printing the current config.
  4. If "Reconfigure", proceed to Phase 2.

If .claude/plans-config.json does not exist, proceed to Phase 2.

Phase 2 — Q&A

Ask two questions via AskUserQuestion, one at a time, recommended-answer option first.

  1. Plans directory. Options: .claude/plans (Recommended), Other (user types a path). Accept absolute or relative paths.
  2. Gitignore the plans directory? Options: Yes (Recommended), No.

Phase 3 — Write config

  1. Create .claude/ if it does not exist.
  2. Write .claude/plans-config.json with the chosen plansDir and gitignore values.
  3. If gitignore: true:
    • If a .gitignore exists at the project root and does not already contain a line matching plansDir (with optional trailing /), append <plansDir>/ to it.
    • If .gitignore does not exist, create it with that single line.
  4. If gitignore: false:
    • Do not modify .gitignore.
    • If .gitignore exists and already contains a line matching plansDir, print a note: "Your .gitignore still contains <plansDir>. Remove it manually if you want plans tracked in git."

Phase 4 — Confirm

Print a summary:

✅ Config written: .claude/plans-config.json
   plansDir: <value>
   gitignore: <true|false>

<gitignore note if applicable>

End the turn.

Constraints

  • Never write outside .claude/plans-config.json and .gitignore.
  • Never remove existing .gitignore lines.
  • Defaults must match the historical behavior (.claude/plans, gitignored).
  • Ask questions via AskUserQuestion; one question at a time; recommended-answer option first.

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.