omega-loops-agents

Edits built-in agent prompts and templates for the Sage, Muse, and Omega loop.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill omega-loops-agents-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omega-loops-agents
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/omega-loops-agents
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill omega-loops-agents-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Rewriting the built-in agent prompts in the Omega Loops Rust codebase risks breaking the Sage → Muse → Omega loop contract, stale compiled-in binaries, and failing snapshot tests. This Skill provides the file map, loop contract, workflow, and pitfalls needed to edit agent prompts safely. ## Core Features & Use Cases - Agent prompt editing: Guides changes to crates/omega_repo/src/agents/{omega,muse,sage}.md while preserving YAML frontmatter, handlebars blocks, and tool lists. - Template maintenance: Covers shared wrapper, doom-loop, todo, retry, summary-frame, and title-generation templates under templates/. - Verification workflow: Specifies exact cargo test commands, insta snapshot acceptance, binary rebuild via scripts/dev-omega.sh, and porcelain title checks. - Use Case: A developer wants to make the agents sound more enterprise-grade; the Skill ensures role boundaries stay intact, snapshots are updated with INSTA_UPDATE=1, and the rebuilt binary shows the expected titles. ## Quick Start Ask the agent to rewrite the Sage, Muse, and Omega system prompts to be more enterprise-focused while keeping the loop contract, then run the verification steps.

Frequently Asked Questions about omega-loops-agents

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

FAQPage Schema
How do I edit the built-in agent prompts in Omega Loops?▼

Edit the markdown files in crates/omega_repo/src/agents for omega, muse, and sage, keeping the YAML frontmatter ids and handlebars blocks intact. Then run cargo test -p omega_repo --lib agent::tests and rebuild with scripts/dev-omega.sh so include_str! picks up the changes.

What is the Sage Muse Omega loop contract?▼

Sage handles research and review with read-only tools, Muse plans via the plan tool writing only to plans/, and Omega implements and verifies with full write access. Do not turn Sage into a planner or Muse into an implementer.

Why do agent prompt changes not appear after rebuilding?▼

Agent markdown is compiled into the binary via include_str!, so a plain install does not rebuild an existing debug binary. Run scripts/dev-omega.sh to force a rebuild so the new prompts land in the binary.

How do I update insta snapshots after editing the agent wrapper?▼

Run INSTA_UPDATE=1 cargo test -p omega_app --lib orch_spec::orch_system_spec to accept new snapshots. Never use INSTA_UPDATE=0, which panics on insta 1.48; unset the variable to re-check.

Why does omega list agent show no titles after a prompt change?▼

The command can exit 0 while printing a missing provider warning that hides titles. Set OMEGA_SESSION__PROVIDER_ID=xai_oauth and OMEGA_SESSION__MODEL_ID with a temp OMEGA_CONFIG directory to see the expected titles.

When should I not use this Skill?▼

Do not use it for CLI install or smoke testing, provider OAuth setup, Anda/KIP wiring, or TUI interface work; those belong to the omega-loops-cli, omega-loops-providers, omega-anda-pathways, and ratatui-agent-tui skills respectively.