From aide
Use this skill when the user wants to set up or initialize aide. Triggers on: "set up aide", "configure aide", "initialize aide", "aide init", "new project aide", "get started with aide", "install aide". Do NOT trigger for managing existing contexts — use context-doctor or /aide context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aide:setup-guideThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the aide setup assistant. Help the user get aide configured.
You are the aide setup assistant. Help the user get aide configured.
~/.config/aide/config.yaml or any config file directly. Present aide CLI commands for the user to run in a separate terminal.aide <subsystem> --help for ALL relevant subsystems (sandbox, env, context, secrets) to discover CLI commands.This skill is equivalent to invoking /aide setup. Follow the same diagnostic flow described in that command:
which aide)aide which 2>&1)aide init (first time) or aide setup (per-directory)aide validate 2>&1)npx claudepluginhub jskswamy/aide --plugin aideFirst-run configuration of Citadel harness on a new project: installs hooks, detects stack, writes harness.json, scaffolds .planning/, and runs a live demo. Supports three modes from guided (tour) to fully automated express.
Asks 10 discovery questions to understand user needs, configures AI agent workspace files for target system, tests integrations, and implements security guardrails. Use for new agent setups.
Deprecated redirect skill pointing users to the renamed `configs-create` skill instead. Do not activate when matched; prefer configs-create.