setup

Initialize the .geas runtime directory and generate project rules.

15|4|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/choam2426/geas --skill setup-choam2426
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/choam2426/geas/tree/main/plugin/skills/setup
Command: npx skills add https://github.com/choam2426/geas --skill setup-choam2426

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects need a reliable, reproducible runtime and policy scaffold before AI agents can execute governed work. Manual bootstrapping of runtime state, health checks, and agent rules is error-prone and interrupts onboarding or first-run workflows. This Skill automates those first-time tasks so teams can start missions consistently.

Core Features & Use Cases

  • Runtime bootstrap: Create the .geas/ directory structure including state, memory/agents, and recovery subfolders.
  • Initial state & health: Generate .geas/state/run.json (versioned run state) and .geas/state/health-check.json with all health signals computed.
  • Project rules and conventions: Detect project stack and commands, generate or update .geas/rules.md with a Code section, and optionally append .geas/ to .gitignore.
  • Safe idempotence & validation: Commands are safe no-ops when artifacts already exist and the CLI enforces schema checks.
  • Use case: Onboarding a new repository or preparing an existing repo for Geas-driven missions so automated agents can operate under a locked contract and evidence pipeline.

Quick Start

Run the setup skill to initialize the .geas runtime, generate rules.md from detected project conventions, and optionally add .geas/ to .gitignore.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I bootstrap a Geas runtime directory and configuration for an existing repository?

Initialize the Geas runtime by running the setup skill, which creates the .geas directory structure, generates state and health-check files, and prepares rules.md based on detected project conventions.

What is the purpose of the .geas state and health-check files when preparing for agent missions?

The .geas state and health-check files provide a reproducible runtime scaffold, recording versioned run state and computed health signals so AI agents can execute governed work consistently.

Do I need to manually update .gitignore before initializing the project runtime config?

You do not need to manually update .gitignore; the setup skill optionally appends the .geas directory to .gitignore automatically while generating project rules and conventions.

Is the project runtime setup safe to run multiple times on the same codebase?

The runtime setup is safe to run multiple times because commands act as idempotent no-ops when artifacts already exist, and the CLI enforces schema validation to ensure safe re-runs.

What does project convention detection generate when bootstrapping a new code repository?

Project convention detection generates a .geas/rules.md file containing a Code section that captures the detected project stack and commands, preparing the repository for automated agent missions.