菜单
Guidelines for scoping research ideas into actionable tasks. Use when the root idea is broad or ambiguous to ensure appropriate granularity and feasibility. Helps with initial decomposition. Apply at root (task "0") and when refining broad sub-tasks.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validate task output against criteria before calling Finish. Use when the task has a validation spec (criteria, optionalChecks). Load this skill, write output to sandbox, run validate script, fix issues if validation fails, then call Finish.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
End-to-end git release workflow for this repository. Use when the user asks to publish a release, says release or ship, or otherwise wants Codex to complete release work by checking and updating docs, reviewing all changes since the previous tag, committing and pushing changes, choosing a version tag based on release scope, and drafting concise Chinese GitHub-ready release notes in a fenced Markdown block.
Develop complete, runnable software projects. Use this whenever the user asks to write code, create an app, or analyze data with scripts. This skill enforces persisting all code to disk (via the WriteFile tool which runs inside the Docker workspace) and executing it (via the RunCommand tool), rather than outputting scattered Markdown code snippets.
Advanced RAG-style research schema with literature-grounded fields. Use when RefineIdea for hardware-aware or citation-heavy proposals.
Quality criteria for refined_idea output. Use before RefineIdea or when ValidateRefinedIdea returns low score. Focus on concrete, decomposable, and specific output.
| name | research-scoping |
| description | Guidelines for scoping research ideas into actionable tasks. Use when the root idea is broad or ambiguous to ensure appropriate granularity and feasibility. Helps with initial decomposition. Apply at root (task "0") and when refining broad sub-tasks. |
Guidelines for turning research ideas into well-scoped task trees. Apply at root (task "0") and when refining broad sub-tasks.
| Domain | Typical Phases | Notes |
|---|---|---|
| Literature review | Search → Filter → Synthesize → Report | Each phase has distinct methodology |
| Technical comparison | Scope → Research A → Research B → Compare | Parallel research, then synthesis |
| Experiment | Hypothesis → Setup → Run → Analyze | Sequential, data flows forward |
| Survey/Interview | Design → Conduct → Analyze → Report | Design defines Conduct; Conduct feeds Analyze |
| Benchmark/Evaluation | Define metrics → Setup → Run → Aggregate | Similar to Experiment |
| Documentation | Outline → Draft → Review → Finalize | Iterative refinement |
| Gap analysis | Define scope → Gather current state → Identify gaps → Recommend | Feasibility, maturity assessment |
When the idea is too broad:
Do not create a task for the final research paper. The Paper Agent generates the paper from task outputs after execution. Tasks may produce summaries, synthesis reports, comparison outputs, or literature reviews—these are appropriate. The Paper Agent composes them into the final paper.
