ccf-experiment-designer
Design and interpret CCF experiments: datasets, baselines, metrics, ablations, run requirements, observed feedback, and result-table contents. Use for 设计实验, 消融, benchmark planning, 实验结果分析, and research evidence design.
Install / Use
npx skills add mikubaka88/CCFA-Skills --skill ccf-experiment-designerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Our assessment of ccf-experiment-designer
ccf-experiment-designer scores 90/100 on our quality scale, 429th of 1,153 Content & Media skills we index (top 38%).
Its SKILL.md is 7.6 KB long, well organised into 9 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,825 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ccf-experiment-designer is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ccf-experiment-designer compared with similar skills
All 4 of these similar skills score higher than ccf-experiment-designer; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ccf-experiment-designer (this skill)by mikubaka88 | 90 | 2.8k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| siyuanby siyuan-note | 100 | 47.3k | today | MCP Server |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
Frequently asked questions
- How do I install ccf-experiment-designer?
- Run
npx skills add mikubaka88/CCFA-Skills --skill ccf-experiment-designer. The install tabs above show the steps for each supported agent. - Which AI agents does ccf-experiment-designer work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ccf-experiment-designer safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ccf-experiment-designer still maintained?
- The repository was last updated about 2 months ago, so ccf-experiment-designer is actively maintained.
Skill content
View source on GitHubname: ccf-experiment-designer description: "Design CCF experiment protocols and evidence schemas: datasets, baselines, metrics, ablations, and result-table contents. Use for 设计实验, 消融, benchmark planning, and 结果表证据结构. Preserve real values. Table styling/rendering belongs to ccf-visual-composer; broad retrieval belongs to ccf-literature-searcher." metadata: ccf_skill_controls: handoff_question_mode: partial respect_session_denylists: true protect_idea_scope_in_writing: true private_material_safety: moderate shared_controls: ../ccf-common/references/
CCF Experiment Designer
Family File Contract
Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root ccfa-workfiles/<purpose>/<artifact-id>/, with source/, assets/, cache/, and build/ only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply artifact-contracts.md and reuse the same paths across skill transitions.
Collaboration Contract
Before specialist execution, read and apply ccf-humanization first, then ccf-common. At every handoff, reuse their applicable active rules or refresh missing/changed ones. Both preflights are required even without prose; detailed editing, experiment, and maintenance modes run only when relevant.
Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional cooperation routes; avoid unrelated stages and duplicate reports.
Invocation Controls
CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode, ../ccf-common/references/handoff-modes.md, and ../ccf-common/references/task-modes.md.
Activate Humanization and Common before all experiment work, including raw protocol planning and evidence schemas. When producing publication prose/tables/captions or changing executable experiments, load ../ccf-humanization/references/experiment-discipline.md as applicable, minimize smoke tests to unique changed critical paths, and verify complete method configurations for reported comparisons. These detailed checks are conditional; the family baseline is not. Describe the method and scientifically relevant configuration without exposing internal approval status. Keep unresolved version decisions outside publication artifacts without hiding material facts.
Core Rule
Design the smallest sufficient experiment package that distinguishes the central hypothesis from plausible alternatives. Use supplied specifications for planned methods; verify complete configurations for reported full-method comparisons. Build result tables and evidence-bound figure specs only from supplied real values or explicit placeholders. Never fabricate numbers, improvements, significance, benchmark ranks, or user-study outcomes. Do not expand protocols with repetitive smoke tests or implausible defensive cases. Publication-grade layout, palette, caption placement, and render QA belong to ccf-visual-composer. Follow the user's requested output shape: experiment plan, table, LaTeX table, figure spec, ablation list, or execution queue.
Modes
design: datasets, baselines, metrics, ablations, robustness, efficiency, failure analysis, and execution priority.result-template: fill-in tables withTBDplaceholders.result-presentation: result tables, figure evidence plans, chart specs, caption facts, and missing-value markers from supplied real results.
Workflow
- Identify the requested output after both family preflights. Raw protocol planning and evidence schemas use Humanization's baseline without a manuscript rewrite. Select detailed prose/experiment checks only when applicable, and establish claims and available evidence before method-version checks.
- Extract the storyline from the idea or draft. Reuse the supplied claim/mechanism description. Read
../ccf-paper-writer/references/storyline-blueprint.mdonly when the central claim needs clarification, not for an already specified result table. - Map every major claim to sufficient evidence, dataset/workload, confirmed baseline, metric, and mechanism-relevant ablation. Add robustness or failure tests only when observed, plausible, claim-relevant, or venue-required; do not enumerate remote defensive cases.
- Resolve missing dataset, baseline, metric, or protocol provenance through
ccf-literature-searcherbefore fixing dependent comparisons. Verify compatibility with the central claim. For a consequential unresolved claim-to-test mismatch, request a focusedccf-paper-reviewercheck and integrate its findings; do not create a full review report for a protocol question. Mark unavailable evidence instead of guessing. - Load
references/evidence-design.mdfor substantive protocol design orreferences/result-templates.mdfor table/schema work. Do not load both for a small task unless both are needed. - For result presentation, preserve units, seeds, confidence intervals, dataset names, metric direction, and confirmed method version/configuration. Mark missing values explicitly; never fill them with simplified runs.
- If executable experiment code is actually changed, retain only non-duplicative smoke tests for those critical paths. Planning or formatting alone does not call for smoke tests. Keep them outside publication evidence and do not use them as substitutes for full experiments.
- Use
ccf-visual-composerwhen the requested deliverable includes visual composition, layout, or rendering. Supply real values, units, uncertainty, metric direction, and caption facts; integrate and check the returned figure/table. A raw evidence schema does not require rendering. - Before finalizing reported comparisons, reconcile claims, numbers, and configurations; use
ccf-integrity-auditorfor material unresolved conflicts. Useccf-paper-writerfor needed manuscript prose andccf-submission-checkerwhen package readiness is in scope. These are conditional contributions, not stages to run for every plan.
Adaptive Output Contract
Return the requested artifact first. For a result table request, output the table. For a figure request, output the evidence-bound figure spec and caption facts, then name ccf-visual-composer as next owner for visual composition when needed. For a full experiment-design request, use this default structure:
Mode:
Venue and assumptions:
Claim-evidence matrix:
Dataset / benchmark needs:
Confirmed method / baseline versions:
Baseline matrix:
Main experiments:
Ablations:
Robustness / failure / efficiency:
Smoke scope and deduplication:
Result tables or figure specs:
Missing values:
Execution priority:
No-fabrication status:
Next CCFA owner:
References
references/evidence-design.md: experiment and benchmark design.references/result-templates.md: fill-in result tables and presentation scaffolds.../ccf-humanization/references/experiment-discipline.md: confirmed full method gate, simplified-version prohibition, smoke-test scope, and experiment-to-paper checks.../ccf-humanization/references/humanization-policy.md: warning-only, non-injection, and defensive-case removal policy.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
siyuan
47.3kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
