Sync ParaSkill design-baselines-and-ablations
Browse files- LICENSE +21 -0
- README.md +56 -0
- SKILL.md +125 -0
- agents/openai.yaml +4 -0
LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
MIT License
|
| 2 |
+
|
| 3 |
+
Copyright (c) 2026 bhxdianzhang
|
| 4 |
+
|
| 5 |
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
| 6 |
+
of this software and associated documentation files (the "Software"), to deal
|
| 7 |
+
in the Software without restriction, including without limitation the rights
|
| 8 |
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
| 9 |
+
copies of the Software, and to permit persons to whom the Software is
|
| 10 |
+
furnished to do so, subject to the following conditions:
|
| 11 |
+
|
| 12 |
+
The above copyright notice and this permission notice shall be included in all
|
| 13 |
+
copies or substantial portions of the Software.
|
| 14 |
+
|
| 15 |
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
| 16 |
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
| 17 |
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
| 18 |
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
| 19 |
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
| 20 |
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
| 21 |
+
SOFTWARE.
|
README.md
ADDED
|
@@ -0,0 +1,56 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
license: mit
|
| 3 |
+
language:
|
| 4 |
+
- zh
|
| 5 |
+
- en
|
| 6 |
+
tags:
|
| 7 |
+
- codex-skill
|
| 8 |
+
- ai-agent
|
| 9 |
+
- scientific-writing
|
| 10 |
+
- research-workflow
|
| 11 |
+
- paraskill
|
| 12 |
+
- paradoxgpt
|
| 13 |
+
- designer
|
| 14 |
+
pretty_name: DesignBaselinesAndAblations
|
| 15 |
+
---
|
| 16 |
+
|
| 17 |
+
# DesignBaselinesAndAblations
|
| 18 |
+
|
| 19 |
+
`design-baselines-and-ablations` is a ParaSkill research workflow skill for the `designer` family.
|
| 20 |
+
|
| 21 |
+
## Purpose
|
| 22 |
+
|
| 23 |
+
Design baseline and ablation plans that test a method's central claims and isolate which components matter. Use when a paper has a method sketch, claims, and research area but needs comparison structure, component ablations, and expected findings. Output is an experiment design plan, not a list of random benchmark names.
|
| 24 |
+
|
| 25 |
+
## Metadata
|
| 26 |
+
|
| 27 |
+
- Family: `designer`
|
| 28 |
+
- Owner model: `ParadoxGPT-Designer-4B`
|
| 29 |
+
- Output type: `generation`
|
| 30 |
+
- Version: `0.1`
|
| 31 |
+
- Default language: `zh`
|
| 32 |
+
|
| 33 |
+
## Included Files
|
| 34 |
+
|
| 35 |
+
```text
|
| 36 |
+
DesignBaselinesAndAblations/
|
| 37 |
+
SKILL.md
|
| 38 |
+
agents/openai.yaml
|
| 39 |
+
README.md
|
| 40 |
+
LICENSE
|
| 41 |
+
```
|
| 42 |
+
|
| 43 |
+
`SKILL.md` is the executable skill instruction. `README.md` is the Hugging Face card.
|
| 44 |
+
|
| 45 |
+
## Installation
|
| 46 |
+
|
| 47 |
+
Copy this folder into a Codex-discoverable skills directory, or reference `SKILL.md` directly from an agent workflow.
|
| 48 |
+
|
| 49 |
+
```bash
|
| 50 |
+
mkdir -p ~/.codex/skills
|
| 51 |
+
cp -r DesignBaselinesAndAblations ~/.codex/skills/design-baselines-and-ablations
|
| 52 |
+
```
|
| 53 |
+
|
| 54 |
+
## Source
|
| 55 |
+
|
| 56 |
+
This skill is part of the ParaSkill library for ParadoxGPT. The full routing table is maintained in `SKILL_INDEX.json` in the source bundle.
|
SKILL.md
ADDED
|
@@ -0,0 +1,125 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
name: design-baselines-and-ablations
|
| 3 |
+
description: >-
|
| 4 |
+
Design baseline and ablation plans that test a method's central claims and
|
| 5 |
+
isolate which components matter. Use when a paper has a method sketch, claims,
|
| 6 |
+
and research area but needs comparison structure, component ablations, and
|
| 7 |
+
expected findings. Output is an experiment design plan, not a list of random
|
| 8 |
+
benchmark names.
|
| 9 |
+
metadata:
|
| 10 |
+
owner_model: ParadoxGPT-Designer-4B
|
| 11 |
+
skill_family: designer
|
| 12 |
+
version: "0.1"
|
| 13 |
+
output_type: generation
|
| 14 |
+
default_language: zh
|
| 15 |
+
trigger_keywords: [baseline, ablation, component, experiment design, 对比实验, 消融, 基线]
|
| 16 |
+
required_inputs: [method_summary, core_components, claims]
|
| 17 |
+
optional_inputs: [research_area, related_work, constraints, current_experiments]
|
| 18 |
+
handoff_to: [map-claims-to-experiments, design-diagnostic-analysis, identify-fatal-concerns]
|
| 19 |
+
---
|
| 20 |
+
|
| 21 |
+
# Design Baselines And Ablations
|
| 22 |
+
|
| 23 |
+
## Purpose
|
| 24 |
+
|
| 25 |
+
为方法型 claim 设计 baseline 和 ablation,使实验能回答“比什么强”“为什么强”“哪个组件必要”。这个 skill 不负责随机挑 dataset 名,而是确定对照结构和消融逻辑。
|
| 26 |
+
|
| 27 |
+
## When to Use
|
| 28 |
+
|
| 29 |
+
- 方法已有核心组件,但实验不知道该怎么对比。
|
| 30 |
+
- reviewer 可能质疑增益来自 trivial baseline 或某个组件无效。
|
| 31 |
+
- `map-claims-to-experiments` 发现 baseline / ablation 缺口。
|
| 32 |
+
|
| 33 |
+
## Do Not Use
|
| 34 |
+
|
| 35 |
+
- 还没有明确 claims → 先用 `map-claims-to-experiments`。
|
| 36 |
+
- 想解释机制为什么有效 → 用 `design-diagnostic-analysis`。
|
| 37 |
+
- 只想判断是否 fatal → 用 `identify-fatal-concerns`。
|
| 38 |
+
|
| 39 |
+
## Required Inputs
|
| 40 |
+
|
| 41 |
+
- `method_summary`: 方法概要。
|
| 42 |
+
- `core_components`: 方法核心组件清单。
|
| 43 |
+
- `claims`: 方法主张。
|
| 44 |
+
- `research_area`: optional,领域或任务类型。
|
| 45 |
+
- `related_work`: optional,相关方法类别。
|
| 46 |
+
- `constraints`: optional,算力/时间/数据限制。
|
| 47 |
+
|
| 48 |
+
## Output Contract
|
| 49 |
+
|
| 50 |
+
输出必须至少包含:
|
| 51 |
+
|
| 52 |
+
1. **baseline_plan** - baseline 类型、比较目的、必须控制的变量。
|
| 53 |
+
2. **ablation_plan** - 每个核心组件如何消融、要检验什么。
|
| 54 |
+
3. **expected_findings** - 若 claim 成立应观察到什么。
|
| 55 |
+
4. **risk_if_missing** - 缺少某项实验会被 reviewer 如何攻击。
|
| 56 |
+
5. **minimal_viable_experiment_set** - 资源有限时的最小实验集。
|
| 57 |
+
|
| 58 |
+
## Procedure
|
| 59 |
+
|
| 60 |
+
1. 先把 claims 按 effectiveness、component necessity、efficiency、robustness 分类。
|
| 61 |
+
2. 为 effectiveness claim 选择 baseline 类型:strong prior method、simple heuristic、same-budget variant、oracle/upper-bound 等。
|
| 62 |
+
3. 为每个 core_component 设计去除、替换或冻结式 ablation。
|
| 63 |
+
4. 判断需要控制的变量:compute、data、model size、training budget、prompt length。
|
| 64 |
+
5. 给出最小实验集和缺失风险。
|
| 65 |
+
|
| 66 |
+
## Quality Bar
|
| 67 |
+
|
| 68 |
+
一个好的输出必须:
|
| 69 |
+
|
| 70 |
+
- baseline 与 claim 对齐,不是越多越好。
|
| 71 |
+
- ablation 能隔离组件贡献,避免同时改变多个变量。
|
| 72 |
+
- expected_findings 能区分 claim 成立/不成立。
|
| 73 |
+
- minimal set 能在 constraints 下执行。
|
| 74 |
+
|
| 75 |
+
一个差的输出:
|
| 76 |
+
|
| 77 |
+
- 只列“加 SOTA baseline、更多 ablation”。
|
| 78 |
+
- 没有说明每个 baseline 检验什么。
|
| 79 |
+
- 消融设计改变太多因素,无法归因。
|
| 80 |
+
|
| 81 |
+
## Failure Modes
|
| 82 |
+
|
| 83 |
+
- **baseline 过弱**:赢了也不能证明贡献。
|
| 84 |
+
- **baseline 过强但不公平**:比较预算或信息不一致。
|
| 85 |
+
- **消融不可解释**:删除组件导致系统无法运行,却被当作证据。
|
| 86 |
+
- **忽略 compute/data 控制**:增益可能来自资源而非方法。
|
| 87 |
+
|
| 88 |
+
## Handoff
|
| 89 |
+
|
| 90 |
+
- 如果 claim 到实验映射还不清 → `map-claims-to-experiments`
|
| 91 |
+
- 如果 ablation 后仍无法解释机制 → `design-diagnostic-analysis`
|
| 92 |
+
- 如果缺失实验可能导致 reject → `identify-fatal-concerns`
|
| 93 |
+
|
| 94 |
+
## Example
|
| 95 |
+
|
| 96 |
+
Input:
|
| 97 |
+
|
| 98 |
+
```
|
| 99 |
+
method_summary: interaction scaling agent with planner and verifier
|
| 100 |
+
core_components: planner, verifier, multi-round interaction budget
|
| 101 |
+
claims: higher long-horizon success; gains come from interaction rounds
|
| 102 |
+
```
|
| 103 |
+
|
| 104 |
+
Output:
|
| 105 |
+
|
| 106 |
+
```
|
| 107 |
+
baseline_plan:
|
| 108 |
+
B1 same model, single-round generation: 检验多轮是否必要。
|
| 109 |
+
B2 same token budget, fewer rounds but longer responses: 控制总生成量。
|
| 110 |
+
B3 prior memory/tool agent: 检验相对已有 agent 的收益。
|
| 111 |
+
|
| 112 |
+
ablation_plan:
|
| 113 |
+
A1 remove verifier: 检验纠错机制是否贡献。
|
| 114 |
+
A2 fixed vs scaled interaction rounds: 检验 scaling 曲线。
|
| 115 |
+
A3 planner-only / verifier-only: 隔离组件作用。
|
| 116 |
+
|
| 117 |
+
expected_findings:
|
| 118 |
+
- 如果 interaction claim 成立,same token budget 下多轮应优于单轮长生成。
|
| 119 |
+
|
| 120 |
+
risk_if_missing:
|
| 121 |
+
- 无 B2 时 reviewer 会认为收益来自更多 tokens。
|
| 122 |
+
|
| 123 |
+
minimal_viable_experiment_set:
|
| 124 |
+
- B1 + B2 + A2。
|
| 125 |
+
```
|
agents/openai.yaml
ADDED
|
@@ -0,0 +1,4 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
interface:
|
| 2 |
+
display_name: "Design Baselines And Ablations"
|
| 3 |
+
short_description: "Design baseline and ablation plans that test a method's central claims and isolate which c"
|
| 4 |
+
default_prompt: "Use $design-baselines-and-ablations for this research-writing task."
|