Use this skill when working with documents in ~/docs/, pushing markdown files to Google Docs, pulling Google Docs comments, or pairing markdown files with Google Docs. Triggered by: "push this doc to Google", "sync with Google Docs", "pair this file with a Google Doc", "show comments from Google Docs", "list my docs", or any mention of savi-docs.
From savinpx claudepluginhub michaelknopf/claude-code-profile --plugin saviThis skill uses the workspace's default tool permissions.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
A CLI tool (savi-docs) manages local markdown files in ~/docs/ and syncs them
with Google Docs. Local markdown is always the source of truth — Google Docs is
a view, not an editor.
~/docs/
repos/<repo-name>/ # repo-specific docs
reports/ # epic-loop report files (not committed to git)
*.md # other repo docs
general/ # docs not tied to a specific repo
*.md
Documents are stored here instead of inside repos so they:
Any markdown file can be paired with a Google Doc via front matter:
---
gdoc_id: "1abc123..."
title: "My Document"
---
# Actual markdown content starts here
gdoc_id: the Google Doc ID (required for push/pull-comments)title: document title shown in Google Docs (optional, defaults to filename)Front matter is stripped before pushing — Google Docs never sees it.
The gdoc_url is always derived from gdoc_id as
https://docs.google.com/document/d/{gdoc_id}/edit.
Run from anywhere; paths to markdown files must be provided.
# Push markdown to its paired Google Doc (create if not yet paired)
savi-docs push ~/docs/general/my-doc.md
# Explicitly create a new Google Doc (errors if already paired)
savi-docs create ~/docs/general/my-doc.md --title "My Doc" --parent FOLDER_ID
# Fetch and display comments from the paired Google Doc (read-only)
savi-docs pull-comments ~/docs/general/my-doc.md
# List all docs in ~/docs/ with their pairing status
savi-docs list
# Filter to a specific repo's docs
savi-docs list --repo my-repo-name
# Pair an existing file with an existing Google Doc
savi-docs init ~/docs/general/my-doc.md --doc "https://docs.google.com/..."
push for create-or-update — it creates a new doc if unpaired,
or updates the existing doc if already paired.pull-comments to see the changes as comments, then apply them locally.~/docs/repos/<repo-name>/ and general docs
under ~/docs/general/.~/docs/repos/<repo-name>/reports/.