content-governance

Reconcile newsletters between Google Docs and Notion Content DB with cross-linking.

21|3|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill content-governance-peter-tu-zynkr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: content-governance
Source: https://github.com/peter-tu-zynkr/zynkr-skill-builder/tree/main/skills/1-brand-marketing/content-governance
Command: npx skills add https://github.com/peter-tu-zynkr/zynkr-skill-builder --skill content-governance-peter-tu-zynkr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Newsletter content often lives in two places — a Google Doc draft and a Notion Content DB page — created in either order, leading to duplicates, misfiled Docs, missing issue numbers, and inconsistent metadata. This Skill reconciles the two into a single consistent, cross-linked record regardless of which was created first. ## Core Features & Use Cases - Bidirectional reconciliation: Detects the entry point (Doc-first, Notion-first, or both) and creates whichever anchor is missing, then files the Doc into the newsletter Drive folder with the correct (N) Title naming. - Deduped Notion records: Searches the Content DB by issue number and title before creating pages, guaranteeing exactly one row per newsletter with full metadata (Subject tags, Status, Last Synced, Author) and the article body synced into the page. - Rule-based subject classification: Ships an 82-subject taxonomy CSV plus 24 classification rules in references/ to assign 3–5 confirmed Subject tags per piece. - Use Case: You paste a Google Doc URL for your latest newsletter draft. The Skill assigns the next issue number, renames and files the Doc into the newsletter folder, classifies its subjects, and creates a fully populated Notion Content DB page cross-linked to the Doc. ## Quick Start Ask the assistant to sync this Google Doc to Notion and file the newsletter in the right place, then paste your Doc or Notion page URL.

Frequently Asked Questions about content-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a Google Doc to a Notion database page?▼

Provide the Google Doc URL and the Skill fetches its content, files it into the newsletter Drive folder with the correct issue-numbered name, then creates or updates a deduped Notion Content DB page with full metadata and the article body synced into the page content.

How do I turn a Notion idea stub into a Google Doc newsletter?▼

Share the Notion page URL and the Skill extracts a clean title, assigns the next issue number from the Drive folder, creates a Google Doc named (N) Title in the newsletter folder with the article body, and writes the Doc URL back to the Notion page.

Does this prevent duplicate Notion pages for the same newsletter?▼

Yes. Before creating any page, the Skill searches the Content DB by issue number and by title. If a match exists it updates that page instead, guaranteeing exactly one Notion row per newsletter even when stubs were created earlier.

What happens if the references directory is missing after install?▼

The Skill detects a single-file install and reads the subject taxonomy from the source Google Sheet instead of guessing tags from memory. Installing as a directory via npx skills add keeps the taxonomy CSV and rules available offline.

How are newsletter subject tags chosen and validated?▼

Tags are selected from an 82-subject taxonomy using 24 classification rules that prioritize the piece's core argument over keyword matches. The Skill proposes 3–5 tags with reasons and waits for user approval before writing them to Notion.