act-like-a-chemist
Optional chemistry reasoning workflow for structure, mechanism, calculation, literature, protocol, and evidence-sensitive tasks.
SKILL.mdskills/act-like-a-chemist/SKILL.md
GitHubAct Like A Chemist
This optional workflow supports careful chemistry reasoning: track evidence, verify uncertain chemical claims, conserve atoms and charge, keep units explicit, and show enough of the reasoning path for the final answer to be auditable.
Non-Negotiables
- Do not fill missing chemistry facts with plausible memory when a tool or source can check them.
- Separate facts as
given,derived,tool-verified,source-supported, orassumption. - If a claim is uncertain and material to the answer, verify it before relying on it.
- If the same tool path is unavailable or fails twice, stop retrying that path, state the limitation, and continue with bounded reasoning.
- Do not skip task-relevant derivation steps, option checks, source checks, or uncertainty notes needed to make the final answer auditable.
Standard Answering Flow
- Identify the task type, answer format, structures, conditions, images, data tables, and external-source requirements.
- Write a compact Atomic Coverage Checklist using the relevant task template below. Split the solution path into atomic tasks, including known givens, formulas, unit conversions, intermediate values, mechanism steps, comparison classes, prompt constraints, and final-answer slots. Use
todountil each atom is locally solved,doneonly after its derivation or evidence is complete, andblockedfor atoms that cannot be resolved after bounded verification. - If provider skills would help, use
contract/skill-triggers.mdas a capability reference for concretetodoatoms. Before each tool call, name the exact atom it should inform and the expected output shape. - Solve step by step, checking conservation, units, structures, and source facts. After each tool result, classify what it does for the targeted atom:
supports,partially supports,contradicts, oronly verifies an intermediate step. Mark an atomdoneonly after that exact task is satisfied; a useful tool result does not close neighboring atoms. - Write a compact fact ledger for the important claims:
given: directly stated by the prompt or attached material.derived: obtained by calculation, conservation, or mechanism reasoning.tool-verified: checked with a local skill or tool.source-supported: checked against a retrieved paper, database, or provided source.assumption: necessary but unverified; mark the risk.
- When all atoms are
doneorblocked, run a final consistency review: Re-check everyblockedatom to see whether prompt evidence, derivation, or earlier tool output now resolves it; confirm each completed atom appears in the answer plan; verify final values, units, dimensionality, rounding, formula or concept fit, structure/count/option constraints, and comparison cases one by one. - Organize all atomic reasoning steps into a smooth, complete reasoning trace, preserve all verified visible checkpoints, and output in the requested format.
Atomic Coverage Checklist
For chemistry questions, start visible work by writing a compact Atomic Coverage Checklist. It is a high-granularity solution outline, not just a list of unknowns. Include atomic tasks for prompt-provided facts and known givens as well as unknowns, because the final answer must visibly carry the whole reasoning path.
Use only these states:
todo: an atomic task that is part of the solution path and has not yet been shown.done: an atomic task whose local derivation, prompt support, source evidence, or scoped evidence is complete.blocked: an atomic task that cannot be resolved within the available tools or after the allowed failure budget.
Build atoms at the granularity a grader would need to award visible reasoning credit:
- givens and known prompt facts that must be reused in calculations or comparisons;
- requested output format, units, rounding, and final-answer slots;
- formulas, substitutions, conversions, algebraic systems, and intermediate values;
- mechanism steps, reactive roles, oxidation states, bond changes, site/structure constraints, and competing pathways;
- all options, candidates, catalyst/material variants, protocol changes, or comparison classes named by the prompt;
- source-specific entities, assay/protocol conditions, named intermediates, spectra peaks, identifiers, and experimental observations.
Numeric, Formula, Or Table Tasks
todo: atomize requested quantity, prompt givens, formula/law, unit conversions, table values, substitutions, intermediate values, algebraic solves, rounding rule, and final value.done: each atom is visibly derived or checked, and final precision matches the prompt.blocked: missing table/image/source value, inconsistent units, or unavailable calculation verification after two failed attempts.
Multiple-Choice Tasks
todo: atomize answer format, all provided options/images, discriminating criteria, and accept/reject checks for each option or option group.done: every plausible option has a visible accept/reject reason tied to structure, mechanism, calculation, or source evidence.blocked: an option depends on unavailable source/image/tool evidence after two failed attempts; choose from remaining evidence and state the limitation.
Research Or Open-Ended Tasks
todo: atomize source-specific claims, required entities, mechanisms, assays, protocols, materials, calculations, named comparison cases, and final synthesis slots.done: each material atom is supported by retrieved/provided sources, scoped evidence, or explicit derivation, with uncertainty separated from facts.blocked: full text, database record, identifier resolution, or provider access remains unavailable after two failed attempts.
Candidate / Hypothesis Verification
- Treat tool results as evidence, not verdicts. If a tool checks a guessed answer, state whether it verifies an intermediate step or the decisive final-answer condition.
- When enumeration is needed, first use deterministic prompt constraints, conservation laws, formula/mass/charge limits, symmetry, option constraints, or required mechanism steps to narrow the candidate set. Then enumerate and verify the reduced plausible set. Do not enumerate every possible candidate first and test them one by one when deterministic reasoning can shrink the space.
- When plausible competing candidates exist, compare the key candidates side by side before choosing. Do not verify only the first candidate that gives a usable tool result.
- A database hit, formula match, approximate numeric match, valid structure, or retrieved source can establish local support. It is not sufficient final-answer evidence unless it also satisfies the task's discriminating constraints or the competing candidates have been rejected.
Numerical Discipline
- Write units for all quantities and convert before calculation.
- Show the formula, substituted values, important intermediate numbers, and final rounding.
- Match the prompt's requested precision. If the benchmark or source uses a specific intermediate path, preserve the same path when visible from the prompt or retrieved material.
- When a numeric result determines identity, composition, or formula, solve for the unknown directly when possible before testing named candidates.
- If using candidate verification for a numeric identity task, compare residuals for nearby or chemically plausible competitors. Do not accept a candidate only because it is approximately close.
- Do not hide a numeric answer behind a qualitative explanation when the question is calculation-based.
Research And Source Discipline
- If the question asks about a named paper, protocol, material, biological target, assay, or source-specific claim, retrieve or inspect the source before answering when tools are available.
- Prefer source facts over generic chemistry priors when they conflict.
- Record weak coverage honestly: missing full text, sparse retrieval, unavailable provider, ambiguous structure, or unresolved identity.
- Do not invent citations, DOIs, protocols, reagent roles, targets, or stability windows.
Final Answer Discipline
- Include a visible trace: decisive structures, mechanism checkpoints, calculations, source facts, and uncertainty notes.
- For multiple-choice tasks, evaluate each option or group of related options against the trace before selecting.
- For open-ended tasks, finish with the exact final-answer format requested by the prompt.
- Keep tool exploration proportionate to the time budget; stop starting new tool paths when time is nearly exhausted.
Visible Trace Contract
- Multiple-choice: show option checks or grouped option eliminations, name the decisive structure/mechanism/evidence distinction, then finish with
FINAL ANSWER: <letters>. - Numeric: show the governing formula, unit conversions, substituted values, intermediate numbers, rounding choice, and final answer line.
- Research/source tasks: show a compact fact ledger, source or tool evidence for material claims, the mechanism/calculation chain, any remaining uncertainty, and final synthesis.
- If evidence is already sufficient to answer because every checklist atom is fully covered or explicitly blocked, stop exploring tools and produce the final answer. Do not stop only because one tool call returned a useful or promising intermediate result.
- If paper or web paths return 403, 429, empty results, or unavailable payloads twice in total, stop broadening that path and answer from available evidence with the limitation marked.