
Proof Collaborative Markdown Editor
Publish, read, comment on, and edit markdown docs in the Proof hosted editor via shareable links
- Repository
- EveryInc/compound-engineering-plugin
- Stars
- 25,850
- Licence
- MIT
- Files
- 3 files
What it does
When installed, the agent can publish a local markdown file to Proof, a hosted collaborative editor, and hand you a shareable link. It can also read a shared Proof doc, add comments or suggested edits, reply to or resolve review comments, and delete docs when you ask. Publishing is one-way: the local file stays the source of truth and nothing is synced back to disk.
Great for
- Developers and product teams who want to share specs, plans, or drafts with reviewers via a link
- People using planning workflows (such as the ce-plan or ce-brainstorm skills) that hand off docs for review
Skip it if
- Anyone publishing sensitive or confidential content: anyone with the share link can read it, and emptying a doc does not remove comment text, so deletion is the only real cleanup
- Users who need offline or private editing, since the skill depends on a third-party hosted service at proofeditor.ai
Try asking
- “Share this markdown spec to Proof and give me the link”
- “Read the Proof doc at this link and summarize the open comments”
- “Add a suggestion to the Proof doc replacing the intro paragraph with the revised text”
- “Resolve the review comments in this Proof doc that have already been addressed”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 3 original files, the MIT licence and an attribution note.
ce-proof.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip ce-proof.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip ce-proof.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Hand reviewers the tokenized tokenUrl link, not the bare document address, so they can comment and edit
- Don't put secrets, API keys, or personal data into a Proof doc; treat every published doc as readable by anyone with the link
- Ask the agent to delete the doc explicitly when a review is finished, since it will not auto-delete after publishing
What's inside
- references/api.md
- references/workflows.md
- SKILL.md
Redistributed unmodified from EveryInc/compound-engineering-plugin under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.