- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add agentsope/SkillAlchemy --skill agentsop-bio-fraud-forensics -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add agentsope/SkillAlchemy --skill agentsop-bio-fraud-forensics -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add agentsope/SkillAlchemy --skill agentsop-bio-fraud-forensics -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add agentsope/SkillAlchemy --skill agentsop-bio-fraud-forensics -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/agentsope/SkillAlchemy/tree/HEAD/skills/agentsop-bio-fraud-forensicsDe l'éditeur
A screening methodology for life-science papers. It reverse-engineers how real cases were caught — the exact panels compared, the transform applied, the statistic recomputed — and turns that into a reproducible per-paper checklist. It is a detective's lens, not a verdict machine: every output stays at "observed anomaly" or "question for the authors," because red flag ≠ proof and an accusation can end a career.
Trigger when:
.xlsx, or a DOI and asks if it's trustworthy.Do NOT trigger when:
Run this as a chain-of-steps. Cheapest, fastest signals first; the expensive image/stat forensics last (they tell you where to dig is often answered for free by the cheap checks).
Step 1 — Scope & status. Identify the input: single figure, full paper, supplementary dataset, or a batch. Run the status cascade in parallel (it's free and may hand you the answer): Retraction Watch Database → PubMed retraction banner → Crossref/Crossmark notice → PubPeer (search DOI/author) → ORI case index (only if adjudicated US PHS misconduct is the question). Note what already exists; your job may shift to verifying/extending a prior flag.
Step 2 — Ordered screen. Walk the pipeline, recording each hit; do not stop at the first:
.xlsx → calcChain.Step 3 — Match a model & classify. For each hit, Read references/sop_models.md, match the
operation model (M1–M7), and name the sub-type + Bik category. Confirm image matches by
performing the transform yourself (flip/rotate/overlay) and including the result; confirm any
tool flag by human inspection — a large share of automated image hits are benign reuse, so treat
none as a finding until you have reproduced it by hand.
Step 4 — Benign-explanation gate (mandatory before any escalation). Run the benign-explanation checklist in M6. Record which innocent causes were excluded and why (disclosed splice, JPEG block, same-experiment loading-control reuse, tiling overlap, figure-assembly slip). No "looks suspicious → flag." Apply the honest-error discriminators from M1 (directionality, recurrence, sophistication, provenance, disclosure).
Step 5 — Grade & document. Default every finding to Tier 1 (observed anomaly). Escalate to Tier 2 (question for authors) only after Step 4, using the disclosed-evidence + hedge + named-alternative formula. Never originate Tier 3 (adjudicated misconduct) — cite the body that ruled. Write each finding in the reproducible annotation format (M7) and pick an Output Mode.
Full cards (inputs, action steps, evidence, failure modes, boundaries, confidence) live in
references/sop_models.md. Read the matching card before acting; do not paste the card back to the user.
>-
---name: agentsop-bio-fraud-forensicsdescription: >----# skills/agentsop-bio-fraud-forensics/SKILL.mdFAQ
Téléchargez skills/agentsop-bio-fraud-forensics/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/agentsope/SkillAlchemy.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.