sync-debug

sync-debug is a skill for Claude Code from makenotion/notion-cookbook. It costs 28 tokens per session (925 once invoked), scanned A, original, MIT.

A guide for diagnosing a broken or incorrect data sync, which is a process that copies or updates information between systems. It checks run status and logs, then compares the reported error with the sync's source code.

In plain words
What is it for?
Use it to inspect sync status, find failed runs, read logs, review the relevant TypeScript code, and explain why data was not copied or was copied incorrectly.
Why use it?
It turns a vague report such as “the sync failed” into a traceable investigation based on actual runs, error messages, and the code that produced them. This helps identify likely causes before suggesting a fix.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to inspect sync status, find failed runs, read logs, review the relevant TypeScript code, and explain why data was not copied or was copied incorrectly.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/makenotion/notion-cookbook/sync-debug
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add makenotion/notion-cookbook --skill sync-debug
Clone the repo
git clone --depth 1 https://github.com/makenotion/notion-cookbook

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.

agentmods badge for sync-debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/makenotion/notion-cookbook/sync-debug/github.svg)](https://agentmods.dev/skills/makenotion/notion-cookbook/sync-debug)
Your own site
<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/sync-debug"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/sync-debug/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.

agentmods 80×15 button for sync-debug

Your own site · 80×15
<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/sync-debug"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/sync-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Memory Poisoning · line 78
    Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.
    Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00925
Opus 5.5 $0.00011 $0.00370
Sonnet 5.5 $0.00006 $0.00185
Haiku 4.5 $0.00003 $0.00093

Measured 1mo ago against content hash bf6c01205376, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-debug scanned grade A with 1 finding 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.

Makes network callslowCapability

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

- API returning no data: test the API call directly (curl or local exec)
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

workers/agents/skills/sync-debug/SKILL.md · 113 lines

How it starts

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

Instructions

Help the user figure out why their sync is failing or producing wrong results. Work through the steps below systematically.

Step 1: Get Current State

Run these commands to understand the situation:

ntn workers sync status

Note which syncs are listed, their status, last run time, and next scheduled run. Look for syncs that are stuck, failing, or haven't run recently.

Step 2: Fetch Recent Runs

ntn workers runs list

Look for runs with non-zero exit codes (shown in red in table output). Note the run IDs for failed runs.

Step 3: Get Logs

For the most recent run (any capability):

ntn workers runs list --plain | head -n1 | cut -f1 | xargs -I{} ntn workers runs logs {}

For the most recent run of a specific sync:

ntn workers runs list --plain | grep <syncKey> | head -n1 | cut -f1 | xargs -I{} ntn workers runs logs {}

Read the full log output. Look for error messages, stack traces, and any console.log output from the sync code.

Step 4: Read the Sync Code

Read src/index.ts (and any imported modules) to understand the sync's logic. Cross-reference the error from the logs with the code.

Step 5: Diagnose

Common failure patterns and their fixes:

API Authentication Errors (401/403)

  • Check if OAuth is configured: ntn workers oauth token <oauthKey>
  • Check environment variables: ntn workers env list
  • If env vars are missing remotely: ntn workers env push
  • If OAuth token expired: ntn workers oauth start <key> to re-authenticate

Rate Limiting (429)

  • Reduce batch size in the sync code
  • Add delays between API calls if needed
  • Check if the API has documented rate limits

Timeout / Long Execution

  • The execute function is taking too long per call
  • Reduce batch size (fewer records per page)
  • Simplify per-record processing (defer heavy transforms)

Cursor / State Errors

  • TypeError on state access: probably a first-run issue (state is undefined)
  • State shape changed after a code update: the persisted state from the previous run has the old shape
  • Fix: ntn workers sync state reset <key> to clear state and re-backfill from scratch

Read the full file on GitHub · 113 lines

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.

  1. 1mo ago First seen · 113 lines · 28 tokens per session scan A bf6c01205376

Subscribe to this mod's changes

sync-debug is a skill published in the GitHub repository makenotion/notion-cookbook (220 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 925 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens

cwv-optimizer

Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…

adobe/skills · 112 tokens

incident-response-incident-response

Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.

rmyndharis/antigravity-skills · 36 tokens