13 skills published by Optim-Agent across 2 repositories. Together they weigh 861 328 tokens — that is what loading all of them at once would cost you in context.
13 skills 861 328 tokens total
Use when optimizing configurable system parameters against a measurable scalar objective.
Use when the user wants to optimize configurable system parameters against a measurable scalar objective, especially for model training, inference, quantitative strategies, reinforcement learning, scientific workflows, or other expensive black-box evaluations where reading the project can improve trial selection.
MUST USE when investigating a bug, CI failure, test failure, regression, incident, broken behavior, root cause, RCA, or debug-why problem before deciding whether to create an optim-plans solution plan; do not use for ordinary feature ideas, vague product planning, direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
Use big-plan for broad or risky repo changes needing codebase inspection, websearch, and deeper refinement; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Use huge-plan for open-ended high-risk repo efforts needing websearch during brainstorming and refinement until convergence; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Use mini-plan for subtle low-risk repo changes needing one alignment question before execution; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
MUST USE when a user asks to plan, brainstorm, design, scope, review, or evaluate a repo change before implementation; do not use for direct implementation-only requests, factual/explanation questions, trivial operations, or explicit no-plan requests.
Use plan for normal repo changes needing bounded decisions, refinement, and high-priority review before execution; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Alias for search-and-plan when external research should inform a repo-change plan before implementation.
Use when the user wants to resume or rediscover an interrupted optim-plans run; automatically run the active recovery path when one is available.
Use when the user asks Codex to review a repository for improvement opportunities, feature inspiration, roadmap ideas, or implementation candidates before planning changes; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Use when external research should inform a repo-change plan before implementation; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.
Use small-plan for small repo changes needing up to three intent checks and exactly one refinement round; exclude direct implementation-only, factual/explanation, trivial, or explicit no-plan requests.