Write
@ivangdavila
npx machina-cli add skill @ivangdavila/write --openclawSetup
On first use, create workspace:
./scripts/init-workspace.sh ~/writing
Workflow
Request → Plan → Draft → Audit → Refine → Deliver
Rules:
- Delegate all writing to sub-agents — main stays free
- NEVER edit files directly — use
./scripts/edit.sh(enforces versioning) - Run quality audit before delivering anything long (see
audit.md) - Offer cleanup only after user confirms piece is final
Configuration
Set in config.json:
depth: "quick" | "standard" | "thorough" — controls research and revision passesauto_audit: true/false — run audits automatically after drafts
Scripts (Enforced)
| Script | Purpose |
|---|---|
init-workspace.sh | Create project structure |
new-piece.sh | Start new writing piece with ID |
edit.sh | Edit with automatic version backup |
audit.sh | Run quality audit, generate report |
list.sh | Show all pieces and versions |
restore.sh | Restore previous version |
cleanup.sh | Remove old versions (with confirmation) |
References: brief.md for planning, execution.md for drafting, verification.md for quality checks, state.md for tracking, research.md for investigation, versioning.md for version rules, audit.md for dimensions, criteria.md for preferences. Scripts in scripts/: scripts/init-workspace.sh, scripts/new-piece.sh, scripts/edit.sh, scripts/audit.sh, scripts/list.sh, scripts/restore.sh, scripts/cleanup.sh.
Preferences
<!-- User's writing preferences -->Never
<!-- Things that don't work for this user -->Empty sections = observe and fill.
Overview
Write enables plan, draft, versioning, and refinement of content with enforced version backups and audit checks. It follows a structured flow: Request → Plan → Draft → Audit → Refine → Deliver, and delegates actual writing to sub-agents while enforcing version control through scripts. References to planning, drafting, verification, and versioning docs guide its process.
How This Skill Works
Initialize a workspace with init-workspace.sh, start a piece with new-piece.sh, and edit only through edit.sh to create automatic version backups. Audits are performed with audit.sh, and can be triggered automatically after drafts if auto_audit is enabled; never edit files directly, and cleanup only after the piece is finalized.
When to Use It
- Starting a new writing piece that requires strict version history and audits
- Collaborating with sub-writers on a multi-section article
- Preparing a long-form document that must be audited before publication
- Restoring a previous version during a rewrite or after feedback
- Delivering a final piece only after a comprehensive quality audit
Quick Start
- Step 1: Initialize workspace with ./scripts/init-workspace.sh ~/writing
- Step 2: Start a new piece with ./scripts/new-piece.sh <ID>
- Step 3: Edit with ./scripts/edit.sh and run audits via ./scripts/audit.sh, then deliver
Best Practices
- Always use edit.sh for changes to enforce version backups
- Run audit.sh on long drafts or enable auto_audit for automatic checks
- Break work into pieces with new-piece.sh to manage versions
- Avoid direct file edits; rely on the workflow and versioning rules
- Configure depth and auto_audit in config.json to match project needs
Example Use Cases
- Drafting a product whitepaper with incremental revisions and audits
- Writing a technical article with section level drafting by sub-agents
- Publishing a blog series where each post is versioned and audited
- Creating a long-form report and restoring a prior version after feedback
- Coordinating with teammates to deliver a polished piece after final audit
