New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Proof Markdown Collaboration

by EveryInc in EveryInc/compound-engineering-plugin

Publishes, reads, comments on, or edits shared markdown documents through the hosted Proof editor's web API.

MITAuto-check: notesDocuments & Office

Install Proof Markdown Collaboration

skills CLI
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-proof -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EveryInc/compound-engineering-plugin ce-proof --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-proof .claude/skills/ce-proof && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ce-proof
GitHub stars
25k
Token cost
~1.9k tokens
SKILL.md length
1,115 words
Files
3 (incl. references)
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Publishes, reads, comments on, or edits shared markdown documents through the hosted Proof editor's web API.

  • Sharing a spec, plan, or draft as a live Proof link
  • SKILL.md covers Identity, Credentials and boundaries, Publish mode and Editing
  • Calls jq; reaches proofeditor.ai
  • Reading or commenting on a document someone shared through Proof

What it does

Proof, a collaborative markdown editor for humans and agents, is reached over its hosted HTTP API or through typed MCP tools when those are already available. A create is confirmed by the tokenized link it returns, a mutation by an explicit success flag or by re-reading the document, a pull by the local file it wrote, and a read by the content it returned.

Every write carries a fixed machine identity and display name so Proof can attribute it consistently, though a caller can pass a different identity when a sub-agent should own the document instead. Deleting needs the right authority: an unclaimed document needs its owner secret, a claimed one needs the owner's own session, and a plain editor token cannot delete at all.

When your agent uses it

  • Sharing a spec, plan, or draft as a live Proof link
  • Reading or commenting on a document someone shared through Proof
  • Pulling a shared Proof document down to a local file

Example prompts

  • “Publish this design doc to Proof and share the link.”
  • “Read the comments on our pricing doc and summarize the open ones.”
  • “Pull the latest version of the roadmap doc to a local file.”

Requirements

  • Network access to the Proof hosted API (proofeditor.ai)
  • Pre-approved tools (allowed-tools): Bash, Read, Write, WebFetch

What it can do on your machine

Read from SKILL.md and the folder at commit cef001f. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • WebFetch

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • proofeditor.ai

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Proof Markdown Collaboration loads about 1.9k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 55 tokens; SKILL.md has 1,115 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~55
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, WebFetch

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EveryInc/compound-engineering-plugin at commit cef001f, republished under its MIT licence (© EveryInc). 1,115 words, ~1,927 tokens.

Download SKILL.mdSave it as .claude/skills/ce-proof/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
ce-proof
description
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
allowed-tools
Bash, Read, Write, WebFetch

Proof - Collaborative Markdown Editor

Proof is a collaborative document editor for humans and agents. It is reached through the hosted web API at https://www.proofeditor.ai, over HTTP from Bash.

Outcome: the user holds a working tokenized Proof link, or the doc carries the read, comment, suggestion, or edit they asked for.

Done: the operation is confirmed at its own level, and the user has the result plus a short summary. A create is confirmed by the tokenUrl it returned. A mutation is confirmed by ok: true; on a 202 or a partial: true response, confirm by re-reading v3/document. A pull is confirmed by the local file it wrote, and a read by the content it returned.

Read references/api.md before the first Proof read or mutation, HTTP or MCP. It defines the endpoints: share/markdown, the v3 document and edit endpoints, presence, title, and DELETE /api/documents/<slug>. It also carries the operation tables, the error and retry classes, and the curl permission hint for Claude Code.

Read references/workflows.md before reviewing a shared doc, before creating and sharing one, and before pulling a doc to a local file. Those flows have exact recipes there.

If typed proof_* MCP tools are already available in the harness (proof_share_markdown, proof_v3_document, proof_v3_edit, proof_presence, proof_document_title, proof_document_delete, proof_report_bug), prefer them. Otherwise use the HTTP recipes. In MCP mode the server injects by, X-Agent-Id, and presence identity. Pass the ?token= value from the Proof URL as shareToken for edits and presence on docs the signed-in user does not own.

Delete authority is unchanged in MCP mode. An unclaimed doc still needs its ownerSecret, and a claimed doc needs its owner's session. An editor accessToken passed as shareToken cannot delete.

Identity

Every write is attributed with both fields, and they do not vary. The machine ID is ai:compound-engineering, sent as by on every op and as the X-Agent-Id header. The display name is Compound Engineering, sent as name on POST /presence, set once per doc session so Proof binds it to that agent ID. A caller may pass a different identity pair when a distinct sub-agent should own the doc. Never improvise a variant such as ai:compound.

