setup

Initialize or update project context files and resolver routing.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/bcbeidel/toolkit --skill setup-bcbeidel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/bcbeidel/toolkit/tree/main/plugins/wiki/skills/setup
Command: npx skills add https://github.com/bcbeidel/toolkit --skill setup-bcbeidel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Initialize or update project context and documentation scaffolding for new or existing projects, ensuring a consistent starting point and maintenance workflow.

Core Features & Use Cases

  • Create and maintain essential project context files (e.g., AGENTS.md, CLAUDE.md) and a routing pointer when needed.
  • Migrate legacy markers and prepare guided workflows for working agreements and resolver setup.
  • Support idempotent re-runs to repair or verify an existing setup without duplicating content.

Quick Start

Run /wiki:setup to scaffold or repair project context in the repository.

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize project context files like AGENTS.md and CLAUDE.md for a new repository?

To initialize project context, run the setup command to scaffold required documentation pointers like AGENTS.md and CLAUDE.md, establish resolver routing, and create guided working agreements for your repository.

What is the best way to repair existing project documentation scaffolding without duplicating content?

Repairing project documentation scaffolding requires an idempotent setup process that verifies existing AGENTS.md and CLAUDE.md pointers, migrates legacy markers, and safely re-runs without duplicating content.

When do I need to update CLAUDE.md pointers and resolver routing in my project?

You need to update CLAUDE.md pointers and resolver routing when starting a new project or repairing an existing setup to ensure documentation pointers remain correct and working agreements are properly configured.

Can I re-run project context setup multiple times without breaking my existing working agreements?

Yes, the project context setup supports idempotent execution, meaning you can safely re-run it to verify or repair an existing configuration without duplicating content or overwriting working agreements.

How does migrating legacy markers work when updating project context documentation?

Migrating legacy markers during project context setup updates old documentation references to the current AGENTS.md and CLAUDE.md pointer format, ensuring resolver routing and working agreements remain valid.