data-transfer
Import and export doccano datasets with the right formats and validation.
- License 许可
- MIT
- 最近更新
- 2026-09-03
- Stars
- ★ 351
- Forks
- 27
01 前言 Front Matter
- name
- data-transfer
- license
- MIT
- metadata
- { "disco-role": "operating" }
- description
- Import and export doccano datasets with the right formats and validation.
- disable-model-invocation
- true
02 资源文件 3
- 参考文档references/formats.md2.8 KB
- 参考文档references/troubleshooting.md2.3 KB
- 脚本scripts/list-formats.py1.3 KB
03 SKILL.md 正文
data-transfer
Use this sub-skill when the task is about getting data into or out of doccano: choosing an import format, validating a file, handling encodings or MIME checks, exporting annotations, or troubleshooting task-specific dataset shapes.
Covers
- import format selection for text, sequence, seq2seq, intent, image, bounding box, segmentation, captioning, and speech projects
- export format selection and formatter behavior
- encoding, delimiter, column, and file-type validation
- relation extraction import/export handling
- collaborative vs per-user export behavior
Excludes
- project creation, labels, members, comments, and annotation CRUD: use
project-annotation - auto-labeling template/request setup: use
auto-labeling - install, deployment, and package build: use
setup-and-deploy
Typical path
- Confirm the project type and whether relation extraction or collaborative export is involved.
- Choose the matching file format and any delimiter or column settings.
- Validate the file contents before uploading when possible.
- Check import errors or export outputs against the documented task shape.
Read next
references/formats.mdfor supported formats, task mapping, and export shapes.references/troubleshooting.mdfor parser, encoding, size, MIME, and validation failures.../../references/task-types.mdfor the project type that owns each annotation shape.scripts/list-formats.pyfor a small helper that prints the supported import/export formats by task.../../references/troubleshooting.mdfor cross-cutting install/runtime issues that may appear while testing imports or exports.
04 同仓库更多 Skills
passnet-triton-opt
Make a single PassNet Triton kernel fast AND numerically faithful: performance model (when a replacement can win at all), block/grid/warp tuning, autotune policy, launch overhead, and per-op numeric recipes to pass the dtype baseline tolerances. Use when a pass matches and is correct but speedup below expected, or when correctness fails by small numeric margins.
passnet-solve
END-TO-END playbook for solving one PassNet sample: analyze the computation graphs, decide the optimization strategy (what to fuse, what to replace, what to leave alone), drive the iteration loop, and maximize the sample score. This is the ENTRY skill — invoke it first for any PassNet optimization task; it tells you when to use passnet-pattern-fusion, passnet-triton-opt and passnet-feedback.
passnet-skill
PassNet GPU kernel optimization via compiler passes. Design and implement Triton-based optimization passes, create pass files under ./pass_dir/, self-evaluate with pass_evaluator, and iterate to maximize GPU speedup.
passnet-pattern-fusion
Author PassNet pass files: write patterns that actually MATCH the FX graph, pick fusion regions (which ops to absorb into one Triton kernel), and structure multi-pass submissions with the mandatory shared-dispatch architecture. Use when creating or fixing pattern()/replacement_args()/replacement_func() files, when a pass "failed to match", or when deciding how to fuse multiple kernels/ops.
passnet-orchestrate
Round/batch planning and decision support for PassNet graph optimization. Use for multi-sample triage, worker allocation, eval-budget policy, and post-eval keep/revert decisions. For solving one concrete sample end to end, use passnet-solve as the entry skill; consult this skill only when you need broader planning or a specific decision gate.
passnet-feedback
Fast, deterministic feedback for PassNet work: pre-flight pattern/match verification WITHOUT burning a GPU evaluation, per-node bottleneck analysis of a sample's graphs, and eval-log parsing into per-variant status + estimated score + failure classification. Use BEFORE every GPU evaluation (check_pattern), at the START of a sample (analyze_graph), and AFTER every evaluation (parse_eval_log).