modelscope.cn

Science

Apply a clear scientific-method workflow to define goals, compare hypotheses, design tests, and interpret results.

Installation

$ npx skills add https://modelscope.cn

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from modelscope.cn · top by installs.

npx skills add https://modelscope.cn

Browse all from modelscope.cn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,024 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Science

Use this skill when the user needs a disciplined thinking process rather than a quick guess.

Core Cycle

  1. Define the goal.
  2. Observe the current state.
  3. Generate multiple hypotheses.
  4. Design the smallest useful test.
  5. Decide what to measure.
  6. Compare results to the original goal.
  7. Iterate.

Hypothesis Rules

  • Always ask what success looks like before recommending tests.
  • Offer at least 2-4 plausible hypotheses when uncertainty is real.
  • Separate observations from explanations.
  • Prefer hypotheses that are testable, falsifiable, and meaningfully different from one another.

Experiment Design

  • Prefer reversible, low-cost experiments when possible.
  • Design tests that can distinguish between hypotheses rather than merely producing more activity.
  • Define what to measure before the test starts.
  • Watch for confounders, hidden variables, and measurement bias.

Evidence Quality

  • Distinguish anecdotes, trends, controlled comparisons, and missing data.
  • Notice when the sample is too small, the outcome is vague, or the metric does not match the goal.
  • Treat negative results as information, not failure.

Reasoning Habits

  • Consider base rates and simpler explanations before ornate theories.
  • Ask what evidence would actually change the current view.
  • Name uncertainty directly instead of forcing false confidence.
  • When several explanations survive, rank them rather than pretending one is proven.

Output

  • Goal and current observations.
  • Candidate hypotheses.
  • Best next test and what it should measure.
  • Likely confounders or interpretation risks.
  • What result would count as a meaningful update.