research-experiment
暂无简介
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- id
- research-experiment
- title
- Structured Experiment Execution
03 SKILL.md 正文
Structured Experiment Execution
Test a hypothesis using a structured methodology that produces quantifiable results.
Process
- Read the hypothesis statement, test plan, and falsification criteria
- Design the experiment:
- Define what constitutes "treatment" vs "control" (or comparison groups)
- Identify the outcome measure
- Document potential confounders
- Execute the experiment — gather evidence through reasoning, literature analysis, or data analysis
- Compute effect size using Cohen's d or appropriate measure
- Estimate confidence interval
- Document methodology and limitations
- Determine outcome against falsification criteria
Effect Size Computation
Cohen's d:
d = (M_treatment - M_control) / SD_pooled
SD_pooled = sqrt((SD1^2 + SD2^2) / 2)
Magnitude: |d| < 0.2 negligible, 0.2-0.5 small, 0.5-0.8 medium, > 0.8 large
For qualitative evidence, estimate effect magnitude from evidence strength:
- Strong, consistent evidence: d ~ 0.8-1.2
- Moderate evidence: d ~ 0.4-0.7
- Weak or mixed evidence: d ~ 0.1-0.3
Output Schema
Each result must include:
status: supported, refuted, or inconclusiveeffectSize: with type, value, magnitudeconfidenceInterval: with lower, upper, levelevidence: array of observations with source and weightmethodology: description of approachlimitations: acknowledged weaknesses
Quality Criteria
- Every observation cites a source
- Effect size is computed and interpreted
- Methodology is documented
- Limitations are acknowledged
- Status is justified by evidence and falsification criteria
04 同仓库更多 Skills
hello-checker
Use this skill when asked to "verify", "check", or "validate" a file's existence and content. It provides a reliable workflow for confirming files meet their spec.
ask-skill
暂无简介
html-review-artifact
Framework-wide guidance for crafting polished human-review artifacts as markdown or HTML
converge-planning
Design a Converge playbook end-to-end. Use when the user says "plan a project", "design a playbook", "decompose into tasks", "scaffold a Converge workflow", "onboard to Converge", or asks how to write TASK.md / playbook.yml. Two entry points: plan a new playbook or update an existing one. Hand off to `/converge-control` after producing the playbook structure.
converge-control
Operate a Converge playbook end-to-end — start runs, monitor progress, narrow failures with `--select`, inspect runtime state, validate definitions, surgically reset subtrees, and stop stuck or orphaned runs. Use this skill whenever the user says "run my playbook", "execute this", "monitor the run", "converge failed", "the run is stuck", "retry failures", "babysit this playbook", "what's the status?", "show me the gantt", or asks how to use `converge run` / `--select` / `inspect` / `doctor` / `clean` / `stop`. Also use it for `HTTP 401` / `Invalid API key` failures on the first task — those are environment-not-playbook problems — and for any post-run cleanup work. Hand off to `converge-planning` if the user wants to design or restructure the playbook itself.
repair-taskts
Fix task.ts definition issues — Seed syntax, missing .build(), empty checks, import errors, TypeScript errors