panjose/Co-Scientist / skills/hypothesis-review-summary
hypothesis-review-summary
VerifiedSummarize the completed reviews for a hypothesis.
hypothesis-review-summary
Goal:
- Summarize the completed reviews for a hypothesis.
Inputs:
hypotheses/<id>/HYPOTHESIS.json- completed review artifacts under
hypotheses/<id>/REVIEW/
Outputs:
hypotheses/<id>/REVIEW/REVIEW_SUMMARY.json
Context Loading:
- Read
hypotheses/<id>/HYPOTHESIS.json. - Read all completed review artifacts under
hypotheses/<id>/REVIEW/. - Focus on synthesizing the strongest strengths, weaknesses, and recommended next actions across those reviews.
Execution Prompt Contract:
- System Intent:
- You are synthesizing the completed review stack into a compact downstream summary.
- Required Reasoning Focus:
- Deduplicate repeated points across review stages.
- Preserve the most important strengths, weaknesses, and action items.
- Prefer high-signal synthesis over exhaustive restatement.
- Do Not Do:
- Do not summarize reviews that do not exist.
- Do not copy every review point verbatim.
- Do not invent a new evaluation framework at summary time.
- Review Quality Floor:
- A
status = completedreview summary must synthesize concrete findings from completed review stages. - Include the strongest actionable strength, weakness, or next-step implication when those appear in prior reviews.
- Do not use placeholder summary phrases such as
Viable evolved hypothesis,Refined from parent,strong candidate, orneeds validationas substantive summary content.
- A
- Output Shape:
- Produce the exact
ReviewSummaryContractfrompackages/agent_contracts/review.py. - Keep the summary as a compact list of downstream-usable points.
- Each item in
summariesmust be a plain string, not an object with nested keys such asreview_stage,outcome, orsummary.
- Produce the exact
Execution Steps:
- Open
skills/shared-references/schema-index.md, then readpackages/agent_contracts/review.pyand confirm the exactReviewSummaryContractshape before writingREVIEW_SUMMARY.json. - Read the current hypothesis and all completed review artifacts.
- Identify repeated themes and high-signal findings.
- Synthesize them into a compact summary list.
- Write
hypotheses/<id>/REVIEW/REVIEW_SUMMARY.json. - Validate before declaring completion.
Artifact Rules:
REVIEW_SUMMARY.jsonis a synthesis artifact, not a copy of all prior review text.- The summary must remain self-contained enough for downstream generation or ranking stages to consume quickly.
Completion Rule:
- This skill is complete only when
REVIEW_SUMMARY.jsonexists and is valid for downstream consumption.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |