What problem does it solve? Job seekers tracking applications in local files lack a glanceable, anywhere-accessible view of their pipeline. This Skill pushes a read-only mirror of ranked jobs and tracked applications into a Notion database while keeping the repo files as the system of record. ## Core Features & Use Cases - Idempotent upsert on Key: Re-running the sync never creates duplicate rows; matching uses the stored job key, and page bodies are write-once so user notes are never clobbered. - Graceful degradation: When the Notion MCP server is not connected or not authenticated, the command exits cleanly with one message and zero side effects. - Status and deadline precedence: Tracker data wins over scraper data, with canonical status normalization (e.g. no response → no_response) before writing to Notion select fields. - Use Case: After running /scrape, /rank, and /apply, invoke /notion-sync to create a "Job Search Pipeline" database with one row per job showing score, verdict, status, deadline, and links, viewable from phone or web. ## Quick Start Run /notion-sync to publish all jobs scoring 60 or above plus every tracked application to my Notion workspace.