Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From glyphdown
Syncs, pushes, and pulls markdown docs with Glyphdown's CRDT-based collaboration platform. Use for editing shared docs, leaving suggestions, or managing a cloned workspace.
npx claudepluginhub sawyerhood/glyphdown --plugin glyphdownHow this skill is triggered — by the user, by Claude, or both
Slash command
/glyphdown:glyphdownThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
CLI for collaborating on Glyphdown markdown docs. Humans edit live in the web UI; you edit plain `.md` files and the server CRDT-merges, so concurrent human work survives — as long as you follow the rules below.
Create, edit with comments/suggestions/rewrites, and share collaborative markdown documents via Proof web API or macOS local bridge.
Creates and edits Obsidian Flavored Markdown including wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Activates when working with .md files or when the user mentions wikilinks, callouts, frontmatter, tags, or embeds.
Provides best practices for Markdown technical documentation and READMEs, including structure, organization, linking, writing style, code examples, and admonitions.
Share bugs, ideas, or general feedback.
CLI for collaborating on Glyphdown markdown docs. Humans edit live in the web UI; you edit plain .md files and the server CRDT-merges, so concurrent human work survives — as long as you follow the rules below.
Full reference: docs/agent-guide.md (works from the repo or a CLI-installed copy).
export GLYPHDOWN_API_KEY=gd_sk_... (minted in Settings → Agents) or glyphdown login --key gd_sk_.... Server defaults to https://glyphdown.com; override with GLYPHDOWN_SERVER or --server.
glyphdown clone work && cd work # once; mirrors every folder/doc you can access (default dir: ./glyphdown)
# ... edit .md files, add images, mkdir new folders — normal tools ...
glyphdown sync # two-way reconcile, run before AND after editing
sync operates on the cwd — run it inside the workspace (or pass the dir: glyphdown sync work).
Vaults: every doc lives in one vault (an Obsidian-style root namespace; a full clone shows vaults as top-level dirs). glyphdown vaults --json lists yours; glyphdown clone --vault <name|id> makes a workspace confined to one vault (clone and sync both ignore everything outside it); glyphdown new <name> --vault <vault> creates at its top level. Vault names resolve case-insensitively; with neither --vault nor --folder, new lands in the key owner's default vault.
Sync prints one action per doc/folder: pushed / pulled / merged / created (new local file → new doc) / new (new server doc) / folder created / new folder (server) / renamed locally: old → new / local missing — re-pulled / remote gone / up to date.
Exit codes (always check): 0 clean · 2 failed hunks — printed like git .rej; re-apply those edits by hand and sync again · 3 degenerate skip — your change rewrites most of a doc that drifted; re-pull and redo, or --force ONLY if the rewrite is intentional — never blind --force on a shared doc · 1 anything else (read stderr).
Single docs without a clone: glyphdown pull <id|url> → edit → glyphdown push <file>.
For reviewable changes: glyphdown push <file> --suggest -m "why" (or sync with a suggester-role key — pushes land as suggestions automatically). Humans accept/reject in the web UI; your local base does not advance — re-pull after review. List with glyphdown suggestions <doc> --json.
glyphdown mv <file> <new-name> — NEVER bare mv: sync does not detect renames, so the old name re-pulls and the new file becomes a duplicate doc. mv renames the local file and the server filename together.
glyphdown comments <doc> --json # open threads
glyphdown comment <doc> --body "..." [--line N] # new (line-anchored) comment
glyphdown comment <doc> --reply <id> --body "..." # reply
glyphdown comment <doc> --resolve <id> [--body "..."] # resolve (reply first if --body)
Owner-only. <doc> is an id or URL; folders/vaults use --folder <id|name> instead (the link covers the whole subtree, URL /f/<folderId>?share=<token>).
glyphdown share <doc> [--role viewer|commenter|suggester|editor] [--json] # create (default viewer); prints https://…/d/<docId>?share=<token>
glyphdown share list <doc> [--json] # active links: token, role, url
glyphdown share revoke <doc> <token> # revoke (a ?share= URL alone also works)
glyphdown share [list|revoke] --folder <ref> … # folder/vault variants
The token IS the capability — treat share URLs as secrets.
--json on read commands (list, vaults, cat, comments, suggestions, new, sync, share) for parsing.[a-z0-9-] + .md); the file name IS the doc name everywhere. The # heading is just content.glyphdown snapshot <doc> -m "msg" before big changes.remote gone) and stay local. Delete via the web UI..glyphdown/ (the push bookkeeping). Sync sequentially — one sync at a time per workspace; pushes are rate-limited 60/min.