github.com/code-yeongyu/lazycodex
| Skill | Added | Review |
|---|---|---|
programming plugins/omo/skills/programming/SKILL.md Applies strict, modern language practice (typed errors, exhaustive match, tests that can fail) for Python, Rust, TypeScript, JavaScript, and Go. Use for work on .py, .rs, .ts, .js, or .go files, and whenever a test or spec file is written, reshaped, reviewed, or deleted: the four-question test authoring gate and the junk-test classes live here. | 67 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
refactor plugins/omo/skills/refactor/SKILL.md Guides a refactor, cleanup, or restructure with the right decomposition. Use when the user asks to refactor, simplify, extract, or modernize code. | 56 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
remove-ai-slops plugins/omo/skills/remove-ai-slops/SKILL.md Removes AI-generated code smells from branch changes or an explicit file list behind regression tests, including junk tests (prose pins, source greps, copied inventories, mock echoes), each proven by its class's rule before a cut. Use when the user asks to clean up, deslop, remove AI-slop patterns, or prune tests from recent changes. | 71 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
review-work plugins/omo/skills/review-work/SKILL.md Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work. | 64 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
rules plugins/omo/components/rules/skills/rules/SKILL.md Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration. | 56 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
rules plugins/omo/skills/rules/SKILL.md Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or environment configuration. | 68 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
teammode plugins/omo/components/teammode/skills/teammode/SKILL.md Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team. | — | |
teammode plugins/omo/skills/teammode/SKILL.md Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when the user asks Codex to create, run, coordinate, inspect, archive, or delete a team of agents/threads/sessions, or to work on something as a team in parallel. FIRST inspects the active tool surface (checking tool_search for deferred tools) and tells the user the route: native MultiAgentV2 agents (flat spawn_agent with task_name) when available, Codex App threads as the fallback, or a plain-subagent split when neither set exists. The main session is always the leader; members are defined by a concrete part, ownership area, or perspective - never a vague job role; a bundled cross-platform script writes the .omo/teams state plus an auto-generated member field manual. Use a team when the work is not perfectly isolated but parallelizing helps; use plain subagents when scope is perfectly isolated or the goal is ambiguous. Triggers: team mode, teammode, make a team, run as a team, team of agents, coordinate threads, parallel Codex threads, archive the team. | — | |
ultimate-browsing plugins/omo/skills/ultimate-browsing/SKILL.md Reaches web pages the user's browser cannot open: WAF-blocked and bot-scored hosts, platform-native readers (Chinese and social platforms), archive snapshots with provenance, and a browser you own for stealth or throwaway profiles. Not for plain search, an unblocked static fetch, or a page the user's browser can open. | 68 Impact — No eval scenarios have been run Securityby Medium Suggest reviewing before use Version: 7e2aae8 | |
ultrawork plugins/omo/skills/ultrawork/SKILL.md Binding ultrawork mode directive for omo on Codex. When a prompt contains ultrawork or ulw, the omo UserPromptSubmit hook injects a short bootstrap that points at this file. Read the whole file and follow every rule in it for the rest of the task. | 58 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
ulw-execute plugins/omo/skills/ulw-execute/SKILL.md Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan. | 64 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
ulw-loop plugins/omo/components/ulw-loop/skills/ulw-loop/SKILL.md A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution. | 64 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
ulw-loop plugins/omo/skills/ulw-loop/SKILL.md A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution. | 54 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
ulw-plan plugins/omo/components/ultrawork/skills/ulw-plan/SKILL.md ACTIVATES ONLY on an explicit user request for the ulw-plan workflow: the user themselves saying ulw-plan, ulw plan, /skill:ulw-plan, or asking in their own words for a work plan before coding. NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request, and the plan-gated reviewers (metis/momus) stay locked without a user request plus a written .omo/plans plan file. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode. | 70 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
ulw-plan plugins/omo/skills/ulw-plan/SKILL.md ACTIVATES ONLY on an explicit user request for the ulw-plan workflow: the user themselves saying ulw-plan, ulw plan, /skill:ulw-plan, or asking in their own words for a work plan before coding. NEVER self-activates: a bare ulw/ultrawork run, an agent-side routing decision, or reading this file is not a request, and the plan-gated reviewers (metis/momus) stay locked without a user request plus a written .omo/plans plan file. Explore-first planning consultant (Prometheus) that grounds in the codebase, asks only the forks exploration cannot resolve - or researches them to best practice when the intent is fuzzy - waits for explicit approval, then writes ONE decision-complete work plan a worker executes with zero further interview. Triggers: ulw-plan, ulw plan, plan this, make a plan, plan before coding, interview me, break this down, start planning, plan mode. | 70 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 | |
ulw-research plugins/omo/skills/ulw-research/SKILL.md Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording. | 64 Impact — No eval scenarios have been run Securityby Passed No findings from the security scan Version: 7e2aae8 | |
visual-qa plugins/omo/skills/visual-qa/SKILL.md Runs rigorous visual QA across web, terminal, and paginated surfaces: an Apple HIG-based checklist, paired light/dark captures at phone and desktop widths, screenshot evidence, and a per-item PASS/FAIL verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right or follows the platform's design guidelines. | 65 Impact — No eval scenarios have been run Securityby Low Low-risk findings worth noting Version: 7e2aae8 |