How do I install the Pre Write Recall Check skill?

Run npx skillmds@latest add yogsoth-ai/pre-write-recall-check in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pre Write Recall Check safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pre Write Recall Check?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pre Write Recall Check free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pre Write Recall Check?

yogsoth-ai (@yogsoth-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pre Write Recall Check by yogsoth-ai

Name: Pre Write Recall Check
Author: yogsoth-ai

Pre Write Recall Check

Independently extract a paper's most important atomic facts directly from the raw source (before looking at the bundle at all), then check whether the bundle covers each one — catching content the bundle omitted. Use this before any article drafting begins, alongside pre-write-precision-check, immediately after extract-structured-bundle produces the bundle. This is a distinct check from precision-check — it catches omissions, not wrong claims — and must never be merged into it.

yogsoth-ai 2ae628d 2 files · 4.2 KB Updated Sep 17, 2026

File contents

Pre-Write Recall Check

Nugget-coverage method (adapted from TLDR/SciTLDR research): independently extract the paper's most important facts from raw source BEFORE looking at the bundle, then check bundle coverage. Catches omission errors — important content the bundle left out.

Execution

Subagent — spawned via subagent-spawning/spawn-agent skill.

Why Subagent

Independent nugget extraction must happen in a context that hasn't yet seen the bundle — reading the bundle first and then asking "did we miss anything?" biases the check toward confirming what's already there rather than discovering what's missing.

Why This Is a Separate SOP From pre-write-precision-check

Precision checks whether stated claims are supported (commission errors); recall checks whether important content was left out (omission errors). These have different mechanisms (checking existing claims vs. independently generating a reference set) and different failure remedies (retry_deep_read vs. retry_deep_read_supplement per failure-routing) — see design spec §2 point 1. Do not collapse this sop's logic into pre-write-precision-check.

Available SOPs

Optional, no fixed order; the final leaf is always a sop.

SOP	When to use
spawn-agent	Spawn a customized CC subagent with full MCP tool access.
literature-research	Full-text paper reading via alphaxiv. Import from literature-engine.

---name: pre-write-recall-checkdescription: Independently extract a paper's most important atomic facts directly from the raw source (before looking at the bundle at all), then check whether the bundle covers each one — catching content the bundle omitted. Use this before any article drafting begins, alongside pre-write-precision-check, immediately after extract-structured-bundle produces the bundle. This is a distinct check from precision-check — it catches omissions, not wrong claims — and must never be merged into it.---# Pre-Write Recall CheckNugget-coverage method (adapted from TLDR/SciTLDR research): independently extract the paper's most important facts from raw source BEFORE looking at the bundle, then check bundle coverage. Catches omission errors — important content the bundle left out.## ExecutionSubagent — spawned via subagent-spawning/spawn-agent skill.## Why SubagentIndependent nugget extraction must happen in a context that hasn't yet seen the bundle — reading the bundle first and then asking "did we miss anything?" biases the check toward confirming what's already there rather than discovering what's missing.## Why This Is a Separate SOP From pre-write-precision-checkPrecision checks whether stated claims are supported (commission errors); recall checks whether important content was left out (omission errors). These have different mechanisms (checking existing claims vs. independently generating a reference set) and different failure remedies (retry_deep_read vs. retry_deep_read_supplement per failure-routing) — see design spec §2 point 1. Do not collapse this sop's logic into pre-write-precision-check.## Available SOPsOptional, no fixed order; the final leaf is always a sop.| SOP | When to use || --- | --- || spawn-agent | Spawn a customized CC subagent with full MCP tool access. || literature-research | Full-text paper reading via alphaxiv. Import from literature-engine. |

Frequently asked questions