本文へ移動
cccskills
無料GitHub で公開

surveying-prior-work

Use after framing a question and before designing an analysis, or when choosing a method, judging whether a result is novel, or needing a prior effect size for a power calculation

インストール方法を見る

含まれるファイル(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Surveying Prior Work

Overview

Before designing an analysis, ground the question and your chosen methods in what is already known. Most questions have established methods, known confounds, and prior effect sizes. Reinventing a method badly — or rediscovering a known artifact and reporting it as a finding — wastes effort and erodes credibility.

Core principle: Find out what is already known before you generate new claims.

This is the science analog of reading the existing codebase before writing new code. It is a flexible skill — adapt depth to the stakes of the investigation.

When to Use

  • After framing-research-questions, before designing-the-analysis
  • When selecting a statistical method or model and unsure what is standard
  • When a result looks novel — check whether it is a known effect or artifact first
  • When you need a plausible prior effect size to power the study
  • When you suspect confounds but don't know which are established in the field

What to Ground

Survey four things:

  1. Established methods — what is the standard, accepted way to analyze this kind of question? What are its assumptions and failure modes?
  2. Known confounds and artifacts — what variables are known to drive this outcome? What measurement artifacts are common in this data type?
  3. Prior effect sizes — what magnitude have others found? This feeds the power/sample-size calculation in the analysis design.
  4. Relationship to prior work — is this a replication, an extension, a new population, or genuinely novel? Be honest about which.

The Process

  1. List what needs grounding — turn the "open questions for prior-work survey" from the question document into concrete search targets.
  2. Search — use web search and any available literature tools for published methods and effect sizes; search the repo and your human partner's prior analyses for in-house precedent and conventions.
  3. For broad surveys, dispatch parallel subagents — one per independent sub-topic (a method, a confound, a prior estimate). REQUIRED: use science-superpowers:dispatching-parallel-investigations for the workflow. This keeps your own context clean.
  4. Synthesize — write a short prior-work note (or a section appended to the question document):
    • Established method(s) you will adopt and why
    • Confounds you must measure or control for
    • Prior effect size(s) and the source, for powering the design
    • Honest statement of how this investigation relates to prior work
  5. Cite sources — record where each fact came from so the design and final report can reference it. When you present findings from web search, follow your platform's citation standards.

Red Flags

  • Reaching for a method you invented when a standard one exists → find and use the standard one (or justify the deviation explicitly)
  • Designing the analysis with no idea what effect size to expect → you skipped the power input; survey first
  • About to report something as novel without having checked → search first; novelty is a claim that needs evidence
  • Ignoring a confound because checking is inconvenient → known confounds are not optional

Handoff

After grounding, invoke science-superpowers:designing-the-analysis. Bring forward the adopted methods, the confound list, and the prior effect size for powering the design.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when you have an approved research question and need a concrete analysis plan, before touching outcome data or fitting any model

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

Use when facing 2+ independent investigations that can proceed without shared state - parallel literature survey, multi-dataset replication, or pre-specified robustness checks

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

Use when your human partner has explicitly opted into exploratory or feasibility mode - a compute-heavy simulation, an unproven pipeline, an unbenchmarked solver, an untested cluster job - or when whether the work can run at all is still unknown, when a plan's largest configuration has never been executed, when a memory or wall-clock ceiling is estimated rather than measured, or when someone proposes pre-registering over runs that have never happened

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

Use when you have a pre-registered analysis plan to execute inline in this session with review checkpoints, on a platform without subagents

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

You MUST use this before any data analysis or investigation - before exploring a dataset, loading or profiling data, running a model, computing a statistic, or testing an idea, and before any outcome data is touched

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

Use when a result is surprising, impossible, contradicts a sanity check, a pipeline fails, a model won't converge, or a replication fails - before adjusting anything

日本語の概要は準備中です。原文の説明を表示しています。

K-Dense-AI/science-superpowers3502026年9月13日 更新

K-Dense-AI のスキルをすべて見る

このスキルの問題を報告する