Skip to content
Skills Library
Other · Automation

setup

/setup

Setup routing and environment configuration. Use for "setup", "configure", and "get started".

Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Setup routing and environment configuration. Use for "setup", "configure", and "get started".

Triggers from the description

setupconfigureget started
Original author description

Setup routing and environment configuration. Use for "setup", "configure", and "get started".

How it works

  1. Skill: setup
  2. When to Use
  3. Setup Modes
  4. Setup Steps
  5. Project Types
  6. Output Format
  7. Constraints
Original SKILL.md headings · 182 lines, 660 words
SKILL.md preview
---
name: setup
description: Setup routing and environment configuration. Use for "setup", "configure", and "get started".
trigger: /oma:setup
---

## Skill: setup

Set up development environments and configurations.

## When to Use

- New project initialization
- Environment configuration
- First-time setup
- Onboarding to a project

## Setup Modes

### `/oma:setup new`
Create a new project structure.
- Initialize files
- Configure tools
- Set up dependencies

### `/oma:setup existing`
Configure for existing project.
- Detect project type
- Configure tools
- Verify setup

### `/oma:setup doctor`
Diagnose setup issues.
- Check dependencies
- Verify configurations
- Report status

### `/oma:setup mcp`
Configure MCP servers.
- List available servers
- Configure connections
- Test integrations

## Setup Steps

### 1. Detect Environment
- Project type
- Language/framework
- Existing configs

### 2. Check Prerequisites
- Required tools installed
- Permissions correct
- Network access

### 3. Configure
- Create config files
- Set up dependencies
- Configure tools

### 4. Verify
- Run basic checks
- Test configuration
- Confirm working

## Project Types

### JavaScript/TypeScript
- package.json
- tsconfig.json
- eslint/prettier
- Jest/Vitest

### Python
- requirements.txt
- pyproject.toml
- pytest
- virtual env

### Rust
- Cargo.toml
- rustfmt.toml
- clippy

### Multi-language
- Nx monorepo
- Turborepo
- Lerna

## Output Format

```
## Setup: {project}

### Environment
- **Type:** {project type}
- **Location:** {path}
- **Existing config:** {yes/no}

### Prerequisites
| Check | Status |
|-------|--------|
| {check} | ✅/❌ |

### Configuration
| Item | Status | Notes |
|------|--------|-------|
| {config} | ✅ | {notes} |

### Files Created
- {file 1}
- {file 2}

### Verification
```bash
{verify command}
```

### Next Steps
1. {step 1}
2. {step 2}
```

## Constraints

- Don't overwrite without backup
- Preserve existing config
- Verify after each step
- Document what was done
- Make setup repeatable

<Tool_Usage>
- **executor**: Primary agent for running the actual setup steps — executor creates files, installs dependencies, runs commands
- **analyst**: Use when the project type cannot be auto-detected — analyst determines what kind of project this is and what it needs
- **architect**: Consult when setup involves architectural decisions (e.g., choosing between monorepo vs. polyrepo, choosing a framework)
- **verifier**: After setup completes, use verifier to confirm the environment is healthy and ready for development
- **Direct Bash tools**: For reading existing config files, running diagnostics, and executing setup commands directly (not for spawning agents)
</Tool_Usage>

<Why_This_Exists>
OMA operates inside Auggie's CLI and needs a reliable way to initialize new projects or configure existing ones for use with OMA's orchestration tools. Setting up `.oma/`, `plugins/oma/`, MCP configurations, and skill directories is a prerequisite for most orchestration modes. Rather than scattering setup logic across agents, setup provides a dedicated entry point so the environment is correctly initialized before ralph, ultraqa, or team modes run — preventing failures from missing state directories or unconfigured MCP servers.
</Why_This_Exists>

<Examples>

### Good Usage

**First-time OMA setup on a new Auggie project:**
```
User: "/oma:setup"
OMA: [Detects: new project, no .oma directory]
OMA: [Creates .oma/state.json, .oma/notepad.json, .oma/plans/]
OMA: [Configures plugins/oma/ if not present]
OMA: [Runs setup doctor: MCP server reachable, Auggie CLI version check]
OMA: [Result: environment ready for /oma:ralph, /oma:team, etc.]
```

**Configure OMA on an existing project:**
```
User: "/oma:setup existing"
OMA: [Detects: existing TypeScript project with tsconfig.json]
OMA: [Checks for .oma/ — not found]
OMA: [Creates .oma/ directory structure]
OMA: [Writes initial .oma/state.json with project type]
OMA: [Result: OMA now aware of the project]
```

### Bad Usage

**Re-running setup on an already-configured environment:**
```
User: "/oma:setup"
OMA: [Detects: .oma/ already exists, .oma/state.json valid]
OMA: [Overwrites existing state, destroying in-progress mode state]
```
→ Use `/oma:setup doctor` instead to verify without re-initializing.

**Setup as a substitute for manual environment understanding:**
```
User: "/oma:setup" on a highly custom monorepo with non-standard tooling
OMA: [Auto-detects wrong project type due to non-standard structure]
OMA: [Misconfigures plugins/oma/ paths]
OMA: [Modes fail with confusing errors]
```
→ Use `/oma:setup doctor` first to see what was detected, then manually configure if needed.
</Examples>

Versions

RepositoryScoreLicence
This page · r3dlex/oh-my-auggie100Apache-2.0
HwangSlater/harness-fit100MIT
nesquikm/dev-process-toolkit100MIT
userKael/rastro100MIT
als-apg/osprey100BSD-3-Clause
dedujeong/gemba100Apache-2.0
eigenwise/eigenwise-toolshed100MIT
awrshift/agent-memory-kit100MIT
lifecycle-innovations-limited/claude-ops100MIT

Database snapshot: 13.11.2026 · package version 41723c511a68 (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

  • 100react-context-setup
    Configure react context setup operations. Auto-activating skill for Frontend Development. Triggers on: react context setup, react context setup Part of the Frontend Development skill category. Use when working with react context setup functionality. Trigger with phrases like…
  • 100arn-spark-dev-setup
    This skill should be used when the user says "dev setup", "arn spark dev setup", "development environment", "configure dev environment", "dev container", "configure CI", "set up CI", "onboard developer", "developer setup", "set up docker", "configure development", "how do I set…
  • 100woo-setup
    Install WooCommerce, configure the development stack, and set up a local dev environment with WP-CLI, Docker, or wp-env. Use when setting up a new WooCommerce project or development environment.
  • 100corezoid-init
    Corezoid environment setup specialist. Use when the user wants to connect to Corezoid, set up credentials, authenticate, pull a project, configure the environment, or start working with a Corezoid project for the first time. Activate when the user says "init", "setup", "connect…
  • 100github-project-setup
    Configure github project setup operations. Auto-activating skill for Enterprise Workflows. Triggers on: github project setup, github project setup Part of the Enterprise Workflows skill category. Use when working with github project setup functionality. Trigger with phrases like…
  • 93neqsim-setup
    Configure and verify the NeqSim task environment: task root, document root, Word report template, and health of Java, the NeqSim JAR, the MCP server and the neqsim CLI. USE WHEN: a user runs /neqsim-setup, asks to set or show the task/document folder, work path or report…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.