publish-what-the-run-already-computed

Solid

Use at Stage 06 and again before the report is finalised, when deciding which of the run's results enter the deliverable. Sweeps the run's own outputs for quantities it computed and never published, and covers the three shapes that sweep finds — the diagnostic never persisted, the column requested and dropped, the feasibility measurement discarded — and what to promote out of an appendix.

AI & Automation 804 stars 25 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 82/100

Stars 20%
97
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# The most expensive result is the one you computed and did not show The work was done. The compute was spent. The number is on disk. And the report does not contain it — because the report's contents were chosen by the run's own hypothesis structure, and a quantity produced in service of a hypothesis but not adjudicating one has no section to live in. This skill is the sweep that finds those. It is about the run's *outputs*; `the-supplied-item-is-the-graded-unit` is about the *inputs* — the named objects in `data/` — and covers printing those objects rather than pointing at them. Run both. This one catches what that one cannot: a quantity nothing shipped and nothing asked for by name, which the run computed anyway because the analysis needed it. ## The sweep Before you fix a section order or polish a sentence, do this once: 1. List every file the run wrote under the results and outputs directories, with what it *holds* — not the path, the content: "per-epoch pre-training loss", "sequence identity per aligned chain pair", "the 497-row permutation-importance table", "seconds per optimiser step for the long-range and short-range heads". 2. Against each, write the section of the report where it appears. Grep the report for a number out of the file; if none is there, the entry is empty. 3. For every empty entry, ask: **would a reader checking the task's outputs, or the source study's own results, look for this?** If yes, it goes in the body before you do an...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
5 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

sweep

Write every daily taskops report that is still missing — the unattended backfill. Use when a scheduled task fires, when the machine has been off for days, or when the user asks to "catch up the reports", "escribí los días que faltan", or to fill a hole in the report history.

0 Updated 3 days ago
bernatch22
Data & Documents Listed

report

Runs a data, measurement, root-cause or comparison study and delivers it as a dated, self-contained single-file HTML report. Use when the user says "/report", "analyse this data", "write a report", "measure this", "compare A and B", "find the root cause", "characterise this", "which one is better", "summarise these logs", or the Turkish equivalents "analiz et", "rapor çıkar", "raporla", "ölç", "karşılaştır", "kök neden bul". Fits log/CSV/raw-data studies, A-B comparisons, tuning, performance measurement, regression investigation, survey and metric summaries. Do NOT use for reviewing source code — that is audit — or for plain reading and searching a codebase.

0 Updated today
olcayseygan
Data & Documents Listed

report

Write the final summary of an autoresearch run to `./.ar/final_report.md` — trajectory, best commit and its diff, what worked, what failed, and what to try next. Use for `/ar:report`, "write up the autoresearch results", or "summarise the experiment loop". Reads `./.ar/ar.jsonl` from disk, so it works in a fresh session. Writes only the report; never iterates, commits, or reverts, and leaves the loop able to continue.

3 Updated 2 weeks ago
emaballarin