doc-coauthoring

Estrelas10

Forks2

Atualizado16 de junho de 2026 às 11:28

Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

canvascoding

canvascoding/canvas-notebook

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Redatores técnicosArtes, Design, Entretenimento, Esportes e Mídia·SOC 27-3042

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	doc-coauthoring
description	Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.
license	Canvas Notebook Sustainable Use License

Doc Co-authoring

This skill helps turn rough context into a useful document. It is a clean-room Canvas skill; do not copy vendor skill material, hidden prompts, or proprietary workflow text into this folder.

Workflow

Frame the job. Confirm document type, audience, decision or action the reader should take, desired tone, target length, deadline, and any required template.
Collect context. Invite an unstructured dump, linked notes, existing drafts, stakeholder constraints, decisions already made, non-goals, risks, and open questions.
Propose structure. Suggest a short outline tailored to the document type. Ask for approval or edits before drafting if the stakes are high.
Draft in sections. Work section by section. For each section, ask only the clarifying questions needed to proceed, then draft concise prose.
Revise surgically. Apply requested edits without rewriting unrelated sections. Preserve the user's terminology and organizational context.
Fresh-reader pass. Review the draft as if the reader has no chat context. Check whether the purpose, assumptions, terms, decision points, risks, and next steps are understandable from the document alone.
Finalize. Remove placeholders, contradictions, stale notes, and internal comments. Produce the requested format.

Document Patterns

Decision memo: context, decision, options considered, rationale, tradeoffs, risks, owner, next steps.
Technical spec: problem, goals, non-goals, architecture, interfaces, rollout, migration, observability, tests, risks.
Proposal: audience need, recommendation, scope, deliverables, timeline, cost or effort, risks, approval path.
Operating guide: purpose, prerequisites, procedure, edge cases, troubleshooting, escalation, ownership.
PRD: user problem, goals, requirements, UX notes, metrics, dependencies, milestones, launch criteria.

Quality Rules

Prefer specific nouns and concrete decisions over broad claims.
Keep summary sections short; put details where readers expect them.
Mark unresolved questions explicitly instead of hiding uncertainty.
Do not invent stakeholder commitments, metrics, sources, or decisions.
If the document will become DOCX, PDF, PPTX, or XLSX, use the relevant file skill for final artifact creation and verification.

Mais deste repositório

mesmo repositório

create-plugin

canvascoding/canvas-notebook

Create, update, validate, and package Canvas Plugins. Use when users want to build a Canvas plugin, bundle multiple skills into a plugin, define plugin metadata, add icons or logos, declare recommended Composio, Canvas Email, or MCP connectors, prepare a marketplace entry, or submit a plugin to the Canvas Plugin Store.

2026-07-1010

greploop

canvascoding/canvas-notebook

Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until it reaches the repository's configured Greptile merge threshold with zero unresolved actionable comments, or until the five-review maximum is reached. Triggers Greptile review, fixes all actionable comments, pushes/re-shelves, re-triggers review only for new head SHAs unless a 5/5 score is already published, and repeats. Use when the user wants to optimize a PR/MR/CL against Greptile's code review standards without creating runaway review loops.

2026-06-2910

release-publisher

canvascoding/canvas-notebook

Publish a new Canvas Notebook release. Use this skill whenever the user asks to bump a version, prepare release notes, update CHANGELOG.md, create or push a git tag, publish a GitHub Release, deploy, or automate the release workflow. This skill covers the full release sequence for this repository: inspect commits/tags, push completed product-code commits first when authorized, confirm the pushed code has built on GitHub, choose the next calendar version, update package and CLI versions, update the changelog, run the required local build, commit, push the release commit, wait for the remote Build and Push worker on the pushed branch, tag, push the tag, and publish the release.

2026-06-2910

opensrc

canvascoding/canvas-notebook

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", "opensrc path", or any task requiring access to dependency source code beyond types and docs.

2026-06-2910

marp-slides

canvascoding/canvas-notebook

Create, edit, review, preview, and export polished Marp Markdown slide decks in Canvas Notebook. Use when the user wants Markdown-native presentations, `.marp.md` or `.slides.md` files, version-controlled decks, Marp PDF/image/PPTX/HTML export, speaker notes, dashboard-style slides, data cards, or better looking decks that should remain close to plain text.

2026-06-1910

algorithmic-art

canvascoding/canvas-notebook

Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.

2026-06-1610

name	doc-coauthoring
description	Use this Canvas-owned clean-room skill to guide collaborative writing for documentation, proposals, technical specs, decision records, PRDs, RFCs, operating guides, and structured memos. Trigger when the user wants help drafting, organizing, refining, reviewing, or testing a document before sharing it.
license	Canvas Notebook Sustainable Use License

Doc Co-authoring

This skill helps turn rough context into a useful document. It is a clean-room Canvas skill; do not copy vendor skill material, hidden prompts, or proprietary workflow text into this folder.

Workflow

Frame the job. Confirm document type, audience, decision or action the reader should take, desired tone, target length, deadline, and any required template.
Collect context. Invite an unstructured dump, linked notes, existing drafts, stakeholder constraints, decisions already made, non-goals, risks, and open questions.
Propose structure. Suggest a short outline tailored to the document type. Ask for approval or edits before drafting if the stakes are high.
Draft in sections. Work section by section. For each section, ask only the clarifying questions needed to proceed, then draft concise prose.
Revise surgically. Apply requested edits without rewriting unrelated sections. Preserve the user's terminology and organizational context.
Fresh-reader pass. Review the draft as if the reader has no chat context. Check whether the purpose, assumptions, terms, decision points, risks, and next steps are understandable from the document alone.
Finalize. Remove placeholders, contradictions, stale notes, and internal comments. Produce the requested format.

Document Patterns

Decision memo: context, decision, options considered, rationale, tradeoffs, risks, owner, next steps.
Technical spec: problem, goals, non-goals, architecture, interfaces, rollout, migration, observability, tests, risks.
Proposal: audience need, recommendation, scope, deliverables, timeline, cost or effort, risks, approval path.
Operating guide: purpose, prerequisites, procedure, edge cases, troubleshooting, escalation, ownership.
PRD: user problem, goals, requirements, UX notes, metrics, dependencies, milestones, launch criteria.

Quality Rules

Prefer specific nouns and concrete decisions over broad claims.
Keep summary sections short; put details where readers expect them.
Mark unresolved questions explicitly instead of hiding uncertainty.
Do not invent stakeholder commitments, metrics, sources, or decisions.
If the document will become DOCX, PDF, PPTX, or XLSX, use the relevant file skill for final artifact creation and verification.