preclinical-safety-assessment
Skill53 starsChanged 55 days agoApache-2.0View on GitHub
Interpret preclinical toxicology studies, compute therapeutic index and hERG safety margins, and assess genotoxicity batteries — repeat-dose study data, cross-artifact margin calculation, ICH S2(R1) weight-of- evidence genotoxicity assessment, and safety pharmacology recording. Use when interpreting tox study results for safety margin evaluation, computing therapeutic index from NOAEL exposure and PK data, assessing a genotoxicity battery, or evaluating measured hERG IC50 margins. Do not use for predicted ADMET endpoints (use admet-property-prediction), for in vivo PK parameters or NCA analysis (use in-vivo-pk-analysis, though PK data is a required input here), or for compound drug-likeness rules and structural alerts (use compound-property-profile).
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use this skill when you need to interpret preclinical toxicology data and compute safety margins.
- Very specific: line 59
oase doctor: run before first use. It ends with a verdict line: STOP means fix or report. - Very specific: line 73
Run phase 1 (ingest, genotox, margins) before phase 2 (analyze).
- Very specific: line 173
When a safety-pharm artifact with measured hERG IC50 is available, the measured hERG margin from tox margins supersedes the predicted …
- Very specific: line 212
Reporting a mixed genotox battery as negative: When the tox.genotox_weight_of_evidence relay fires, the battery had mixed results.
- Very specific: line 216
Carrying both predicted and measured hERG findings: When a measured hERG IC50 margin is available from tox margins, it supersedes …
- Distinctive: line 227
Do not supply a value in prose or in a finding.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
1. When to use, and when not
Use this skill when you need to interpret preclinical toxicology data and compute safety margins. Entry points include:
- Ingesting and normalising repeat-dose, safety pharmacology, or genotoxicity study data for downstream analysis.
- Computing therapeutic index (TI) from NOAEL exposure and PK NCA data — cross-artifact margin calculation requiring both tox and PK artifacts.
- Assessing a genotoxicity battery using ICH S2(R1) weight-of-evidence classification.
- Computing measured hERG IC50 safety margins from safety pharmacology data and PK exposure.
- Applying the
tox-safety-packagethreshold set to produce verdicts on margins, genotoxicity, or safety pharmacology artifacts.
Do not use when:
- You need predicted ADMET endpoints (metabolic stability, permeability,
predicted hERG structural flag) ->
admet-property-prediction. - You need in vivo PK parameters, NCA analysis, or allometric scaling
->
in-vivo-pk-analysis(though PK NCA artifacts are a required input for margin calculation here). - You need compound drug-likeness rules or structural alerts
->
compound-property-profile.
2. Preconditions
- Input schemas: canonical JSON matching one of:
oase.tox-repeat-dose.v1— repeat-dose study data (for ingest, margins).oase.tox-safety-pharm.v1— safety pharmacology data with measured hERG IC50 (for ingest, margins--herg, analyze).oase.tox-genotox.v1— genotoxicity battery results (for ingest, genotox).
- Cross-artifact dependency:
tox marginsrequires BOTH a tox repeat-dose artifact AND a PK NCA artifact (oase.pk-nca.v1, produced byin-vivo-pk-analysis). Optionally takes a safety-pharm artifact via--hergfor measured hERG IC50 margin calculation. PK data is a precondition for margin computation — runin-vivo-pk-analysisfirst. oase doctor: run before first use. It ends with a verdict line:STOPmeans fix or report;PROCEEDmeans work.- No authentication needed — all operations are local.
- No network — all subcommands are offline.
3. Tool invocations
| Question | Run | Writes to |
| Ingest and normalise a tox study? | oase tox ingest <INPUT_FILE> | raw/tox/{id}.tox-repeat-dose.json + .meta.json<br>raw/tox/{id}.tox-safety-pharm.json + .meta.json<br>raw/tox/{id}.tox-genotox.json + .meta.json |
| Assess a genotoxicity battery? | oase tox genotox <GENOTOX_ARTIFACT> | raw/tox/{compound_id}.tox-genotox-assessment.json + .meta.json |
| Compute therapeutic index and hERG margins? | oase tox margins <TOX_FILE> <PK_FILE> [--herg <SAFETY_PHARM>] | raw/tox/{study_id}.tox-margins.json + .meta.json |
| Apply thresholds and produce verdict? | oase tox analyze <ARTIFACT> | raw/tox/{stem}.tox.analysis.json |
Run phase 1 (ingest, genotox, margins) before phase 2
(analyze). analyze reads from disk and can be re-run with different
thresholds without recomputing.
ingest dispatches on the schema field in the input JSON — one
command handles all three study types.
4. Interpretation contract
Verdicts
analyze applies the tox-safety-package@1.0 threshold set and
emits per-artifact-type verdicts:
Margins analysis (oase.tox-margins.v1):
- acceptable — TI and hERG margins (when present) meet thresholds.
- flagged — one or more margins below threshold.
- incomplete — NOAEL exposure data not available; TI cannot be computed.
Genotox analysis (oase.tox-genotox-assessment.v1):
- acceptable — battery negative, no genotoxic concern.
- flagged_equivocal — mixed results, in vitro positive / in vivo negative pattern (equivocal).
- flagged_concern — positive or mixed results indicating genotoxic concern (includes all-positive, in vivo positive, or preponderance positive batteries).
- unknown — battery verdict not classifiable.
Safety-pharm analysis (oase.tox-safety-pharm.v1):
- recorded — safety pharmacology data recorded. Quantitative hERG
margin requires running
tox marginswith both PK and safety-pharm artifacts.
Genotox battery classification
tox genotox classifies the battery result per ICH S2(R1):
- negative — all assays negative.
- positive — all assays positive.
- equivocal — in vitro positive / in vivo negative (WoE needed).
- concern — in vivo micronucleus positive with mixed results (WoE needed).
- positive_concern — 2+ positive results in a mixed battery (WoE needed).
Thresholds
The tox-safety-package@1.0 threshold set provides:
ti_minimum— minimum acceptable therapeutic index fold-margin (ICH M3(R2)).herg_safety_margin— minimum hERG safety margin fold (ICH S7B).herg_marginal— operational boundary below the full hERG margin.noael_exposure_margin— UNRESOLVED. This threshold has no defensible default value. It is entirely program-specific. Do not invent a value — set it via.oase/thresholds.yamlper program and record the justification.
Thresholds are cited by name. The values in force are in the artifact:
every .analysis.json carries threshold_set, thresholds_applied,
threshold_sources, and threshold_provenance. Quote values from the
analysis being cited, never from prose.
Mandatory relays
| Relay code | Kind | Fires when | Obligation |
tox.genotox_weight_of_evidence | Qualifier | Genotox battery has mixed results requiring weight-of-evidence reasoning (conditional) | State that this genotoxicity assessment used ICH S2(R1) weight-of-evidence reasoning because the battery results were mixed. Do not report the verdict as a clean negative — name the positive assay and the basis for the overall assessment. |
Upstream relay forwarding. tox margins reads the PK NCA sidecar
and forwards any upstream mandatory relays (e.g.,
pk.nca_assumes_linearity). Any upstream relay present in the margins
.meta.json must also be satisfied in the finding. Check
mandatory_relays in both the .analysis.json and in each phase-1
.meta.json.
Consequence rules
- Margins acceptable: state the verdict, the threshold set, and which margins were computed (TI Cmax, TI AUC, hERG). Proceed to downstream work.
- Margins flagged: state which margins are below threshold and by
how much (from the analysis, not from recomputation). A flagged TI
below the configured
ti_minimumis a substantive safety concern. A flagged hERG margin betweenherg_marginalandherg_safety_marginwarrants attention; belowherg_marginalis elevated concern. - Margins incomplete: NOAEL exposure data was absent. The NOAEL dose is recorded but TI cannot be computed without measured exposure. This is not a failure — it is a data gap that requires toxicokinetic (TK) data.
- Genotox acceptable: battery negative, no genotoxic concern.
- Genotox flagged: state the battery classification and the
weight-of-evidence basis. Satisfy the
tox.genotox_weight_of_evidencerelay if present. - Safety-pharm recorded: data is recorded but quantitative margin
assessment requires running
tox marginswith both PK and safety-pharm artifacts.
Stage 3 to Stage 4 boundary
When a safety-pharm artifact with measured hERG IC50 is available, the
measured hERG margin from tox margins supersedes the predicted
structural flag from Stage 3 ADMET (admet.herg_structural_flag). A
measured IC50 and computed safety margin are direct evidence; a
pharmacophore-based prediction is indirect. Do not carry both the
measured margin and the predicted flag as independent findings — the
measured margin replaces the prediction.
Cross-disciplinary consequences
- The therapeutic index assumes the PK file represents exposure at the
intended therapeutic dose.
oase.pk-nca.v1does not tag dose context — this assumption cannot be verified from the artifact alone. - A margins artifact without hERG data does not imply hERG safety — it means the measurement was not provided.
- Genotox battery classification is categorical. No threshold application occurs for genotox — the verdict maps directly from the battery result pattern.
- Safety-pharm data recording does not substitute for quantitative
margin calculation. The hERG IC50 value is captured but not compared
to therapeutic exposure until
tox marginsis run with both artifacts.
5. Failure modes and anti-fabrication guard
Do not compute these values yourself. The value is whatever the tool emitted. If the tool did not run, there is no value. If a required tool is unavailable, report the task as blocked. Do not estimate, and do not proceed on an assumed result.
Named pathologies
- Computing TI without PK data.
tox marginsrequires both a tox repeat-dose artifact and a PK NCA artifact. Do not estimate a therapeutic index from the NOAEL dose alone — exposure-based TI requires measured exposure data. - Treating an incomplete margins verdict as acceptable. Incomplete means TI could not be computed, not that the margin is adequate. A missing TI is a data gap, not a pass.
- Reporting a mixed genotox battery as negative. When the
tox.genotox_weight_of_evidencerelay fires, the battery had mixed results. The verdict is the classification after WoE reasoning, not a clean negative. - Carrying both predicted and measured hERG findings. When a
measured hERG IC50 margin is available from
tox margins, it supersedesadmet.herg_structural_flag. Do not present both as independent lines of evidence. - Ignoring upstream PK relays on the margins artifact.
tox marginsforwards upstream relays from the PK sidecar (e.g.,pk.nca_assumes_linearity). Every forwarded relay must be satisfied in the finding — they are not tox-specific, but they apply to the TI calculation that depends on the PK data. - Inventing a value for
noael_exposure_margin. This threshold is UNRESOLVED and program-specific. The CLI will refuse to apply it. Do not supply a value in prose or in a finding.
6. Provenance
Therapeutic index convention references ICH M3(R2) general guidance
for starting dose selection and safety margin assessment. hERG safety
margin references ICH S7B (adopted 2005) for the recommended margin
between therapeutic free plasma Cmax and hERG IC50. Genotoxicity
battery assessment references ICH S2(R1) for weight-of-evidence
evaluation of mixed battery results. Provenance details are stamped in
every .analysis.json via threshold_provenance.
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- terravic/pde-agent-plugin★ 096% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository82 other files it gives its agents.
- applications/open-agentic-science-engine/templates/admet-dmpk-scientist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/bootstrapper/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/computational-biologist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/computational-chemist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/experimental-biologist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/finding-validator/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/head-of-discovery/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-evolution/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-generation/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-meta-review/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-proximity/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-reflection/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-supervisor/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/hypex-tournament/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/medicinal-chemist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/preclinical-toxicologist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/project-curator/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/regulatory-scientist/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/research-operations-controller/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/science-program-lead/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/scientific-reviewer/agents.mdAGENTS.md
- applications/open-agentic-science-engine/templates/structural-biologist/agents.mdAGENTS.md
- cost-estimationSkill
- database-queriesSkill
- job-managementSkill
- job-submissionSkill
- results-analysisSkill
- storage-managementSkill
- visualizationSkill
- admet-property-predictionSkill
- artifact-conventionsSkill
- binding-mode-analysisSkill
- bioactivity-landscapeSkill
- brain-atlasSkill
- citation-resolutionSkill
- citation-verificationSkill
- competitive-differentiationSkill
- compound-identity-resolutionSkill
- compound-property-profileSkill
- debate-protocolSkill
- disease-transcriptomicsSkill
- elo-tournamentSkill
- evolution-operatorsSkill
- hypex-tool-setupSkill
- hypothesis-entrySkill
- hypothesis-run-corpusSkill
- hypothesis-schemaSkill
- in-vivo-pk-analysisSkill
- literature-searchSkill
- manufacturing-feasibilitySkill
- meta-review-protocolSkill
- model-organism-phenotypeSkill
- pocket-druggabilitySkill
- program-state-managementSkill
- protein-structure-confidenceSkill
- proximity-protocolSkill
- regulatory-variant-effectSkill
- review-rubricSkill
- run-protocolSkill
- safety-screenSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

