Back to Details

results-report

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Results Report

实验结果报告

Write the complete post-experiment summary report after analysis artifacts are ready.
This skill is for the stage after 
results-analysis
.
在分析成果准备就绪后，撰写完整的实验后总结报告。
本Skill适用于
results-analysis
完成后的阶段。

Role boundary

角色边界

results-analysis
does

results-analysis
负责：

  • strict statistics,
  • real figures,
  • figure interpretation scaffolding,
  • stats appendix.
  • 严谨的统计分析，
  • 真实数据，
  • 图表解读框架，
  • 统计附录。

results-report
does

results-report
负责：

  • complete experiment wrap-up report,
  • decision-oriented narrative,
  • figure-by-figure interpretation inside a coherent structure,
  • limitations, failure cases, and next actions,
  • Obsidian write-back into 
    Results/Reports/
    .
When the task is to create or redesign paper-ready figures/tables themselves, rely on 
publication-chart-skill
instead of expanding 
results-report
into figure/table production.
Do not replace strict analysis with confident prose. If the analysis bundle is missing, first identify the blocker and request or produce the missing bundle.
  • 完整的实验总结报告，
  • 决策导向的叙述，
  • 在连贯结构中逐图解读，
  • 局限性、失败案例及后续行动，
  • 写入Obsidian的
    Results/Reports/
    目录。
当任务是创建或重新设计可用于论文的图表/表格时，请依赖
publication-chart-skill
，而非扩展
results-report
的功能来制作图表/表格。
请勿用主观表述替代严谨分析。若分析包缺失，需先明确障碍所在，请求或生成缺失的分析包。

Default output

默认输出

The default report is an internal research report, not manuscript prose.
It should be named as:
text
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md
Example:
  • 2026-03-18--freezing--r03--transfer-summary.md
  • 2026-03-18--contrastive-adversarial--r02--ablation-report.md
The note title should be:
text
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}
Read 
references/report-naming.md
before finalizing the filename or note title.
默认报告为内部研究报告，而非论文文稿。
报告命名格式如下：
text
YYYY-MM-DD--{experiment-line}--r{round}--{purpose}.md
示例：
  • 2026-03-18--freezing--r03--transfer-summary.md
  • 2026-03-18--contrastive-adversarial--r02--ablation-report.md
报告标题格式应为：
text
{Experiment Line} / Round {N} / {Purpose} / {YYYY-MM-DD}
最终确定文件名或报告标题前，请阅读
references/report-naming.md
。

Required frontmatter

必填前置内容

yaml
---
type: results-report
date: 2026-03-18
experiment_line: freezing
round: 3
purpose: transfer-summary
status: active
source_artifacts:
  - analysis-output/analysis-report.md
  - analysis-output/stats-appendix.md
linked_experiments:
  - Experiments/Freezing-Study.md
linked_results:
  - Results/Freezing-vs-Adapter.md
---
yaml
---
type: results-report
date: 2026-03-18
experiment_line: freezing
round: 3
purpose: transfer-summary
status: active
source_artifacts:
  - analysis-output/analysis-report.md
  - analysis-output/stats-appendix.md
linked_experiments:
  - Experiments/Freezing-Study.md
linked_results:
  - Results/Freezing-vs-Adapter.md
---

Default report structure

默认报告结构

The report must include all sections below.
  1. Executive Summary
  2. Experiment Identity and Decision Context
  3. Setup and Evaluation Protocol
  4. Main Findings
  5. Statistical Validation
  6. Figure-by-Figure Interpretation
  7. Failure Cases / Negative Results / Limitations
  8. What Changed Our Belief
  9. Next Actions
  10. Artifact and Reproducibility Index
Read 
references/report-structure.md
before writing.
报告必须包含以下所有章节：
  1. 执行摘要
  2. 实验标识与决策背景
  3. 实验设置与评估方案
  4. 主要发现
  5. 统计验证
  6. 逐图解读
  7. 失败案例/负面结果/局限性
  8. 认知更新
  9. 后续行动
  10. 成果与可复现性索引
撰写前请阅读
references/report-structure.md
。

Workflow

工作流程

1. Confirm the report object

1. 确认报告对象

Lock these fields first:
  • date,
  • experiment line,
  • round,
  • purpose,
  • linked experiment note,
  • linked durable result note if one already exists.
If round is unknown, do not silently invent a semantic round. Use 
r00
only as a temporary placeholder and state that it should be normalized later.
首先锁定以下字段：
  • 日期，
  • 实验系列，
  • 轮次，
  • 报告目的，
  • 关联的实验笔记，
  • 若已存在持久化结果笔记，需关联该笔记。
若轮次未知，请勿随意设定语义化轮次。仅可将
r00
作为临时占位符，并注明后续需规范调整。

2. Read the strict analysis bundle

2. 阅读严谨分析包

