Docs on Vibe Coding

Google Drive

Mon, 01 Jan 0001 00:00:00 +0000

The Google Drive server lets an agent search your Drive and read the contents of documents and spreadsheets, using OAuth scoped to your account.

Why it matters

A lot of real work context — specs, meeting notes, planning docs — lives in Docs and Sheets, not in a codebase. This connector lets an agent reference that material directly instead of you manually copying content into a prompt.

Skill Seekers

Mon, 01 Jan 0001 00:00:00 +0000

Skill Seekers automatically converts any documentation website into a ready-to-use Claude skill, turning scattered docs into structured, invokable reference material.

Why a skill for this

Most third-party libraries have documentation but no packaged skill. Automating the conversion means any well-documented tool can get a working skill without hand-authoring one from scratch.

Outline Wiki Skill

Mon, 01 Jan 0001 00:00:00 +0000

The Outline Wiki skill searches, reads, creates, and manages documents in an Outline wiki instance, whether cloud-hosted or self-hosted.

Why a skill for this

Team knowledge often lives in a wiki rather than the codebase, so a coding-only agent misses it. Wiring in direct wiki access keeps documentation work and code work in the same conversation.

Notion Spec-to-Implementation Skill

Mon, 01 Jan 0001 00:00:00 +0000

This curated Codex skill turns a Notion spec document directly into an implementation plan and pull request.

Why a skill for this

Specs often live in Notion, separate from the codebase, which means implementation work starts with manually re-reading and re-typing the spec. A skill that reads Notion directly removes that translation step.