How do I install the Mo Setup skill?

Run npx skillmds@latest add shkarupa-alex/mo-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Mo Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Mo Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Mo Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Mo Setup?

shkarupa-alex (@shkarupa-alex) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Mo Setup by shkarupa-alex — Agent Skill

Name: Mo Setup
Author: shkarupa-alex

Mo Setup

Inspect and bring a project and its environment up to the Meta-O contract, including substantive knowledge, instructions, tooling, backend companions, and unsandboxed Codex, Claude Code, and OpenCode posture.

shkarupa-alex b7d92a6 8 files · 41.4 KB Updated Sep 17, 2026

File contents

Set up a project for Meta-O

Read Project setup contract, Backend contract, and Purpose and architecture contract completely. For a Python project also read Python QC profile completely; for a TypeScript or JavaScript project also read TypeScript QC profile. Read both for a mixed Python/TypeScript project. Read only the applicable language profiles completely.

Detect Orca through its native environment and status surface; report unsupported or ambiguous environments. Check orca/orca-cli separately from the upstream orchestration companion skill.

When watchdog readiness is in scope, check mature jq and flock dependencies separately from backend controls.

Use Orca's version-matched orca skills guide. Report the exact source separately from control discovery; an unrelated personal copy is not evidence.

Inspect knowledge, entry instructions, README, architecture reasons, backlog quality, E2E and acceptance mapping, language/build config, mature complexity and size linting, significant-code purpose, deterministic non-mutating QC, and unsandboxed Codex/Claude Code/OpenCode posture. Do not create a backend fixture document in ordinary projects.

If tracked repair is required, explain it and use a separate feature/meta-o-setup branch based on up-to-date develop; never mix setup repair into the current feature branch. Personal configuration changes require explicit confirmation.

Frequently asked questions