Agent skill

Doca Collaboration

Install Doca Collaboration

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a claude-code

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

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration --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/smartdoca/doca.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/doca-collaboration .claude/skills/doca-collaboration && 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/

Paste into Claude Code

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .claude/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smartdoca/doca.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/doca-collaboration .agents/skills/doca-collaboration && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .agents/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smartdoca/doca.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/doca-collaboration .cursor/skills/doca-collaboration && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .cursor/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/smartdoca/doca.git --path skills/doca-collaboration

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smartdoca/doca.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/doca-collaboration .gemini/skills/doca-collaboration && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .gemini/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/smartdoca/doca.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/doca-collaboration .github/skills/doca-collaboration && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .github/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add smartdoca/doca --skill doca-collaboration -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install smartdoca/doca doca-collaboration --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/smartdoca/doca.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/doca-collaboration .opencode/skills/doca-collaboration && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "doca-collaboration" agent skill from https://github.com/smartdoca/doca/tree/main/skills/doca-collaboration into .opencode/skills/doca-collaboration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "doca-collaboration", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: doca-collaboration
GitHub stars: 118
Token cost: ~1.4k tokens
SKILL.md length: 698 words
Files: 4 (incl. references)
Skills in repo: 3
Repo updated: Oct 4, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Collaboration SDK changes
SKILL.md covers Scope and maintenance, Core constraints, Package upgrade workflow and Verification
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Subpackage development

What it does

Doca Collaboration is an agent skill from smartdoca/doca. Implement, review, or upgrade realtime collaboration between Doca and any document-type editor subpackage (rich text, spreadsheet, Markdown, canvas, slides, and future formats) using the shared Yjs lifecycle, version, acknowledgement, presence, and comment-anchor contract. Use for collaboration SDK changes, subpackage development, and host package integration, not unrelated UI work.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `agents/openai.yaml`, `references/contract.md` and `references/file-exchange.md`).

It sits in Documents & Office, covering Excel spreadsheets and Slides and decks. The repository describes itself as: Document and knowledge base for individuals and small teams. The licence is MIT.

When your agent uses it

Collaboration SDK changes
Subpackage development
Host package integration
Not unrelated UI work

Example prompts

“/doca-collaboration”

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Doca Collaboration loads about 1.4k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 698 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 smartdoca/doca at commit b4356a4, republished under its MIT licence (© smartdoca). 698 words, ~1,439 tokens.

Download SKILL.mdSave it as .claude/skills/doca-collaboration/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: doca-collaboration
description: Implement, review, or upgrade realtime collaboration between Doca and any document-type editor subpackage (rich text, spreadsheet, Markdown, canvas, slides, and future formats) using the shared Yjs lifecycle, version, acknowledgement, presence, and comment-anchor contract. Use for collaboration SDK changes, subpackage development, and host package integration, not unrelated UI work.

Doca collaboration

Read the full contract before changing collaboration behavior. It is a target contract plus a dated implementation inventory, not evidence that an API already exists. Inspect the current package README, exports, source and tests before using any proposed API.

Scope and maintenance

This contract governs every document-type editor subpackage — rich text, spreadsheet, Markdown, canvas, slides and future formats — not only slatetsx/exlsx. Format-specific rules (Excel baseline, stable row/column anchors) are the format's instances of the shared contract, not exceptions from it.

Subpackage developers and Doca host developers maintain this contract together: a change is only valid when both sides agree, and the project source documents (docs/collaboration-sdk-contract.md, docs/editor-file-exchange-contract.md) and every packaged skill copy (project skills/ and user skills directories) must be updated in the same change. Do not let the copies drift.

Core constraints

Unify transport, authentication, durable ACK, outbox and reconnect behavior. Keep format-specific data models behind codec adapters; never convert a workbook into a text CRDT just for uniformity.
Separate protocolVersion, codec/schemaVersion, epochId, seq, checkpointSeq, resource.version and business history IDs. Epoch identity is always carried as epochId.
Initialize from a server-authoritative, atomically paired baseline and Yjs state, then mount one stable editor instance. Props, readonly, selection, save state and resize must not rebuild the document or mutate shared state.
Only local content transactions enter the outbox. Remote/bootstrap/presence/focus/scroll changes must not generate writes or operation IDs. Do not introduce a second autosave transport.
ACK only after database commit. Keep original bytes and message ID until the matching ACK; a sync response is not an ACK. Never infer dirty state from a nonempty vector diff: an already synchronized deletion set can still be returned.
Replay unacknowledged updates on reconnect; refuse mismatched epochs and unknown schemas. Do not silently discard pending work or apply it to a replacement baseline. No offline-durability claims without persistent storage.
Preserve CRDT identities in checkpoints. Excel restores immutable baseline plus commands of that epoch, never a latest workbook snapshot plus old commands.
Session identity and color come from the server. Same account in two pages has two selections. Presence is temporary, permission checked and non-persistent. Text uses relative points; cells use sheet/range plus editing state; never transmit typed content through presence.
Permanent comment anchors are distinct from presence coordinates. Excel needs stable row/column identities with deletion handling. Do not fake permanent anchors with A1 coordinates.
Content changes, validation, ACL and persistence remain atomic. Recheck authorization on writes/broadcasts. Unknown/duplicate ACKs cannot clear other pending edits.

