# Scrape To Gated Claims

> Use when Apify/scrape rows must become trusted memory. Runs structured scrape then evidence/scope/conflict gates before commit.

- Skill: `cassidyrice/scrape-to-gated-claims` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx skillmds@latest add cassidyrice/scrape-to-gated-claims`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cassidyrice/scrape-to-gated-claims/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cassidyrice (https://skillmd.com/u/cassidyrice)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/cassidyrice/scrape-to-gated-claims

---


# Scrape → Gated Claims

**Source × gate:** Actor datasets never enter trusted store raw.

## When to Use
- Apify/SERP/docs crawl produced rows you might remember
- Need atomic claims with source URLs for fact_store / brain

**Not for:** dumping HTML into notes; interactive browse-only tasks.

## Process
1. Run `apify-actor` with capped `maxResults` / `maxPages`.
2. Normalize rows → candidate claims (one fact each) + source URL.
3. For each candidate, run `verified-brain-commit-ritual` gates.
4. Commit passes; keep fails in inbox with gate reasons.
5. Return ledger: committed ids vs inbox holds.

## NEVER
- Commit without URL
- Bundle five facts into one write
- Store API tokens from pages

## Collision parents

`apify-actor`, `verified-brain-commit-ritual`