Menü
Use at every gate checkpoint and periodically during experiments to verify that project progress matches the target venue's requirements in terms of experiment scale, novelty depth, and evidence quality
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Use when designing the evaluation protocol for a method development project — locks primary metrics, datasets, seeds, statistical tests, and baseline list into an immutable contract
Use when G2 (plan freeze) and G3 (execution readiness) gates have passed — handles all implementation, baseline reproduction, experimentation, and iteration for both Type M and Type D projects; this is Phase 4
Use when research direction is validated (G1 passed) and the project needs method design, analysis framework, evaluation protocol, or story line — this is Phase 3 and must complete before any code or experiments
Reusable protocol for multi-agent discussions that iterate until convergence. Used by results-integration (Phase 5) and paper-writing (Phase 6) to ensure discussions actually resolve issues rather than just noting them.
Use when and ONLY when the user explicitly requests paper writing and G4 (write-ready) gate has passed — handles LaTeX structure, senior-level writing, reference verification, and iterative refinement
Use when Phase 1 (research-direction-exploration) is complete and G1 gate has passed — subjects the research problem to adversarial defense-style questioning, classifies project intent, re-evaluates venue target, and produces a final feasibility ruling before any method design begins
| name | venue-alignment |
| description | Use at every gate checkpoint and periodically during experiments to verify that project progress matches the target venue's requirements in terms of experiment scale, novelty depth, and evidence quality |
A project that meets Tier C standards but targets a Tier A venue will be rejected. A project that exceeds Tier A standards but targets a Tier C venue wastes effort. This skill keeps project ambition and execution aligned with the target venue at every stage.
Check venue alignment at every gate and periodically during Phase 4 execution.
"Is the identified gap significant enough for [venue]?"
"Does the method/analysis design have enough depth for [venue]?"
"Is the planned experiment scale sufficient for [venue]?"
"Does the evidence package (figures, tables, statistics) meet [venue] standards?"
| Requirement | Tier A | Tier B | Tier C |
|---|---|---|---|
| Baselines | 5–8 strong, recent | 3–5 | 2–3 |
| Datasets | 3–5 | 2–3 | 1–2 |
| Ablation | Full component ablation | Key components | Optional |
| Statistics | CI + significance test | mean ± std | mean ± std |
| Novelty | Clear, significant advance | Solid contribution | Incremental or applied |
| Analysis depth | Multi-angle, comprehensive | Adequate coverage | Focused |
If current progress falls short of venue requirements at any gate:
research-anchor.yaml under venue_targetNever silently accept misalignment. The user must make an informed decision.
Match ambition to evidence. Match evidence to venue.
Misalignment in either direction wastes effort.