Borrowing it
Nothing to install: this file belongs to Othmane-Khadri/YALC-the-GTM-operating-system. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/notion-review/SKILL.mdgit clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-systemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/notion-review)<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/notion-review"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/notion-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/notion-review"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/notion-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00261 | $0.00785 |
| Opus 5.5 | $0.00104 | $0.00314 |
| Sonnet 5.5 | $0.00052 | $0.00157 |
| Haiku 4.5 | $0.00026 | $0.00078 |
Grade A, and why
notion-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
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:
- Output type — one of
qualified_lead,qualified_visitor,qualified_engager,lead_magnet_reply,content_draft. - 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>— forreview: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.
- Batches DB:
- 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 — usereview:setup,review:reconfigure,review:gate,review:doctor.
This skill is tenant-agnostic. Config is global (not per-tenant) in v3.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 34 lines · 261 tokens per session scan A d1ddf24e5e35
notion-review is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (323 stars, last pushed 2mo ago), licensed MIT. It adds 261 tokens to every session and 785 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
kn-handoff
Use when a feature crosses repository boundaries and one side must hand work to the other - generates a self-contained frontend-to-backend brief or backend-to-frontend API contract.
deepline-org-chart
Build an interactive account org chart, leadership map, buying committee, or manager/report neighborhood around a person. Use for decision makers, reporting-line candidates, stakeholder mapping, and warm intro paths. Skip standalone email lookup and unrelated cross-company prospecting.
luma-event-campaign
DRAFT. Use when running a Luma-centered GTM event campaign: pull/export guests, enrich and score, draft invites and social, stage email+LI sequences paused for approval, and wire registration sync. Not installed by deepline skills.
event-ops-score-and-door
DRAFT. Score Luma/RSVP lists, approve against capacity, produce host-hit shortlists and day-of door packs. Systems framing — not a marketing CSV dump. Not installed by deepline skills.
toflow-manage-crm
Create, search, and update CRM records (people, companies, deals), manage custom attributes, categories, and deal pipelines. Use this whenever the user wants to look up, add, or edit CRM data, or manage a deal's pipeline stage.
toflow-manage-activities
Log calls, create follow-up tasks, and attach notes to CRM records (people, companies, deals). Use this whenever the user wants to record a call outcome, set a reminder/to-do, or capture context about a contact or account.