Skill rating

Run the Omnigent load test and produce a results file explaining the latencies. Load when the user wants to load-test / stress-test / benchmark Omnigent under concurrency ("load test omnigent", "stres

Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.

Turn a breaking change (an API rename, removed flag, changed default, or moved module) into concrete upgrade steps with before/after examples. Use when the user asks how to migrate, upgrade, or adapt

Draft or refresh Omnigent package release notes for the next version using the existing GitHub Actions preview, merged PR material, and release-note composer. Use when preparing release highlights bef

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a

Deep reference on Omnigent config format, executor types, skill/tool structure, and conventions. Load when you need to look up how the platform works.

Spin up a live local Omnigent server + runner and exercise the native Pi TUI harness (pi-native) end-to-end — launch the real `pi` CLI via `omnigent pi`, drive turns through the web/bridge, smoke-test

Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.

Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.

Have the Claude and GPT partners critique each other's answers across a configurable number of rounds (default 1) before converging on a synthesis. Use when the user wants the two perspectives stress-

Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a

Choose the design, record the alternatives and CUJ coverage, or stop when a choice needs a human.

Spin up a live local Omnigent server + runner and exercise the native Antigravity (agy) TUI harness (antigravity-native) end-to-end — launch the real `agy` CLI via `omnigent antigravity`, drive turns

Turn the ticket into requirements and CUJs, and stop with a split proposal when it is too big.

Run Polly and OCR on a PR until all findings settle.

Procedure for answering a question with a thorough, cross-checked, cited web-research report using the Keenable search + fetch tools.

Reference guide for building new Omnigent harness integrations — covers SDK/subprocess harnesses and native harnesses as separate tracks, each with their own feature matrix, implementation patterns, a

Select the Resolve mode, recover its input, check the workspace, and discover existing fixes.

Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks and loop until clean.

Delegate read-only investigation, debugging, audit, search, or code-understanding tasks to sub-agents; synthesize only from their structured reports.

Run independent subtasks in parallel — one git worktree and one implementation sub-agent per task, each opening its own PR — then cross-review every PR. polly never merges; the human does.

Verify the reported path, cause, and historical intent before choosing a fix.

Drive an open PR through Polly/OCR, validation, and maintainer handoff.

Emit the complete feature handoff with exact modes, outcomes, CUJs, demos, and publication state.

Commit the feature, write the PR body, publish in the selected mode, and drive the PR.

Read the input and ticket, choose the mode, run preflight, and check for existing delivery.

Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.

Audit a recovered repro patch, assertions, and behavioral baseline before authoring or reviewing.

Handle trusted reviewers' change requests on Otto PRs.

Implement the design with focused tests mapped to each covered CUJ.

Check the final diff's consumers, focused tests, evidence, and gaps.

Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop. Drives the real `omnigent` binary through a PTY (pexpect) insid

PR mergeability, CI, and live preview.

Research checklist and source-quality guidance for the archer e2e fixture.

Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, o

Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a

Spin up a live local Omnigent server and exercise the Cursor SDK harness end-to-end — build cursor agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the cur

Test counter — pi skills e2e. The unique suffix d2f6e1 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.

Test greeter — pi skills e2e. The unique suffix c4a8d5 appears in the skill name so a string match in the agent's output proves Pi loaded this skill.

Spin up a live local Omnigent server and exercise the GitHub Copilot SDK harness end-to-end — build copilot agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debuggin

End-to-end test the polly multi-agent coding orchestrator's critical user journeys (CUJs). Two halves — a deterministic mock-LLM driver (polly_cuj.py) that boots a throwaway local server + mock LLM an

Test counter — codex skills e2e. The unique suffix b8d4e7 appears in the skill name so a string match in the agent's output proves codex loaded this skill.

Test greeter — codex skills e2e. The unique suffix a3f9c2 appears in the skill name so a string match in the agent's output proves codex loaded this skill.

Find the root cause, implement a focused fix, and prove behavior with targeted tests and recordings.

Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.

Record at least one captioned demo for every covered CUJ through its real entry point.

Review an existing fix PR using the audited repro and full diff, preserving branch and approval rules.

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user