Systems Lab

Agent skill

notion-review

Set up a Notion verification surface so YALC outputs (qualified leads, qualified visitors, qualified engagers, lead-magnet replies, content drafts) land in a kanban that you approve in Notion before downstream skills act on them.

activeNeeds a keyInstructions only295 words

Filed under Prospecting and list building.

From Othmane-Khadri/YALC-the-GTM-operating-system · 61 skills · 290 · pushed 2026-08-20

What it does when it runs

Set up a Notion verification surface so YALC outputs (qualified leads, qualified visitors, qualified engagers, lead-magnet replies, content drafts) land in a kanban that you approve in Notion before downstream skills act on them. Each output type has ONE Batches kanban — every card is a batch (e.g. one lead list per campaign). Clicking a card opens its page with an INLINE Leads table rendered directly in the body (no extra click). Every item defaults to Status='Qualified'; users mark bad rows as 'Removed' (kill list), then drag the batch from To Review → Approved with one drag. Supports per-user-configured columns. Registers config in ~/.gtm-os/notion-reviews.yaml. Toggles the gate between hard (halt until approved) and autonomous (push + continue). Use when someone says 'set up a review kanban for [output type]', 'create a Notion review surface', 'I want to verify [output type] in Notion', 'let me approve qualified leads before YALC acts on them', 'reconfigure my review kanban', 'turn on Notion verification', 'trust YALC to act on engagers autonomously', or 'turn the verification gate back on for engagers'.

Read from the skill and the 1 file bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
  • NOTION_API_KEY
  • claude_ai_Notion
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about notion-review

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git /tmp/YALC-the-GTM-operating-system
git -C /tmp/YALC-the-GTM-operating-system sparse-checkout set ".claude/skills/notion-review"
mkdir -p ~/.claude/skills/notion-review
cp -R "/tmp/YALC-the-GTM-operating-system/.claude/skills/notion-review/." ~/.claude/skills/notion-review/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Before you install: this skill will not complete its job on a bare agent. It needs claude_ai_Notion, NOTION_API_KEY, which you have to obtain separately.

The skill

Source on GitHub ↗

Reproduced in full from Othmane-Khadri/YALC-the-GTM-operating-system/blob/5686d1f2f526346133f78eef3349fc5a655757b4/.claude/skills/notion-review/SKILL.md, which is licensed MIT (repository). 295 words, 1 heading.

Notion Review Surface

Execute the procedure in skills/notion-review.md.

The setup is a conversational flow asked ONCE per output type (not per batch / not per campaign).

Required inputs:

  1. Output type — one of qualified_lead, qualified_visitor, qualified_engager, lead_magnet_reply, content_draft.
  2. Parent Notion page — URL, page ID, or page title.

Then configuration questions about category name, batch card columns, inline-table columns, and gate mode. Defaults shown — user can accept them and skip.

Optional flags:

  • --rebuild — force a new Batches DB even if one is registered. Default: reconfigure existing.
  • --mode <hard|autonomous> — for review:gate.

Hard rules:

  • Two separate status state machines. Batch-level on the kanban: To Review → Approved / Rejected (the gate signal). Item-level inside each card's inline table: Qualified (default) / Removed (kill list).
  • Inline child databases. When a batch is pushed, an inline items DB (is_inline: true) is created inside that batch's page — items render directly in the card body, no navigation.
  • Per-batch items DBs. There is NO global items DB. Each batch owns its own items DB. Clean separation between campaigns; YALC reads back through getApprovedBatches.
  • Load-bearing contract:
    • Batches DB: Title, Status, Batch ID, Items DB ID (the last is plumbing — stamped at push time so the read path can locate the items DB).
    • Per-batch items DB: Title, Item ID, Status. These are added automatically. Everything else is user-configurable.
  • Hybrid Notion access: DB + page creation, queries, updates go through src/lib/services/notion.ts. Kanban + Gallery view creation uses the Notion MCP (mcp__claude_ai_Notion__notion-create-view) — only place in this skill where MCP is used.
  • Runtime config lives at ~/.gtm-os/notion-reviews.yaml. Never edit by hand — use review:setup, review:reconfigure, review:gate, review:doctor.

This skill is tenant-agnostic. Config is global (not per-tenant) in v3.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what notion-review does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.