proof

Manage HITL Markdown review workflows through Proof's web API.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill proof-yxc023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: proof
Source: https://github.com/yxc023/agent-config-studio/tree/main/.opencode/skills/proof
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill proof-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Proof enables teams to run human-in-the-loop iterations on Markdown documents by coordinating creation, editing, commenting, sharing, and review cycles via Proof's web API and local bridge. It centralizes feedback, synchronizes work between local files and Proof docs, and keeps an auditable trail of changes for compliant collaboration.

Core Features & Use Cases

  • Create, edit, comment on, share, and run HITL iteration loops over Markdown documents via Proof's web API.
  • Use HITL review workflows to manage feedback on local or shared docs, with presence, state reads, mutations, and end-sync flows.
  • Support both web API and macOS Proof app bridges for end-to-end collaboration, including actionable threads and audit trails.

Quick Start

Upload a local Markdown file to Proof to start a HITL review and iterate with Proof, then sync changes back to your local file.

Frequently Asked Questions about proof

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run human-in-the-loop reviews on Markdown documents?

Human-in-the-loop reviews on Markdown documents are managed by creating Proof docs from local files, applying edits, comments, and presence updates, then syncing changes back to disk.

Can I sync local Markdown files with an online collaboration platform?

You can sync local Markdown files by uploading them to Proof, iterating through the review cycle, and applying end-sync flows to write the updated content back to your local disk.

How does presence syncing work for collaborative Markdown editing?

Presence syncing coordinates live state reads and updates across web and macOS Proof app bridges, ensuring collaborators see real-time changes and actionable threads during document iterations.

What is the best way to manage feedback and comments on shared Markdown docs?

Managing feedback on shared Markdown docs involves creating a Proof document, using token-based mutations to apply suggestions or edits, and maintaining an auditable trail of all review changes.

Do I need the Proof web API to automate HITL document workflows?

The Proof web API is required for automating HITL workflows, as it enforces consistent identity, handles mutations through /edit/v2, and bridges web and local Markdown file synchronization.

Are there limitations when syncing Proof document changes back to local disk?

Syncing changes back to local disk requires end-to-end safety rails and consistent identity enforcement to prevent data loss, meaning local file state must align with Proof's auditable review trail.