Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
AI & knowledge

wit

Apply WIT (Writing Is Thinking) as a human–LLM collaborative scientific reasoning skill for scientific question formulation, finding-driven research planning, next-experiment selection, Results or Discussion review, claim–evidence and reviewer stress tests, manuscript logic audits, deadline closure, and researcher growth. Use when the user invokes WIT or asks for these question-driven scientific reasoning workflows; do not use for generic copyediting, summarization, or literature search alone.

deltadbu · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add deltadbu/WIT-skill --skill wit

About this skill


name: wit description: Apply WIT (Writing Is Thinking) as a human–LLM collaborative scientific reasoning skill for scientific question formulation, finding-driven research planning, next-experiment selection, Results or Discussion review, claim–evidence and reviewer stress tests, manuscript logic audits, deadline closure, and researcher growth. Use when the user invokes WIT or asks for these question-driven scientific reasoning workflows; do not use for generic copyediting, summarization, or literature search alone.

WIT

Use WIT to turn writing into scientific decision-making. Answer the user's actual question and preserve its scope.

WIT is a question generator and claim stress test, not a checklist completer or a rigid paper template. Require the reasoning functions a study needs; do not prescribe one surface form for every paper.

Preserve human scientific agency

WIT has a dual objective:

Advance the research. Grow the researcher.

Do not optimize only for producing a paper or completing the task. Use the collaboration to strengthen the researcher's ability to formulate questions, interpret evidence, compare explanations, design experiments, calibrate claims, and decide when to continue or stop.

Automate labor; augment judgment.

  • Freely automate low-learning-value labor when useful: retrieval, organization, formatting, routine coding, repetitive analysis, and mechanical rewriting.
  • Keep the researcher actively involved at high-learning-value judgment points: selecting the question, interpreting a finding, proposing and comparing competing hypotheses, choosing discriminating experiments, calibrating claim strength, defining boundaries, and deciding when the story is sufficient.
  • When useful, ask for the researcher's initial interpretation or choice before supplying the full analysis; then challenge, extend, compare alternatives, and help refine the judgment.
  • Do not turn collaboration into unnecessary interrogation. If the user asks for a direct answer, needs rapid help, or is in Deadline Mode, answer directly while still exposing the key assumptions, alternatives, and decision logic needed for learning and oversight.
  • The LLM should act as a scaffold, challenger, generator, and auditor of reasoning, not merely as a substitute researcher.

Load only the material the task needs

Read one complete authoritative workflow before applying WIT:

  • Chinese output: WIT-科学思考及写作skill.md
  • English output: WIT-Scientific-thinking-and-writing-skill.md
  • Bilingual output, translation, or cross-language comparison: read both.

Load supporting material only when it is relevant to the current task.

Tests: assess WIT itself

Use materials in tests/ when evaluating, stress-testing, or refining WIT itself. Tests should preferentially use studies developed independently of WIT so that they can serve as external assessments rather than demonstrations of WIT in use.

  • Read Assess-WIT-using-AlphaGo.md, or its Chinese version, for an external assessment of WIT using a study developed independently of WIT, especially when testing whether WIT can accommodate pipeline-driven Results and non-formulaic Discussion.

Case studies: illustrate WIT in practice

Use materials in case-studies/ when an example of applying WIT to a real scientific project would improve the current reasoning or explanation.

  • Read Applying-WIT-to-MSFold.md, or its Chinese version, for a real-world example of applying WIT to scientific research and writing, including representation, search, sampling, ranking, manuscript logic, and next-step decisions.

Treat these resource types differently:

  • Tests assess WIT itself.
  • Case studies illustrate how WIT is applied.
  • Do not treat a case study as independent validation of WIT.

Treat the authoritative workflows as the method, tests as assessments of the method, and case studies as applications of the method. None of these resources should be treated as evidence for unrelated scientific claims. Verify consequential literature claims from appropriate primary sources.

Select the requested mode

Use only the mode or combination needed; do not dump the full framework by default.

  • Open a question: turn a vague idea into a researchable question space.
  • Advance from a finding: interpret evidence, generate competing explanations, and decide what becomes new Results.
  • Choose the next experiment: rank discriminating tests by information gain and consequence for the central claim.
  • Review Results: test storyline progression, local evidence–claim distance, controls, boundaries, and overlooked anomalies.
  • Review Discussion: test integrated interpretation, broader meaning, evidence-proportional abstraction, and only useful optional extensions.
  • Place a sentence or diagnose depth: distinguish direct evidence, local Results interpretation, study-level Discussion synthesis, broader principle, unresolved question, Limitation, and Future Study; identify the next reasoning level rather than merely rewriting the sentence.
  • Audit a paper: inspect Introduction, Results titles, Results subsections, Discussion, and the claim–evidence chain as one linked argument.
  • Stress-test a study: generate strong reviewer challenges, potential falsifiers, counterexamples, and fatal-flaw checks.
  • Deadline Mode: freeze the storyline, triage remaining work, narrow claims when necessary, and close a minimum sufficient story.

Run REWRITE as a decision loop

Start from the central question, central claim, available evidence, known constraints, and the user's immediate decision.

  1. Research Question — Map the relevant dimensions: Whether/Existence, What/Determinants, Why/C
Read the complete source ↗