Minimum required inputs:
  • analysis-report.md
  • stats-appendix.md
  • figure-catalog.md
  • actual figures, if available
If these are missing, either generate them first with 
results-analysis
or explicitly state which claims cannot be supported.
所需的最低输入：
  • analysis-report.md
  • stats-appendix.md
  • figure-catalog.md
  • 实际图表（若可用）
若上述文件缺失，需先通过
results-analysis
生成，或明确说明哪些结论无法得到支持。

3. Write the report as a decision object

3. 撰写以决策为核心的报告

This report is not a transcript of outputs.
Each section must answer a real question:
  • What did we test?
  • What changed numerically?
  • What is actually supported?
  • What failed or remains uncertain?
  • What should we do next?
Read 
references/decision-oriented-analysis.md
for the expected reasoning depth.
本报告并非输出内容的转录。
每个章节必须回答实际问题：
  • 我们测试了什么？
  • 数据有哪些变化？
  • 哪些结论是有依据的？
  • 哪些部分失败或仍存不确定性？
  • 我们下一步该做什么？
如需了解预期推理深度，请阅读
references/decision-oriented-analysis.md
。

4. Interpret figures inside the report

4. 在报告中解读图表

Do not only attach figures.
For each main figure:
  • introduce why it is included,
  • state the key observation,
  • explain the supported interpretation,
  • explain the decision implication.
Read 
references/figure-interpretation.md
and 
references/statistical-completeness.md
as needed.
请勿仅粘贴图表。
针对每个主要图表：
  • 说明纳入该图表的原因，
  • 阐述关键观察结果，
  • 解释可支持的解读，
  • 说明对决策的影响。
必要时请阅读
references/figure-interpretation.md
和
references/statistical-completeness.md
。

5. Choose the write target explicitly

5. 明确选择写入目标

If the current repo is bound to an Obsidian project knowledge base:
  • create or update 
    Results/Reports/{report-name}.md
    ,
  • link back to the relevant 
    Experiments/
    note,
  • update the matching canonical 
    Results/
    note when a durable conclusion is now supported,
  • append a short trace to today's 
    Daily/
    note,
  • update 
    .claude/project-memory/<project_id>.md
    .
If the repo is not bound:
  • write the report as a local markdown artifact in the requested output location or next to the analysis bundle,
  • keep the same filename contract,
  • explicitly say that no Obsidian write-back was attempted.
Use 
obsidian-project-memory
conventions only for bound repos. Internal experiment reports belong in 
Results/Reports/
, not 
Writing/
.
若当前仓库绑定到Obsidian项目知识库：
  • 创建或更新
    Results/Reports/{report-name}.md
    ，
  • 关联至相应的
    Experiments/
    笔记，
  • 当得出持久化结论时，更新对应的标准
    Results/
    笔记，
  • 在当日的
    Daily/
    笔记中添加简短记录，
  • 更新
    .claude/project-memory/<project_id>.md
    。
若仓库未绑定：
  • 在指定输出位置或分析包旁生成本地Markdown格式的报告，
  • 遵循相同的命名规则，
  • 明确说明未尝试写入Obsidian。
仅在绑定仓库中使用
obsidian-project-memory
约定。内部实验报告应存放于
Results/Reports/
，而非
Writing/
目录。

6. End with explicit next actions

6. 以明确的后续行动收尾

The report must end with operational decisions, for example:
  • stop a weak branch,
  • schedule one missing ablation,
  • promote a stable finding into manuscript-facing writing,
  • update the active plan.
报告必须以可执行的决策收尾，例如：
  • 终止表现不佳的分支，
  • 安排缺失的对照组实验，
  • 将稳定的发现推进至论文撰写阶段，
  • 更新当前计划。

Required quality bar

质量要求

  • The report must be dateable, searchable, and attributable to one experiment line and one round.
  • The report must cite actual evidence from the analysis bundle.
  • The report must include negative results when they matter.
  • The report must separate stable conclusion from tentative interpretation.
  • The report must say what changed in project belief and what should happen next.
  • 报告必须可标注日期、可搜索，并关联到特定实验系列和轮次。
  • 报告必须引用分析包中的实际证据。
  • 若负面结果有意义，必须纳入报告。
  • 报告必须区分稳定结论与初步解读。
  • 报告必须说明项目认知有哪些更新，以及后续应采取的行动。

Reference files

参考文件

Load only what is needed:
  • references/report-structure.md
  • references/report-naming.md
  • references/figure-interpretation.md
  • references/statistical-completeness.md
  • references/decision-oriented-analysis.md
  • references/EVIDENCE-PROPAGATION.md
  • examples/example-results-report.md
按需加载以下文件：
  • references/report-structure.md
  • references/report-naming.md
  • references/figure-interpretation.md
  • references/statistical-completeness.md
  • references/decision-oriented-analysis.md
  • references/EVIDENCE-PROPAGATION.md
  • examples/example-results-report.md