Show full SKILL.md (290 more words)Show less

Package upgrade workflow

Read the new package's integration documentation and compare exported APIs/schema with the currently installed build. Build/pack and install the actual updated artifact; when versions are reused, use a new hash-qualified filename and lockfile entry to avoid stale caches. Keep the previous artifact and a rollback route. Do not modify upstream source just to force host compatibility without task authorization.

Adapt host bindings, codec validation and exact current-schema negotiation together. This project accepts only the current empty-database/document baseline; schema changes replace that baseline and do not add migration paths. Declare upstream gaps explicitly rather than silently approximating them.

Verification

Use isolated test data, not user documents. For affected paths verify:

Idle open, selection, scroll and resize produce zero content updates for 60 seconds.
Two replicas converge; remote application causes no echo. Same-user tabs show distinct presence; readonly does not publish/render editing selections.
Pure deletions followed by repeated sync do not re-upload indefinitely.
Lost/delayed/duplicate ACKs, reconnect and edits during remote reception do not lose data or show premature saved state.
Snapshot plus log restoration and compaction preserve the online projection; mismatched epoch/schema is rejected.
For Excel, test each changed operation class (row/column insertion/deletion, cells, formulas, merges, sorting/filtering, undo). Do not claim all operations converge from a cell-edit test.
Revocation, disabled/anonymous users and spoofed identity/invalid ranges are handled.
Format state drives both toolbars; no remount/focus loss on status updates.

In the handoff distinguish implemented behavior, verified tests, external-service verification, and still-proposed contract changes. A successful build alone is not collaboration verification.

For file import/export touching initialization or persistence, read file exchange. Default imports establish a new resource and lineage; exports are read-only projections. A converter must not clear an outbox, initialize an already-open document, or silently replace the active baseline.

Files

SKILL.md and 3 other files (references) in skills/doca-collaboration of smartdoca/doca.

SKILL.md
agents/openai.yaml
references/contract.md
references/file-exchange.md

Open the folder on GitHubat commit b4356a4

Compare with similar skills

Doca 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.

Doca Collaboration compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Doca Collaboration this skillsmartdoca/doca	118	—	~1.4k	Automated safety check: Pass	MIT	4 days ago
Xiaobei Skill Image To Vbaxiao24bei/xiaobei-skill	582	—	~6.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Harness Useautonomous-ai/Physical-AI-Operating-System	381	—	~8k	Automated safety check: Pass	Apache-2.0	today
Sn Da Non Spreadsheet AnalysisOpenSenseNova/SenseNova-Skills	5.7k	—	~1.2k	Automated safety check: Pass	MIT	20 days ago
Jev Office GatePluviobyte/rnskill	1.6k	—	~965	Automated safety check: Pass	Custom licence	17 days ago
Office Productivityaiskillstore/marketplace	430	3 repos	~1.2k	Automated safety check: Pass	None	yesterday

Similar skills

