setup
One-time bootstrap of a personal ALBA agent system - asks 7 discovery questions, then generates CLAUDE.md, the memory tree, skills, hooks, rules and .claude/settings.json. Use when the user explicitly types /setup, has just cloned ALBA, and has no CLAUDE.md yet. Do NOT use to add a single skill, hook or rule to a working setup (use /extend), and never run it against an already-configured system - it rewrites CLAUDE.md, settings.json and the memory files.
onurpolat05 · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add onurpolat05/ALBA --skill setupAbout this skill
name: setup description: One-time bootstrap of a personal ALBA agent system - asks 7 discovery questions, then generates CLAUDE.md, the memory tree, skills, hooks, rules and .claude/settings.json. Use when the user explicitly types /setup, has just cloned ALBA, and has no CLAUDE.md yet. Do NOT use to add a single skill, hook or rule to a working setup (use /extend), and never run it against an already-configured system - it rewrites CLAUDE.md, settings.json and the memory files. context: inline effort: medium disable-model-invocation: true allowed-tools: [Read, Write, Edit, Glob, Bash, AskUserQuestion]
ALBA Interactive Setup
Create a personalized AI agent system through collaborative discovery. Ask, don't assume.
Why
disable-model-invocation: true: this skill overwritesCLAUDE.md,.claude/settings.jsonand the wholememory/tree. Nothing here should ever fire because a prompt sounded vaguely like "help me get set up". The flag restricts it to an explicit/setupfrom the user, and it also keeps the skill out of scheduled-task triggers and out of subagent preloading — both places where an accidental run would be invisible until the damage was done.
Phase 1: Discovery (ask ONE question at a time)
Show progress with each question: "(1/7)", "(2/7)", etc.
Q1 - Role (1/7): "Let's build your ALBA agent! What's your primary role?" Options: Software Developer, Project Manager, Designer, Content Creator, Researcher, Business/Founder, Other
Q2 - Daily Work (2/7): "What takes up most of your time daily?" (allow multiple) Options: Writing/reviewing code, Managing projects, Communication, Research, Content creation, Email/calendar, Design, Other
Q3 - Pain Points (3/7): "What frustrates you most in your workflow?" Options: Too many tools, Email overload, Losing track of tasks, Repetitive work, Scattered info, Losing context, Other
Q4 - Tools (4/7): "Which tools do you use regularly?" (allow multiple) Options: GitHub, Trello, Notion, Gmail, Slack, Google Calendar, Linear, Obsidian, Other
Q5 - Automation Goals (5/7): "What would you like to automate or improve?" Free text or: Task organization, Email categorization, Research, Content creation, Team updates, Meeting notes
Q6 - Technical Level (6/7): "How comfortable are you with technical setup?" Options: Beginner (guide me), Intermediate (can edit configs), Advanced (full control)
Q7 - Setup Scope (7/7): "How do you want to start?" Options: Minimal (essentials only), Standard (recommended), Full (everything)
Phase 2: Create Structure
2a. Core Structure (always created)
Create directories and files from templates:
memory/
├── state/
│ ├── dashboard.md # from templates/memory/dashboard.md.template
│ └── todo.md # from templates/memory/todo.md.template
├── knowledge/
│ ├── learnings.md # from templates/memory/learnings.md.template
│ ├── preferences.md # from templates/memory/preferences.md.template
│ └── errors.md # create with header: "# Error Patterns\n\nAuto-recorded error patterns and solutions.\n"
├── projects/ # empty, ready for project contexts
└── daily/ # empty, session logs go here
.claude/
├── docs/
│ ├── memory-system.md # from templates/claude/memory-system.md.template
│ ├── decision-protocol.md # from templates/claude/decision-protocol.md.template
│ ├── quality-gates.md # from templates/claude/quality-gates.md.template
│ ├── memory-compatibility.md # from templates/claude/memory-compatibility.md.template
│ └── loop-integration.md # from templates/claude/loop-integration.md.template
├── agents/
│ └── planner.md # from templates/agents/planner.md
└── rules/ # rules auto-load from here (see 2e)
One doc per *.md.template in templates/claude/ (excluding CLAUDE.md.template, which is
handled in Phase 3). Generate every one of them, and never list a doc in CLAUDE.md that has no
template behind it — /end links to memory-compatibility.md, so a setup that skips it leaves a
dead link in a skill the user runs daily. The same applies to planner.md: the "Plans (Planner
Agent)" section of quality-gates.md assumes that agent exists.
Naming: files under templates/claude/ and templates/memory/ carry a .template suffix that
gets dropped on copy. Files under templates/agents/ and templates/rules/ do not — copy those
as-is, no rename.
2b. Skills (scope-based)
All nine skills already ship in .claude/skills/. Scope decides which ones get listed in the
generated CLAUDE.md Skills table — the rest stay on disk and can be surfaced later with /extend.
Minimal (core loop): /start, /end, /status, /extend
Standard adds: /research, /reflect, /weekly-review, /create-skill
Full adds: everything above, plus walk the user through the remaining skills and any custom ones they describe.
/setup itself is always present but is not listed as a day-to-day skill — it is a one-time
bootstrap.
If user selected "Minimal" - note: "Core skills (/start, /end, /status, /extend) are ready. Use /extend anytime to add /research, /reflect, /weekly-review, or custom skills."
2c. Hooks (scope-based)
Copy hook scripts from templates/hooks/ to .claude/hooks/, dropping the .template suffix
(bash-validator.sh.template → bash-validator.sh), then make them executable.
Minimal hooks (always):
bash-validator.sh(PreToolUse → Bash) - blocks dangerous commands
Standard hooks (adds):
session-start.sh(SessionStart) - load dashboard on startmemory-check.sh(Stop) - remind to save stateerror-logger.sh(PostToolUse → Bash + PostToolUseFailure) - log error patterns from any toolpre-compact.sh(PreCompact) - preserve context before compactionsession-end.sh(SessionEnd) - leave a dated trace in today's log even when/endis skipped