WritingGeneral FoundationFreedomIntelligence/OpenClaw-Medical-SkillsPaper Writing & Submission

doc-coauthoring

Maintainer FreedomIntelligence · Last updated March 31, 2026

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentati….

OpenClawNanoClawWritingSubmissiondoc-coauthoring🧰 general & coregeneral toolsguide

Original source

FreedomIntelligence/OpenClaw-Medical-Skills

https://github.com/FreedomIntelligence/OpenClaw-Medical-Skills/tree/main/skills/doc-coauthoring

Maintainer: FreedomIntelligence
License: MIT
Last updated: March 31, 2026

Skill Snapshot

Key Details From SKILL.md

2 min

Key Notes

This skill provides a structured workflow for guiding users through collaborative document creation. Act as an active guide, walking users through three stages: Context Gathering, Refinement & Structure, and Reader Testing.
User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up.
User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC.
User seems to be starting a substantial writing task.
Trigger conditions: User mentions writing documentation: "write a doc", "draft a proposal", "create a spec", "write up" User mentions specific doc types: "PRD", "design doc", "decision doc", "RFC" User seems to be starting a substantial writing task.

Source Doc

Excerpt From SKILL.md

Stage 1: Context Gathering

Goal: Close the gap between what the user knows and what Claude knows, enabling smart guidance later.

Initial Questions

Start by asking the user for meta-context about the document:

What type of document is this? (e.g., technical spec, decision doc, proposal)
Who's the primary audience?
What's the desired impact when someone reads this?
Is there a template or specific format to follow?
Any other constraints or context to know?

Inform them they can answer in shorthand or dump information however works best for them.

If user provides a template or mentions a doc type:

Ask if they have a template document to share
If they provide a link to a shared document, use the appropriate integration to fetch it
If they provide a file, read it

If user mentions editing an existing shared document:

Use the appropriate integration to read the current state
Check for images without alt-text
If images exist without alt-text, explain that when others use Claude to understand the doc, Claude won't be able to see them. Ask if they want alt-text generated. If so, request they paste each image into chat for descriptive alt-text generation.