Xiaobei Skill Image To Vba
xiao24bei/xiaobei-skill
A skill your agent uses when users want XiaoBei skill / xiaobei-skill / 小北在读研 style academic image-to-VBA reconstruction: convert academic figures, scientific diagrams, slides, screenshots, or other…
582 GitHub stars~6.9k tokensUpdated 1 mo ago
Documents & OfficeAuto-check passed
Harness Use
autonomous-ai/Physical-AI-Operating-System
Delegate digital work to agents on the computer paired through Harness; discover Store packages and prepare an agent when needed.
381 GitHub stars~8k tokensUpdated today
Documents & OfficeAuto-check passed
Sn Da Non Spreadsheet Analysis
OpenSenseNova/SenseNova-Skills
Word / PDF / PPT 文档解析与数据分析引擎。覆盖三类文件格式的全量提取、表格数值化、图表理解与跨文档汇总分析。遇到以下任一情况就主动使用本 skill：①用户上传或指定了 .docx / .doc / .pdf / .pptx / .ppt 文件并要求分析、提取或统计其中内容；②用户出现触发词：Word分析 / PDF解析 / PPT提取 / 文档分析 / 报告解析 /…
5.7k GitHub stars~1.2k tokensUpdated 20 days ago
Documents & OfficeAuto-check passed
Jev Office Gate
Pluviobyte/rnskill
Add a Jev-powered decision and release gate after an office assistant generates a report, proposal, spreadsheet, document, or slide deck.
1.6k GitHub stars~965 tokensUpdated 17 days ago
Documents & OfficeAuto-check passed
Office Productivity
aiskillstore/marketplace
Office productivity workflow covering document creation, spreadsheet automation, presentation generation, and integration with LibreOffice and Microsoft Office formats.
430 GitHub starsUsed in 3 repos~1.2k tokens
Documents & OfficeAuto-check passed
Tencent Docs
LeoYeAI/openclaw-master-skills
Tencent Docs - Provides complete Tencent Docs operations. An agent skill from LeoYeAI/openclaw-master-skills.
2.2k GitHub stars~3k tokensUpdated 2 mo ago
Documents & OfficeAuto-check passed

Questions about Doca Collaboration

What does Doca Collaboration do?

Implement, review, or upgrade realtime collaboration between Doca and any document-type editor subpackage (rich text, spreadsheet, Markdown, canvas, slides, and future formats) using the shared Yjs…. Doca Collaboration is an agent skill from smartdoca/doca. Implement, review, or upgrade realtime collaboration between Doca and any document-type editor subpackage (rich text, spreadsheet, Markdown, canvas, slides, and future formats) using the shared Yjs lifecycle, version, acknowledgement, presence, and comment-anchor contract.

When should I use Doca Collaboration?

Doca Collaboration fits situations like: collaboration SDK changes; subpackage development; host package integration; not unrelated UI work.

How do I install Doca Collaboration in Claude Code?

Run `npx skills add smartdoca/doca --skill doca-collaboration -a claude-code`. Or copy the skill folder (skills/doca-collaboration in smartdoca/doca) into .claude/skills/doca-collaboration in your project. Claude Code loads it when a task matches its description.

How do I install Doca Collaboration in Codex?

Run `npx skills add smartdoca/doca --skill doca-collaboration -a codex`. Or copy the skill folder (skills/doca-collaboration in smartdoca/doca) into .agents/skills/doca-collaboration in your project. Codex loads it when a task matches its description.

Can I use Doca 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 smartdoca/doca --skill doca-collaboration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/doca-collaboration, .gemini/skills/doca-collaboration, .github/skills/doca-collaboration and .opencode/skills/doca-collaboration in your project.

What does Doca Collaboration need to run?

SKILL.md names no scripts, command-line tools or credentials: Doca Collaboration is instructions for the agent only.

Does Doca Collaboration access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Doca Collaboration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Doca Collaboration use?

Doca 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 Doca Collaboration use?

About 1.4k tokens (SKILL.md is roughly 5.8k 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 5.2k tokens, read only when the agent opens those files.

What are the alternatives to Doca Collaboration?

Skills that share tags, products or a category with Doca Collaboration: Xiaobei Skill Image To Vba (xiao24bei/xiaobei-skill, 582 stars), Harness Use (autonomous-ai/Physical-AI-Operating-System, 381 stars), Sn Da Non Spreadsheet Analysis (OpenSenseNova/SenseNova-Skills, 5.7k stars) and Jev Office Gate (Pluviobyte/rnskill, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Doca Collaboration?

smartdoca (a GitHub user) maintains it in smartdoca/doca, which has 118 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 4, 2026.

Source: smartdoca/doca on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Doca Collaboration

Install Doca Collaboration

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Doca collaboration

Scope and maintenance

Core constraints

Package upgrade workflow

Verification

Files

Compare with similar skills

Similar skills

Xiaobei Skill Image To Vba

Harness Use

Sn Da Non Spreadsheet Analysis

Jev Office Gate

Office Productivity

Tencent Docs

More from smartdoca/doca

Doca I18n

Doca Editor Integration

Questions about Doca Collaboration

Install Doca Collaboration

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Doca collaboration

Scope and maintenance

Core constraints

Package upgrade workflow

Verification

Files

Compare with similar skills

Similar skills

More from smartdoca/doca

Related

Questions about Doca Collaboration