gdrive_synthesize

Synthesizes durable KTX wiki pages from staged Google Drive document pulls.

1.6k|101|Updated May 10, 2026
One-click install
npx skills add https://github.com/Kaelio/ktx --skill gdrive-synthesize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdrive_synthesize
Source: https://github.com/Kaelio/ktx/tree/main/packages/cli/src/skills/gdrive_synthesize
Command: npx skills add https://github.com/Kaelio/ktx --skill gdrive-synthesize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Google Drive documents contain valuable organizational knowledge—policies, definitions, and operating procedures—but that knowledge stays locked in raw docs unless someone reads, deduplicates, and distills it into a durable, searchable knowledge base.

Core Features & Use Cases

  • Doc-to-Wiki Synthesis: Reads staged Google Doc raw files (page.md plus metadata.json) and writes a small set of high-quality KTX wiki pages capturing durable business knowledge.
  • Deduplication and Conflict Handling: Searches existing wiki pages before writing, updates overlapping pages instead of creating duplicates, and records conflict notes when sources disagree.
  • Identifier Verification: Verifies warehouse, dbt, Looker, Metabase, or MetricFlow references via discovery, entity details, and SQL probes before citing them, marking unverifiable identifiers explicitly.
  • Eviction Management: Processes deleted raw paths through eviction decisions so stale knowledge is retired deliberately.
  • Use Case: A memory agent receives a WorkUnit containing a Google Doc describing the company's revenue recognition policy; the skill reads the doc, finds the existing revenue wiki page, updates it with the new policy, and cites the doc title and last-modified date.

Quick Start

Load this skill when a WorkUnit contains staged Google Drive raw files under docs/** and synthesize the durable knowledge into KTX wiki pages.

Frequently Asked Questions about gdrive_synthesize

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

FAQPage Schema
How do I turn Google Drive documents into a searchable wiki knowledge base?

Stage the Google Docs as raw files under docs/** in a WorkUnit, then this skill reads each page.md and metadata.json, searches for overlapping wiki pages, and writes a small set of durable KTX wiki entries citing the source doc title and last-modified date.

What content from Google Docs should be captured in a company wiki?

Capture durable knowledge: policies, workflows, product definitions, business terminology, source-of-truth statements, and cross-system aliases. Skip transient content like brainstorming notes, task lists, meeting logistics, and duplicate docs with no new facts.

Can Google Drive docs create semantic-layer sources in KTX?

No. Google Drive docs are knowledge-only in v1, so durable output stays in wiki pages and no semantic-layer sources may be created under the gdrive connection. Verified warehouse references may be attached as sl_refs in wiki output.

How are warehouse table references in documents verified before writing?

The skill runs discover_data and entity_details to confirm identifiers resolve, checks sampleValues for literal values, and can run a sql_execution probe. Unresolvable identifiers are wrapped as unverified with the citing raw path or recorded via emit_unmapped_fallback.

What happens when a source Google Doc is deleted?

Deleted raw paths appear in the WorkUnit Eviction Set. The skill calls eviction_list, decides whether to retain or retire the derived knowledge, and emits an eviction decision for every deleted path, even when no wiki write is needed.