Credentials and boundaries

  • accessToken is the everyday bearer for read, edit, presence, and events. ownerSecret carries owner authority only — delete and other owner-level ops — and is never the everyday bearer. Capture both at create time, and persist ownerSecret for the session separately from accessToken, in shell vars or equivalent; it is required for owner delete while the doc is unclaimed. Neither belongs in repo-tracked files, commits, or durable logs, and ownerSecret never appears in user-facing copy.
  • Hand humans the tokenized link (tokenUrl), never a bare /d/<slug> — the token in that link is also what lets a signed-in user claim an ownerless doc.
  • Public creates are ownerless until a signed-in Every user claims the doc in the browser. Claiming permanently revokes ownerSecret while accessToken keeps working, so delete then needs the owner's Every session — ask the owner, or use their session token. Two responses mean the secret was revoked: a 403 with code: "DOCUMENT_DELETE_FORBIDDEN" and reason: "CREDENTIAL_NOT_OWNER", or a 401 when presenting the creation ownerSecret. Stop using the secret rather than retrying. reason: "DOCUMENT_HAS_NO_OWNER" is the opposite: the doc is still unclaimed, so only the original ownerSecret can delete it and an Every session cannot.
  • Never put secrets, credentials, API keys, private tokens, or sensitive personal data into a Proof doc unless the user explicitly approves, and never silently replace a repo-tracked project doc with a Proof link.
  • Emptying the markdown does not scrub comment marks. Quotes and commentary stay readable to anyone with the share credential, so a content wipe is not a privacy cleanup. Deleting the document is — with ownerSecret while the doc is unclaimed, or as the owner after a claim.
  • Do not auto-delete after a publish handoff. Review docs must linger. Delete when the user asks, or when finishing an explicitly ephemeral scratch doc.
Show full SKILL.md (464 more words)Show less

Publish mode

The primary use is one-way publishing. Read an existing local markdown file in full, post its contents as the new doc's body, and hand the user the shareable URL. The local file stays canonical — publishing syncs nothing back to disk.

Two entry points share those mechanics. One is a bare user request naming a local markdown file ("share this to proof", "get me a proof link for this doc"); ask which file only if it is ambiguous, and expect no upstream caller. The other is a handoff from ce-brainstorm, ce-ideate, or ce-plan passing the file path and title.

Only publish markdown. If the source is an HTML unified plan, return the local browser/open path instead of uploading it. When publishing a unified plan, label the title by readiness when it is known, e.g. Plan: <title> (requirements-only) or Plan: <title> (implementation-ready).

Publish the source file's bytes, never hand-written or placeholder content. references/workflows.md gives the jq --rawfile recipe that escapes newlines, quotes, and backticks correctly. After a publish handoff, show the user the URL and return control.

Editing

GET /api/agent/<slug>/v3/document and POST /api/agent/<slug>/v3/edit are the only endpoints an agent reads from and writes to. Comments, replies, resolutions, suggestions, and content changes are all operations in the v3 edit body, so a path you did not read in references/api.md is one you invented.

Read v3/document as the source of truth before editing. Then choose the narrowest operation that expresses the change: a scoped replace, insert, or delete for prose; suggest when the change should be visible as tracked changes; set_document only when the user asks for a whole-doc replacement, or the change cannot be expressed narrowly. Targets are visible text in markdown, never raw markdown syntax or block refs.

comments[] and suggestions[] from that read are the review state. Reply, resolve, unresolve, accept, or reject by id. v3 has no delete-comment op. A comment marked orphaned: true is still readable and replyable, but its old quote is no longer a live anchor.

Errors that mean stop and check, before retrying anything:

  • TARGET_AMBIGUOUS — the anchor matched more than once and nothing changed. Disambiguate with occurrence / before / after from error.candidates; never assume silent first-match, and never blind-retry a comment.
  • retryable: false — fix the request. retryable: true with error.current — re-resolve targets against current, then retry once.
  • 202 / PENDING, or ok: false with partial: true — the write may have committed. Re-read v3/document before chaining or reporting success, and retry only the failed op (a repeated Idempotency-Key replays safely).
  • Still failing after a fresh read and one safe retry — report the bug per references/api.md rather than looping.

Pulling a doc down to a local file overwrites that file. When the pull is a side effect of some other action rather than something the user asked for, confirm the path first.

© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/ce-proof of EveryInc/compound-engineering-plugin.

  • SKILL.md
  • references/api.md
  • references/workflows.md

Open the folder on GitHubat commit cef001f

Compare with similar skills

Proof Markdown Collaboration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Proof Markdown Collaboration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Proof Markdown Collaboration this skillEveryInc/compound-engineering-plugin25k—~1.9kAutomated safety check: NotesMIT
Clean Content FetchLeoYeAI/openclaw-master-skills2.2k—~574Automated safety check: PassMIT
Markvisgeekplux/markvis1.6k—~786Automated safety check: PassMIT
Cmux Markdown Viewer Panelbasicmachines-co/basic-memory4.1k2 repos~527Automated safety check: PassAGPL-3.0
Wechat Article To Markdownjackwener/wechat-article-to-markdown1k—~352Automated safety check: PassNone
Web Article Extractordongbeixiaohuo/writing-agent435—~740Automated safety check: PassMIT

