setup

Configures a fresh template clone by checking prerequisites and registering sibling git repos.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill setup-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/setup
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill setup-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a multi-repo agent workflow by hand means manually checking prerequisites, deciding how the clone operates, and wiring up a project registry — steps that are easy to skip or get wrong. This Skill automates first-time onboarding for a freshly cloned agent-workflow-template so the environment is verified and repos are registered consistently. ## Core Features & Use Cases - Prerequisite Verification: Checks git identity, gh CLI auth, python3, review-engine environment variables (OPENROUTER_API_KEY, ANTHROPIC_API_KEY), and reports each as ready, warning, or blocking. - Repo Discovery and Registration: Scans for sibling git repositories next to the clone and offers to register them in .cto/projects.yaml, inferring language from files like pyproject.toml or package.json. - Mechanism Deployment: Optionally pushes the template's dev-team mechanism (CLAUDE.md, hooks, scripts, personas) into selected repos via push-to-repos.sh without committing. - Use Case: After cloning the template, say "set up my environment" — the Skill checks prerequisites, asks whether to operate in place or spawn a private <project>-cto home, registers your existing repos, settles the review engine, and marks setup complete. ## Quick Start Ask the agent to set up my environment and answer its questions about operating mode and which sibling repos to register.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I set up the agent workflow template after cloning?

Open the cloned folder in Claude Code and say "set up my environment". The setup Skill runs prerequisite checks, asks how the clone should operate, discovers sibling git repos, and writes the .cto/projects.yaml registry. It also auto-fires on the first session in a fresh clone.

How do I register existing repos with the CTO setup?

The setup Skill scans the parent directory for sibling git repositories not yet registered and lets you select which to add. Each selected repo gets an entry in .cto/projects.yaml with name, path, language, and active status. Re-run /setup any time to add more repos.

What prerequisites does the agent workflow template require?

Git with configured user.name and user.email plus python3 are required and block setup if missing. The gh CLI is needed only to publish new repos, and OPENROUTER_API_KEY unlocks the optional kimi review engine. ANTHROPIC_API_KEY should be unset since the template assumes subscription auth.

Which review engine should I choose during setup?

The kimi engine via OpenRouter is recommended because it provides cross-model-family independent reviews for pennies per review, but requires OPENROUTER_API_KEY. The subagent engine runs in-session for free with no API key, and handoff runs reviews in a separate interactive Claude window.

Does setup commit changes to my dev-team repositories?

No. The push-to-repos.sh script writes CLAUDE.md, settings, hooks, scripts, and persona files into selected repos but never commits them. Committing is left to the dev-team session or the user, and dirty repos are flagged so you know other work in progress exists.

Can I re-run the setup Skill safely?

Yes, setup is idempotent. If .cto/projects.yaml already exists, it skips the operating-mode question and simply offers to register additional repos. It is the intended way to add more repos to an already-configured environment.