Polish SkillGym dataset card
Browse files
README.md
CHANGED
|
@@ -20,29 +20,40 @@ tags:
|
|
| 20 |
<div align="center">
|
| 21 |
|
| 22 |
<picture>
|
| 23 |
-
<source media="(prefers-color-scheme: dark)"
|
| 24 |
-
|
| 25 |
-
<
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 26 |
</picture>
|
| 27 |
|
| 28 |
-
|
| 29 |
|
| 30 |
-
|
|
|
|
|
|
|
| 31 |
|
| 32 |
-
|
| 33 |
-
|
| 34 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 35 |
|
| 36 |
</div>
|
| 37 |
|
| 38 |
## Dataset Summary
|
| 39 |
|
| 40 |
-
**SkillGym** is the data release accompanying the SkillGym framework. It connects human-written
|
| 41 |
-
procedural knowledge to executable task environments, code-based outcome verifiers, paired
|
| 42 |
-
with-skill / without-skill executions, and long-horizon agent trajectories.
|
| 43 |
|
| 44 |
-
The dataset is intended to support research on skill-grounded task construction, agent training,
|
| 45 |
-
verifier-based evaluation, procedural transfer, and outcome-based learning.
|
| 46 |
|
| 47 |
| Statistic | Value |
|
| 48 |
| --- | ---: |
|
|
@@ -68,11 +79,9 @@ Successful trajectories cover 62 of the 63 sub-categories represented by accepte
|
|
| 68 |
|
| 69 |
### Release Snapshot
|
| 70 |
|
| 71 |
-
The large-artifact dataset snapshot is associated with GitHub commit
|
| 72 |
-
[`6ebabba`](https://github.com/ECNU-ICALK/SkillGym/commit/6ebabba).
|
| 73 |
|
| 74 |
-
The GitHub codebase, dataset repository, and model repository are versioned independently. For exact
|
| 75 |
-
reproduction, record the revision used from each repository.
|
| 76 |
|
| 77 |
## Quick Start
|
| 78 |
|
|
@@ -118,13 +127,10 @@ hf download ecnu-icalk/SkillGym \
|
|
| 118 |
--local-dir .hf/skillgym
|
| 119 |
```
|
| 120 |
|
| 121 |
-
For building new environments, use the
|
| 122 |
-
[SkillGym Task Builder](https://github.com/ECNU-ICALK/SkillGym/tree/main/task_builder).
|
| 123 |
|
| 124 |
## Dataset Organization
|
| 125 |
|
| 126 |
-
At the release level:
|
| 127 |
-
|
| 128 |
```text
|
| 129 |
SkillGym/
|
| 130 |
├── Tasks.tar.zst
|
|
@@ -135,26 +141,19 @@ SkillGym/
|
|
| 135 |
└── verifier_passed_*.jsonl
|
| 136 |
```
|
| 137 |
|
| 138 |
-
The task archives contain the source skill/task relationship, task instructions, environment
|
| 139 |
-
configuration, task-specific verification logic, and paired execution variants used during
|
| 140 |
-
construction and validation.
|
| 141 |
|
| 142 |
-
Trajectory collections preserve agent interaction traces and verification outcomes for successful
|
| 143 |
-
sampled executions.
|
| 144 |
|
| 145 |
## Terminology
|
| 146 |
|
| 147 |
-
The same paired skill-availability concept appears under slightly different names across the paper,
|
| 148 |
-
released data, and implementation:
|
| 149 |
-
|
| 150 |
| Context | Skill available | Skill removed |
|
| 151 |
| --- | --- | --- |
|
| 152 |
| **Paper / benchmark tables** | `w/ Skills` | `w/o Skills` |
|
| 153 |
| **Released dataset variants** | `withskill` | `withoutskill` |
|
| 154 |
| **Task Builder internals** | `with_skill` | `no_skill` |
|
| 155 |
|
| 156 |
-
These names refer to the same paired evaluation concept; the differences reflect presentation,
|
| 157 |
-
released-storage, and implementation conventions.
|
| 158 |
|
| 159 |
## Task Labels and Paired Variants
|
| 160 |
|
|
@@ -170,16 +169,13 @@ A task is labeled **Skill-Dep.** when, under the reference construction configur
|
|
| 170 |
|
| 171 |
### Verifier-Passed
|
| 172 |
|
| 173 |
-
A **Verifier-Passed** task has a valid executable environment and outcome verifier but does not satisfy
|
| 174 |
-
the stricter contrastive Skill-Dep. criterion under the reference configuration.
|
| 175 |
|
| 176 |
-
These labels characterize accepted environments at construction time. They do **not** guarantee that
|
| 177 |
-
every later model or harness will succeed or fail in the same way.
|
| 178 |
|
| 179 |
## Trajectory Data
|
| 180 |
|
| 181 |
-
Successful trajectories retain the interaction sequence that led to a verifier-confirmed outcome.
|
| 182 |
-
Depending on the source harness, records may include:
|
| 183 |
|
| 184 |
- task and session identifiers;
|
| 185 |
- task prompt and skill metadata;
|
|
@@ -192,17 +188,14 @@ Depending on the source harness, records may include:
|
|
| 192 |
|
| 193 |
### Schema Note
|
| 194 |
|
| 195 |
-
The eight trajectory files preserve source-specific trace structures. Some nested fields differ across
|
| 196 |
-
harness/model collections, so the release should **not** be assumed to have one perfectly uniform
|
| 197 |
-
nested JSON schema across every file.
|
| 198 |
|
| 199 |
For the most robust loading behavior:
|
| 200 |
|
| 201 |
- load one trajectory collection at a time; or
|
| 202 |
- explicitly normalize compatible files before concatenating them.
|
| 203 |
|
| 204 |
-
Using an explicit `data_files` path, as in the streaming example above, is preferable to treating every
|
| 205 |
-
trajectory JSONL file as a single homogeneous split.
|
| 206 |
|
| 207 |
## Trajectory Statistics
|
| 208 |
|
|
@@ -218,14 +211,10 @@ trajectory JSONL file as a single homogeneous split.
|
|
| 218 |
| Corpus-wide maximum logged text tokens | **342.9k** |
|
| 219 |
| Corpus-wide maximum interaction steps | **318** |
|
| 220 |
|
| 221 |
-
The maxima above are corpus-wide maxima for their respective measures and need not come from the same
|
| 222 |
-
trajectory. Logged/saved text-token counts are dataset statistics and should not be interpreted as API
|
| 223 |
-
billing usage or as a single-request context length.
|
| 224 |
|
| 225 |
## Collection Configurations
|
| 226 |
|
| 227 |
-
Successful trajectories were collected from multiple harness–model configurations:
|
| 228 |
-
|
| 229 |
| Harness | Teacher model | Successful trajectories |
|
| 230 |
| --- | --- | ---: |
|
| 231 |
| Claude Code | DeepSeek V4 Pro | 1,722 |
|
|
@@ -233,9 +222,7 @@ Successful trajectories were collected from multiple harness–model configurati
|
|
| 233 |
| Codex | GPT-5.4 | 1,967 |
|
| 234 |
| Codex | Nex-N2-Pro | 2,906 |
|
| 235 |
|
| 236 |
-
This diversity broadens the interaction traces beyond one agent configuration, but the released
|
| 237 |
-
trajectory distribution should not be treated as representative of every model, harness, task domain,
|
| 238 |
-
or deployment setting.
|
| 239 |
|
| 240 |
## Intended Uses
|
| 241 |
|
|
@@ -254,11 +241,9 @@ SkillGym can support research on:
|
|
| 254 |
- Skill-Dep. and Verifier-Passed are reference-configuration labels, not universal properties.
|
| 255 |
- Category coverage is broad but uneven.
|
| 256 |
- Trajectory collections are generated by a finite set of harness–model configurations.
|
| 257 |
-
- Successful trajectories are a selected subset of sampled executions and should not be interpreted
|
| 258 |
-
as an unbiased behavioral distribution.
|
| 259 |
- Some trajectory files preserve harness-specific schema differences.
|
| 260 |
-
- Source skills, fixtures, and supporting assets may carry upstream notices or additional licensing
|
| 261 |
-
requirements.
|
| 262 |
|
| 263 |
## Related Resources
|
| 264 |
|
|
@@ -271,9 +256,6 @@ SkillGym can support research on:
|
|
| 271 |
|
| 272 |
## Citation
|
| 273 |
|
| 274 |
-
The accompanying paper is currently under double-blind review. Until final publication metadata is
|
| 275 |
-
available, please use:
|
| 276 |
-
|
| 277 |
```bibtex
|
| 278 |
@misc{skillgym2026,
|
| 279 |
title = {Internalizing Large-Scale Human-Written Skills into LLMs for Real-World Problem Solving},
|
|
@@ -284,11 +266,8 @@ available, please use:
|
|
| 284 |
|
| 285 |
## License
|
| 286 |
|
| 287 |
-
The dataset is marked **`license: other`** because it aggregates artifacts that may retain distinct
|
| 288 |
-
upstream notices or additional terms.
|
| 289 |
|
| 290 |
-
Repository-level SkillGym code is released under the **MIT License**. The SkillGym-Agent checkpoint
|
| 291 |
-
is released separately under **Apache-2.0**.
|
| 292 |
|
| 293 |
-
When redistributing source skills, fixtures, or supporting assets, preserve the corresponding upstream
|
| 294 |
-
notices and licensing terms.
|
|
|
|
| 20 |
<div align="center">
|
| 21 |
|
| 22 |
<picture>
|
| 23 |
+
<source media="(prefers-color-scheme: dark)"
|
| 24 |
+
srcset="https://raw.githubusercontent.com/ECNU-ICALK/SkillGym/main/assets/brand-dark.png">
|
| 25 |
+
<source media="(prefers-color-scheme: light)"
|
| 26 |
+
srcset="https://raw.githubusercontent.com/ECNU-ICALK/SkillGym/main/assets/brand-light.png">
|
| 27 |
+
<img
|
| 28 |
+
src="https://raw.githubusercontent.com/ECNU-ICALK/SkillGym/main/assets/brand-light.png"
|
| 29 |
+
alt="SkillGym"
|
| 30 |
+
width="360">
|
| 31 |
</picture>
|
| 32 |
|
| 33 |
+
<h2>SkillGym Dataset</h2>
|
| 34 |
|
| 35 |
+
<p>
|
| 36 |
+
<strong>Human-written skills, executable environments, and verified long-horizon agent trajectories</strong>
|
| 37 |
+
</p>
|
| 38 |
|
| 39 |
+
<p>
|
| 40 |
+
<strong>English</strong> ·
|
| 41 |
+
<a href="README_zh-CN.md">简体中文</a>
|
| 42 |
+
</p>
|
| 43 |
+
|
| 44 |
+
<p>
|
| 45 |
+
<a href="https://github.com/ECNU-ICALK/SkillGym">GitHub</a> ·
|
| 46 |
+
<a href="https://huggingface.co/ecnu-icalk/SkillGym-Agent">SkillGym-Agent</a> ·
|
| 47 |
+
<a href="https://github.com/ECNU-ICALK/SkillGym/blob/main/assets/Internalizing_Large_Scale_Human_Written_Skills_into_LLMs_for_Real_World_Problem_Solving.pdf">Paper</a>
|
| 48 |
+
</p>
|
| 49 |
|
| 50 |
</div>
|
| 51 |
|
| 52 |
## Dataset Summary
|
| 53 |
|
| 54 |
+
**SkillGym** is the data release accompanying the SkillGym framework. It connects human-written procedural knowledge to executable task environments, code-based outcome verifiers, paired with-skill / without-skill executions, and long-horizon agent trajectories.
|
|
|
|
|
|
|
| 55 |
|
| 56 |
+
The dataset is intended to support research on skill-grounded task construction, agent training, verifier-based evaluation, procedural transfer, and outcome-based learning.
|
|
|
|
| 57 |
|
| 58 |
| Statistic | Value |
|
| 59 |
| --- | ---: |
|
|
|
|
| 79 |
|
| 80 |
### Release Snapshot
|
| 81 |
|
| 82 |
+
The large-artifact dataset snapshot is associated with GitHub commit [`6ebabba`](https://github.com/ECNU-ICALK/SkillGym/commit/6ebabba).
|
|
|
|
| 83 |
|
| 84 |
+
The GitHub codebase, dataset repository, and model repository are versioned independently. For exact reproduction, record the revision used from each repository.
|
|
|
|
| 85 |
|
| 86 |
## Quick Start
|
| 87 |
|
|
|
|
| 127 |
--local-dir .hf/skillgym
|
| 128 |
```
|
| 129 |
|
| 130 |
+
For building new environments, use the [SkillGym Task Builder](https://github.com/ECNU-ICALK/SkillGym/tree/main/task_builder).
|
|
|
|
| 131 |
|
| 132 |
## Dataset Organization
|
| 133 |
|
|
|
|
|
|
|
| 134 |
```text
|
| 135 |
SkillGym/
|
| 136 |
├── Tasks.tar.zst
|
|
|
|
| 141 |
└── verifier_passed_*.jsonl
|
| 142 |
```
|
| 143 |
|
| 144 |
+
The task archives contain the source skill/task relationship, task instructions, environment configuration, task-specific verification logic, and paired execution variants used during construction and validation.
|
|
|
|
|
|
|
| 145 |
|
| 146 |
+
Trajectory collections preserve agent interaction traces and verification outcomes for successful sampled executions.
|
|
|
|
| 147 |
|
| 148 |
## Terminology
|
| 149 |
|
|
|
|
|
|
|
|
|
|
| 150 |
| Context | Skill available | Skill removed |
|
| 151 |
| --- | --- | --- |
|
| 152 |
| **Paper / benchmark tables** | `w/ Skills` | `w/o Skills` |
|
| 153 |
| **Released dataset variants** | `withskill` | `withoutskill` |
|
| 154 |
| **Task Builder internals** | `with_skill` | `no_skill` |
|
| 155 |
|
| 156 |
+
These names refer to the same paired evaluation concept; the differences reflect presentation, released-storage, and implementation conventions.
|
|
|
|
| 157 |
|
| 158 |
## Task Labels and Paired Variants
|
| 159 |
|
|
|
|
| 169 |
|
| 170 |
### Verifier-Passed
|
| 171 |
|
| 172 |
+
A **Verifier-Passed** task has a valid executable environment and outcome verifier but does not satisfy the stricter contrastive Skill-Dep. criterion under the reference configuration.
|
|
|
|
| 173 |
|
| 174 |
+
These labels characterize accepted environments at construction time. They do **not** guarantee that every later model or harness will succeed or fail in the same way.
|
|
|
|
| 175 |
|
| 176 |
## Trajectory Data
|
| 177 |
|
| 178 |
+
Successful trajectories retain the interaction sequence that led to a verifier-confirmed outcome. Depending on the source harness, records may include:
|
|
|
|
| 179 |
|
| 180 |
- task and session identifiers;
|
| 181 |
- task prompt and skill metadata;
|
|
|
|
| 188 |
|
| 189 |
### Schema Note
|
| 190 |
|
| 191 |
+
The eight trajectory files preserve source-specific trace structures. Some nested fields differ across harness/model collections, so the release should **not** be assumed to have one perfectly uniform nested JSON schema across every file.
|
|
|
|
|
|
|
| 192 |
|
| 193 |
For the most robust loading behavior:
|
| 194 |
|
| 195 |
- load one trajectory collection at a time; or
|
| 196 |
- explicitly normalize compatible files before concatenating them.
|
| 197 |
|
| 198 |
+
Using an explicit `data_files` path, as in the streaming example above, is preferable to treating every trajectory JSONL file as a single homogeneous split.
|
|
|
|
| 199 |
|
| 200 |
## Trajectory Statistics
|
| 201 |
|
|
|
|
| 211 |
| Corpus-wide maximum logged text tokens | **342.9k** |
|
| 212 |
| Corpus-wide maximum interaction steps | **318** |
|
| 213 |
|
| 214 |
+
The maxima above are corpus-wide maxima for their respective measures and need not come from the same trajectory. Logged/saved text-token counts are dataset statistics and should not be interpreted as API billing usage or as a single-request context length.
|
|
|
|
|
|
|
| 215 |
|
| 216 |
## Collection Configurations
|
| 217 |
|
|
|
|
|
|
|
| 218 |
| Harness | Teacher model | Successful trajectories |
|
| 219 |
| --- | --- | ---: |
|
| 220 |
| Claude Code | DeepSeek V4 Pro | 1,722 |
|
|
|
|
| 222 |
| Codex | GPT-5.4 | 1,967 |
|
| 223 |
| Codex | Nex-N2-Pro | 2,906 |
|
| 224 |
|
| 225 |
+
This diversity broadens the interaction traces beyond one agent configuration, but the released trajectory distribution should not be treated as representative of every model, harness, task domain, or deployment setting.
|
|
|
|
|
|
|
| 226 |
|
| 227 |
## Intended Uses
|
| 228 |
|
|
|
|
| 241 |
- Skill-Dep. and Verifier-Passed are reference-configuration labels, not universal properties.
|
| 242 |
- Category coverage is broad but uneven.
|
| 243 |
- Trajectory collections are generated by a finite set of harness–model configurations.
|
| 244 |
+
- Successful trajectories are a selected subset of sampled executions and should not be interpreted as an unbiased behavioral distribution.
|
|
|
|
| 245 |
- Some trajectory files preserve harness-specific schema differences.
|
| 246 |
+
- Source skills, fixtures, and supporting assets may carry upstream notices or additional licensing requirements.
|
|
|
|
| 247 |
|
| 248 |
## Related Resources
|
| 249 |
|
|
|
|
| 256 |
|
| 257 |
## Citation
|
| 258 |
|
|
|
|
|
|
|
|
|
|
| 259 |
```bibtex
|
| 260 |
@misc{skillgym2026,
|
| 261 |
title = {Internalizing Large-Scale Human-Written Skills into LLMs for Real-World Problem Solving},
|
|
|
|
| 266 |
|
| 267 |
## License
|
| 268 |
|
| 269 |
+
The dataset is marked **`license: other`** because it aggregates artifacts that may retain distinct upstream notices or additional terms.
|
|
|
|
| 270 |
|
| 271 |
+
Repository-level SkillGym code is released under the **MIT License**. The SkillGym-Agent checkpoint is released separately under **Apache-2.0**.
|
|
|
|
| 272 |
|
| 273 |
+
When redistributing source skills, fixtures, or supporting assets, preserve the corresponding upstream notices and licensing terms.
|
|
|