setup

Configure a new harness environment by detecting stacks and generating configuration.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/special-place-administrator/citadel_codex --skill setup-special-place-administrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/special-place-administrator/citadel_codex/tree/main/skills/setup
Command: npx skills add https://github.com/special-place-administrator/citadel_codex --skill setup-special-place-administrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

First-run experience for new projects: the harness is configured, stacks detected, state scaffolding created, configuration generated, a real demo task executed, and a concise reference card of all skills printed.

Core Features & Use Cases

  • Auto-detect project language and framework from repo files (tsconfig.json, package.json, pyproject.toml, etc.)
  • Scaffold the .citadel/ state directory and generate a ready-to-run config.json
  • Run a tiny demo task to showcase the workflow and onboard users quickly
  • Print a compact reference card listing available skills after setup

Quick Start

Run do setup in a new project to configure the harness and generate the initial state

Frequently Asked Questions about setup

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

FAQPage Schema
How do I automate project onboarding and generate configuration files for a new setup?

Automating project onboarding involves running a setup flow that detects the language stack, scaffolds the .citadel/ state directory, and generates a config.json file. This provides a ready-to-run initial environment for fresh projects.

How does stack detection work for new repositories during first-run configuration?

Stack detection works by scanning repository files like tsconfig.json, package.json, and pyproject.toml to identify the project language and framework. This mechanism ensures the generated configuration matches the detected tech stack automatically.

What is the best way to scaffold a harness environment and run an initial demo task?

The best way to scaffold a harness environment is executing a single setup flow that creates the state directory, generates configuration, and runs a tiny demo task. This showcases the workflow and prints a reference card of available skills.

Does the setup flow support optional scripts, references, and assets during initial onboarding?

The setup flow supports optional scripts, references, and assets during initial onboarding. This allows extending the scaffolding and configuration generation beyond the base state directory and config.json outputs.

What is included in the reference card printed after configuring a new harness environment?

The reference card printed after setup provides a concise list of all available skills. It serves as a quick-start guide delivered immediately following the demo task execution during the first-run experience.