Similar skills

  • Clean Content Fetch

    LeoYeAI/openclaw-master-skills

    获取干净、可读的网页正文内容，适合现代网页、博客、新闻、公告和微信公众号文章抓取；支持网页正文提取、内容清洗、去噪、Markdown 输出，适用于普通 fetch 效果不佳、页面噪音较多或动态渲染干扰的场景。Clean content fetch for modern web pages, article extraction, WeChat article capture, content…

    2.2k GitHub stars~574 tokensUpdated 2 mo ago
    Documents & OfficeAuto-check passed

  • Markvis

    geekplux/markvis

    A skill your agent uses when the user wants a chart of numbers in Markdown (bar, line, area, scatter, pie, hist, heatmap, funnel, waterfall, radar, gauge, sankey, treemap, dumbbell, bullet, boxplot…

    1.6k GitHub stars~786 tokensUpdated today
    Documents & OfficeAuto-check passed

  • Cmux Markdown Viewer Panel

    basicmachines-co/basic-memory

    Opens markdown files in a formatted cmux panel beside the terminal that re-renders on every change, handy for plans and task lists.

    4.1k GitHub starsUsed in 2 repos~527 tokens
    Documents & OfficeAuto-check passed

  • Wechat Article To Markdown

    jackwener/wechat-article-to-markdown

    Fetch WeChat Official Account (微信公众号) articles from mp.weixin.qq.com and convert to Markdown.

    1k GitHub stars~352 tokensUpdated 6 mo ago
    Documents & OfficeAuto-check passed

  • Web Article Extractor

    dongbeixiaohuo/writing-agent

    使用隔离的 Chrome DevTools MCP 从博客、新闻、公众号等网页提取正文，返回结构化内容，或保存 Markdown 和远程图片。用户要求提取文章、抓取网页正文、保存为 Markdown、下载文章图片或排查正文选择器时调用。

    435 GitHub stars~740 tokensUpdated 4 days ago
    Documents & OfficeAuto-check passed

  • HTML Summary

    testdouble/han

    Convert a stakeholder summary markdown file into a single self-contained HTML executive report — bottom line and decision asks up front, supporting detail later — styled with a Test Double-derived…

    279 GitHub stars~2.9k tokensUpdated 6 days ago
    Documents & OfficeAuto-check passed

More from EveryInc/compound-engineering-plugin

All 37 skills in this repo

  • Compound Learning Writer

    EveryInc/compound-engineering-plugin

    Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Compound Learnings Refresh

    EveryInc/compound-engineering-plugin

    Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Compound Engineering Prototype

    EveryInc/compound-engineering-plugin

    Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Compound Engineering Setup

    EveryInc/compound-engineering-plugin

    Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • PR Babysitter

    EveryInc/compound-engineering-plugin

    Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.

    25k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • CE Brainstorm

    EveryInc/compound-engineering-plugin

    Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.

    25k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Categories

Questions about Proof Markdown Collaboration

What does Proof Markdown Collaboration do?

Publishes, reads, comments on, or edits shared markdown documents through the hosted Proof editor's web API. Proof, a collaborative markdown editor for humans and agents, is reached over its hosted HTTP API or through typed MCP tools when those are already available. A create is confirmed by the tokenized link it returns, a mutation by an explicit success flag or by re-reading the document, a pull by the local file it wrote, and a read by the content it returned.

When should I use Proof Markdown Collaboration?

Proof Markdown Collaboration fits situations like: sharing a spec, plan, or draft as a live Proof link; reading or commenting on a document someone shared through Proof; pulling a shared Proof document down to a local file.

How do I install Proof Markdown Collaboration in Claude Code?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-proof -a claude-code`. Or copy the skill folder (skills/ce-proof in EveryInc/compound-engineering-plugin) into .claude/skills/ce-proof in your project. Claude Code loads it when a task matches its description.

How do I install Proof Markdown Collaboration in Codex?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-proof -a codex`. Or copy the skill folder (skills/ce-proof in EveryInc/compound-engineering-plugin) into .agents/skills/ce-proof in your project. Codex loads it when a task matches its description.

Can I use Proof Markdown Collaboration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill ce-proof -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ce-proof, .gemini/skills/ce-proof, .github/skills/ce-proof and .opencode/skills/ce-proof in your project.

What does Proof Markdown Collaboration need to run?

Going by SKILL.md and its folder, Proof Markdown Collaboration needs the command-line tools its instructions call (jq). Our summary lists: Network access to the Proof hosted API (proofeditor.ai). Its frontmatter pre-approves these tools: Bash, Read, Write, WebFetch.

Does Proof Markdown Collaboration access the network?

SKILL.md names 1 domain. In commands or code: proofeditor.ai; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Proof Markdown Collaboration safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Proof Markdown Collaboration use?

Proof Markdown Collaboration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Proof Markdown Collaboration use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.6k tokens, read only when the agent opens those files.

What are the alternatives to Proof Markdown Collaboration?

Skills that share tags, products or a category with Proof Markdown Collaboration: Clean Content Fetch (LeoYeAI/openclaw-master-skills, 2.2k stars), Markvis (geekplux/markvis, 1.6k stars), Cmux Markdown Viewer Panel (basicmachines-co/basic-memory, 4.1k stars) and Wechat Article To Markdown (jackwener/wechat-article-to-markdown, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Proof Markdown Collaboration?

EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,412 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 7, 2026.

Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.