notion-advanced-troubleshooting
Use when standard Notion troubleshooting fails or you are chasing intermittent API errors — deep debugging for response inspection, permission chain tracing, property type mismatches, pagination edge cases, and block nesting limits. Trigger with phrases like "notion deep debug", "notion permission trace", "notion property mismatch", "notion pagination bug", "notion nesting limit".
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill notion-advanced-troubleshooting --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Notion Advanced Troubleshooting ## Overview Deep debugging techniques for Notion API issues that resist standard fixes — API response inspection with request IDs, permission chain tracing, property type mismatch detection, pagination edge cases, and block nesting limit violations (max depth of 3 levels via API). Full runnable TypeScript and Python for every step lives in [references/implementati
What does the notion-advanced-troubleshooting skill do?
Use when standard Notion troubleshooting fails or you are chasing intermittent API errors — deep debugging for response inspection, permission chain tracing, property type mismatches, pagination edge cases, and block nesting limits. Trigger with phrases like "notion deep debug", "notion permission trace", "notion property mismatch", "notion pagination bug", "notion nesting limit".
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill notion-advanced-troubleshooting --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
