What is claap-weekly-recap?

An automated weekly recap for sales calls recorded in Claap, a service for recording and reviewing calls. It turns recent call information into action items and focus blocks in a Notion Kanban board, then sends a summary to Slack.

Use it to identify deal-related actions, preserve supporting call quotes and timestamps, plan next week's focus, and deliver the results in Notion and Slack.

It removes the manual work of reviewing a week of calls and transferring follow-up tasks into a shared planning system.

How Othmane-Khadri/YALC-the-GTM-operating-system configures Claude Cod

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/Othmane-Khadri/YALC-the-GTM-operating-system/main/.claude/skills/claap-weekly-recap/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap/github.svg)](https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap)

Your own site

<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap"><img src="https://agentmods.dev/badge/skills/othmane-khadri/yalc-the-gtm-operating-system/claap-weekly-recap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 141 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,738 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00141	$0.05738
Opus 5	$0.00071	$0.02869
Sonnet 5	$0.00028	$0.01148
Haiku 4.5	$0.00014	$0.00574

Measured 13d ago against content hash c08a62180c3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

claap-weekly-recap scanned grade C with 2 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 13d 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.

Harvests environment variableshighData exfiltration

Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.

Run `printenv CLAAP_API_KEY` via `Bash` and read the exit code only (do

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST -H 'Content-Type: application/json' \

.claude/skills/claap-weekly-recap/SKILL.md · 569 lines

How it starts

The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claap Weekly Recap

Reads every Claap recording from the last N days, extracts per-deal action items with verbatim quotes and Claap timestamp links, synthesizes weekly focus blocks, writes them to a Notion Kanban DB, and delivers a Slack summary. Designed to run unattended on a Sunday morning schedule after the user runs it once interactively to seed config.

You produce action items and focus blocks. You do NOT modify the underlying call recordings, edit existing Notion cards beyond the idempotency guard, or write to any database other than the GTM Action Items DB recorded in config.

When This Skill Applies

"give me the week in calls"
"what did prospects ask for this week"
"draft action items from my Claap calls this week"
"Sunday recap from sales calls"
"set up a weekly recap from Claap into Notion + Slack"

NOT this skill:

"summarize this one call" — use Claap's own per-call summary in the app
"ask my call history a question right now" — use Claap MCP directly

Config File

The skill is driven by .claude/skills/claap-weekly-recap/.claap-config.json, created on first run by SETUP MODE. Secrets never live in this file. Only structural choices and non-sensitive IDs:

{
  "version": 1,
  "claap_tool_prefix": "mcp__claap__",
  "gtm_action_items_data_source_id": "collection://<YOUR_DATA_SOURCE_UUID>",
  "notion_db_url": "https://www.notion.so/<workspace>/<db-id>",
  "slack_delivery": {
    "mode": "mcp_user",
    "target": "<U_YOUR_SLACK_ID>"
  },
  "lookback_days": 7,
  "min_call_minutes": 3,
  "extraction_signals": [
    "objection",
    "competitor_mention",
    "feature_request",
    "action_item",
    "next_step_promised"
  ],
  "kanban_statuses": ["Backlog", "Focus This Week", "Done", "Archived"],
  "extra_properties": [],
  "prior_recap_history_path": "~/.gtm-os/state/claap-recap-history.md",
  "model": "claude-sonnet-4-6",
  "max_turns": 100
}

Allowed claap_tool_prefix values:

mcp__claap__ (self-hosted / project-scoped Claap MCP)
mcp__claude_ai_Claap__ (claude.ai connector)

Read the full file on GitHub · 569 lines

Files

What ships with it

10 files 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.

Changes

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.

13d ago First seen · 569 lines · 141 tokens per session scan C c08a62180c3e

Subscribe to this mod's changes

claap-weekly-recap is a skill published in the GitHub repository Othmane-Khadri/YALC-the-GTM-operating-system (301 stars, last pushed 23d ago), licensed MIT. It adds 141 tokens to every session and 5,738 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 2 findings (harvests environment variables, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Productivity Project management ai-native clay-alternative cli gtm lead-generation open-source

YALC-the-GTM-operating-system: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade C, and why

Harvests environment variableshighData exfiltration

Makes network callslowCapability

How it starts

Claap Weekly Recap

When This Skill Applies

Config File

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

task-management

gws-workflow-email-to-task

gws-workflow-standup-report

slack-tools

kn-handoff

alive:bundle