setup
/setup
Configure aigent-OS identity, priorities, authority, projects, people, and decision logic. Use when running setup, reconfiguring settings, or changing authority levels.
- Author
- wrg32786 ↗
- Repository
- aigent-os ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Configure aigent-OS identity, priorities, authority, projects, people, and decision logic. Use when running setup, reconfiguring settings, or changing authority levels.
Original author description
Configure aigent-OS identity, priorities, authority, projects, people, and decision logic. Use when running setup, reconfiguring settings, or changing authority levels.
How it works
- Entry behavior
- Interview
- Completion
- Rules
SKILL.md preview
---
name: setup
description: "Configure aigent-OS identity, priorities, authority, projects, people, and decision logic. Use when running setup, reconfiguring settings, or changing authority levels."
trigger: /setup
---
# aigent-OS setup and reconfiguration
`/start` owns the day-one onboarding arc. `/setup` is the deeper configuration flow and may also be used later to revise one section.
## Entry behavior
Read `.aigent/state.json` first.
- If state is missing or not `ready`, route through `/start` unless the operator explicitly requested advanced setup.
- If state is `ready`, ask which configuration area needs revision rather than replaying the entire interview.
- Never detect setup state by searching for placeholder prose in a Markdown file.
Before writing, set `status: setup-in-progress` while preserving any prior `completedAt`. On interruption, the next `/start` or `/setup` should resume from the last durably completed section.
## Interview
Ask one question at a time and write each completed section immediately.
### 1. Identity
Ask for the operator's role, responsibilities, preferred collaboration style, and risk posture. Update `system/00_identity.md` without replacing framework-owned doctrine.
### 2. Priorities
Ask for the top two or three active priorities, the most urgent outcome, operating mode, and blockers. Update `vault/memory/ACTIVE_PRIORITIES.md`.
### 3. Authority boundaries
Ask what the AI may handle autonomously, what needs confirmation, what is human-only, and whether spending has an escalation threshold. Update `system/12_authority_matrix.md`.
### 4. Decision logic
Ask what makes the operator accept or reject opportunities, their active-work limit, and their most common time trap. Update `system/14_decision_framework.md`.
### 5. Projects and people
For each active project, capture purpose, current state, priority, next action, and relevant people. Create or update notes under `vault/projects/` and `vault/people/`, then connect them from active priorities with wikilinks.
### 6. Specialist agents
Ask whether any specialized agents are useful now. For each accepted agent, capture name, scope, tools, model tier, escalation boundary, and success criteria. Store the definition in `vault/agents/` with valid `name:` and `tools:` frontmatter so the installer can register it in `.claude/agents/`.
## Completion
After all requested sections are durably written:
1. Summarize exactly what changed.
2. Append an idempotent setup entry to `vault/memory/SESSION_LOG.md`.
3. Set `.aigent/state.json` to:
```json
{
"schemaVersion": 1,
"status": "ready",
"completedAt": "<ISO-8601 timestamp>"
}
```
4. Write `.aigent/first-run-done` for compatibility with older installs.
5. Teach or remind the operator of `/open`, normal work, and `/close`.
Do not mark the installation ready when required writes failed.
## Rules
- One section at a time.
- Adapt to information already supplied.
- Mirror the operator's language without inventing details.
- Preserve user-authored content and make precise edits.
- Sections may be deferred explicitly.
- Reconfiguration must not erase unrelated state.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · wrg32786/aigent-os | 100 | MIT |
| HwangSlater/harness-fit | 100 | MIT |
| nesquikm/dev-process-toolkit | 100 | MIT |
| userKael/rastro | 100 | MIT |
| als-apg/osprey | 100 | BSD-3-Clause |
| dedujeong/gemba | 100 | Apache-2.0 |
| eigenwise/eigenwise-toolshed | 100 | MIT |
| awrshift/agent-memory-kit | 100 | MIT |
| lifecycle-innovations-limited/claude-ops | 100 | MIT |
Database snapshot: 13.11.2026 · package version f837c013df81 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100status
Report aigent-OS operational status. Use when checking the current operational state of aigent-OS. - 90operator-setup
Interview the AIgent operator about their business, save initial memory, and give a briefing. Use when onboarding, setting up a business, or running the first interview. - 86agent-identity-setup
Use when setting up or resetting agent SOUL, memory, skills. - 100init
Interactive setup wizard for claudekit. Scaffolds rules, hooks, and MCP server configs into the user's project. Run /claudekit:init to configure. Use when setting up a new project with claudekit or reconfiguring an existing one.