project-builder
Use when creating a new skill, MCP server, or CLI tool project.
What this skill does
# Project Builder
## Step 0: Challenge
Before scaffolding, research and challenge:
1. What tools/APIs already exist in this domain? Check installed CLIs, existing skills, MCP servers.
2. Does this need code, or does a SKILL.md with raw commands suffice?
3. What's the minimum that solves the actual problem?
Present findings to user with recommendation. If no scaffold needed → suggest alternative, STOP.
## Step 1: Discovery
AskUserQuestion (single call, two questions):
1. question: "What type of project?" header: "Type" options: Skill, MCP server, CLI tool
2. question: "Which license?" header: "License" options: MIT (Recommended), Apache 2.0
If type is MCP server or CLI tool, ask:
1. question: "Should this also be a Claude Code plugin?" header: "Plugin" options: Yes, No (Recommended)
Then ask conversationally, one at a time:
1. "What should the project be called? Use kebab-case, e.g. `my-tool`."
2. "Where should the project be created? Use an absolute or repo-relative directory. Default: current directory."
3. "In one sentence, what problem does this solve?"
4. "What are the 2-3 key things it should do?"
Set `${TYPE}` = skill|mcp|cli, `${NAME}`, `${LICENSE}`, `${OUTPUT_DIR}`, `${PROBLEM}`, `${CAPABILITIES}`.
Set `${PLUGIN_FLAG}`:
- `skill` -> empty string, plugin is implicit
- `mcp` or `cli` with Plugin=Yes -> `--plugin`
- `mcp` or `cli` with Plugin=No -> empty string
## Step 2: Create project structure
```bash
python3 ./builder-project/project_builder/build_project.py ${TYPE} ${NAME} ${OUTPUT_DIR} ${PLUGIN_FLAG}
```
Creates: full directory tree with template files, git repo, verified tests + lint.
If script exits non-zero: show error output, `STOP`.
## Step 3: Fill template files
Using discovery answers, fill: README.md, DEVELOPMENT.md, TESTING.md, CHANGELOG.md, LICENSE, TODO.md, ARCHITECTURE.md, CLAUDE.md (`## Tech Stack` + `## Project Structure`). Type-specific: SKILL.md stub / server.py docstring / cli.py help.
Only fill `.claude-plugin/marketplace.json` when plugin scaffold exists.
Then scan `${OUTPUT_DIR}` for sibling directories containing `SKILL.md`:
- If none: skip silently
- If 1-4: offer multi-select via AskUserQuestion
- If >4: list names and ask for exact comma-separated directory names
- Empty input or `none`: skip
- Unknown name: show error and ask again
- Create relative symlinks into `${OUTPUT_DIR}/${NAME}/.claude/skills/`
- If a symlink already exists: keep it, do not overwrite
## Done
Show tree. Suggest: invoke building-skills / mcp-builder / cli-tool-builder next.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.