install

Initialize o-m-cc project files and agents after official setup.

6|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kok1eee/o-m-cc --skill install-kok1eee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install
Source: https://github.com/kok1eee/o-m-cc/tree/main/skills/install
Command: npx skills add https://github.com/kok1eee/o-m-cc --skill install-kok1eee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, opinionated setup that adds o-m-cc specific files and settings to a project after the official /init, preventing manual configuration errors and missing runtime files.

Core Features & Use Cases

  • CLAUDE.md augmentation: Detects an existing CLAUDE.md and appends an o-m-cc workflow section if absent.
  • Workspace preparation: Creates a plan/ directory, places the default sisyphus agent under .claude/agents, and adds o-m-cc runtime entries to .gitignore.
  • Permissions and plugin management: Merges recommended permissions into .claude/settings.json without overwriting existing settings and installs suggested plugins if missing.
  • Use case: Use when onboarding an existing repository or after running the official /init to ensure the project is ready for o-m-cc Sisyphus workflows.

Quick Start

Run the o-m-cc install flow to append the workflow to CLAUDE.md, create plan/, deploy the sisyphus agent, merge recommended permissions, and add runtime ignores.

Frequently Asked Questions about install

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

FAQPage Schema
How do I set up an o-m-cc project after running the official /init in Claude Code?

To set up an o-m-cc project, this Skill automates the initialization and configuration of project files and agents. It appends a workflow section to CLAUDE.md, creates a plan/ directory, deploys the sisyphus agent, and merges permissions into settings.json.

What is the best way to configure Claude Code agents and permissions without overwriting existing settings?

Configuring Claude Code permissions safely involves merging recommended settings into settings.json without overwriting existing configurations. This approach ensures the sisyphus agent and plan directories are deployed alongside your current project setup.

Do I need an existing CLAUDE.md to initialize o-m-cc project files?

Yes, an existing CLAUDE.md is required to initialize o-m-cc project files. The setup process detects the existing CLAUDE.md and appends an o-m-cc workflow section if absent, requiring repository write access to complete.

Can I automate the installation of suggested plugins and .gitignore entries for my Claude Code project?

Yes, you can automate plugin installation and .gitignore entries for your Claude Code project. The setup flow installs suggested plugins if missing and adds o-m-cc runtime entries to .gitignore, provided you have access to claude plugin tooling.

Why does my o-m-cc Sisyphus workflow setup fail after the official repository initialization?

Your o-m-cc Sisyphus workflow setup may fail if you lack repository write access or an existing CLAUDE.md file. The configuration process strictly requires these prerequisites to merge settings.json permissions and deploy the default sisyphus agent correctly.