codex_e2e_xyz_greet_a3f9c2
This Claude Code skill serves as a test fixture for end-to-end validation of the Codex skills loading mechanism. It should be used during automated testing to verify that the agent correctly loads and enumerates Claude Code skills by asserting that the unique skill identifier appears in the agent's skills output.
git clone --depth 1 https://github.com/omnigent-ai/omnigent /tmp/codex_e2e_xyz_greet_a3f9c2 && cp -r /tmp/codex_e2e_xyz_greet_a3f9c2/tests/resources/agents/codex_skills_none/skills/codex_e2e_xyz_greet_a3f9c2 ~/.claude/skills/codex_e2e_xyz_greet_a3f9c2SKILL.md
# Codex E2E Greet (a3f9c2) This is a fixture skill for `tests/e2e/test_codex_skills_filter_e2e.py`. The skill body itself does not matter — the test asserts on whether the SKILL name (`codex_e2e_xyz_greet_a3f9c2`) appears in the agent's enumerated-skills response.
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, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.
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 cursor harness (omnigent/inner/cursor_executor.py, cursor_harness.py, cursor_auth.py) or its auth / model / tool-bridge behavior.
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 wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.
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-tested against each other, not just shown side by side.
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.
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.
Delegate read-only investigation, debugging, audit, search, or code-understanding tasks to sub-agents; synthesize only from their structured reports.
Patterns and templates for generating valid Omnigent agent directories. Load when ready to create files.