Skip to content
Back to skills

Finding Rewriter

ASecurity

Rewrites each auto-extracted Finding cell in a Fetchproof project's research/EVIDENCE.md into a real claim - what the cached page establishes, with the number or rule that proves it and a word-for-word [quote: ...] from the capture - keeping the Raw cell pointing at the capture. Use on a collector after research.mjs collects, when preflight reports quote or finding problems, or when the user asks to rewrite or review the findings.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 22, 2026
ai-agents

Works with

  • cli

Security analysis

A100/100

Scanned October 22, 2026

npx -y skills add StepenkoAnatoli/Fetchproof --skill finding-rewriter --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Finding Rewriter?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Finding Rewriter
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/stepenkoanatoli-finding-rewriter/badge)](https://www.skillsdirectory.com/skills/stepenkoanatoli-finding-rewriter)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: finding-rewriter
description: Rewrites each auto-extracted Finding cell in a Fetchproof project's research/EVIDENCE.md into a real claim - what the cached page establishes, with the number or rule that proves it and a word-for-word [quote: ...] from the capture - keeping the Raw cell pointing at the capture. Use on a collector after research.mjs collects, when preflight reports quote or finding problems, or when the user asks to rewrite or review the findings.
---

# Finding rewriter

`research.mjs` fills each `Finding` cell with an extracted sentence. It is a pointer into
the page, not a claim. Rewriting it is the second review step of phase 1.

## Each row

1. Open the capture the `Raw` cell names, under `research/raw/`.
2. Write what the page **establishes** for the unknown it was collected for - the
   number, the rule, the field, the limit - in your own words, concretely.
3. Add the sentence it rests on as `[quote: ...]`, copied from the capture **word for
   word, on one line** of the capture. The gate checks it occurs there (ADR-0087); a
   sentence that wraps across two lines in the capture fails - quote the part on one line.
4. Say what the page does **not** establish, when a reader would assume it does.
5. Never put a `|` in the cell; it breaks the table.

## Rules

- Never edit the capture, the `Raw` cell, or `research/raw/.fetches.jsonl`. An edited
  capture fails the gate and blocks every commit.
- A thin or client-rendered capture (`raw-thin`) is not cited for the fact. Say so in its
  Finding, and collect the page that owns the fact as text.
- A claim the page does not support is not written, however likely it is.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.