oulang-bq-to-notion

Installation
SKILL.md

Oulang BQ → Notion Skill (single canonical workflow)

Why this skill exists

Previous attempts split work across four skills (bigquery-oulang-creative, bigquery-oulang-analysis, oulang-knowledge-capture, oulang-knowledge-sync). Agents kept running BigQuery, surfacing live findings, then losing them because capture was treated as a separate, optional, batch-only step. The user has repeatedly had to re-request the same analyses because nothing was persisted to the canonical Notion knowledge system.

This skill is the single source of truth. Running BQ here and NOT writing to Notion is a failure. Capture is not a separate skill — it is part of the query loop.

Hard contract (non-negotiable)

  1. All analysis goes through BigQuery. No direct MySQL connections. No PostHog REST API calls. MySQL is accessed via EXTERNAL_QUERY, PostHog via exported tables.
  2. Every query you run must be paired with a durable finding written to Notion before the session ends. Zero findings = incomplete task.
  3. No placeholder SQL, no hypothetical tables. Run the schema check first when unsure.
  4. Inline capture, not batch. Write to Notion as insights emerge, not at the end and not in a separate skill run.
  5. Use the service account full-owner@megacursos.iam.gserviceaccount.com — it already has BQ + federated + PostHog access.

Auth (copy-paste verbatim)

Installs
1
First Seen
Apr 14, 2026