Skip to main content

OpenClaw

OpenClaw is a terminal-native AI agent that works directly in your shell. Because it already reads and writes files and executes commands as part of its workflow, OpenDocs publishing feels like a natural final step rather than a separate tool to learn.

Setup​

Install the CLI and authenticate:

npm install -g @opendocs.cc/cli
opendocs login

Then point OpenClaw at the OpenDocs SKILL.md. This teaches OpenClaw the full OpenDocs workflow — publish, update, list, pull, and unpublish — so it remembers across sessions without you having to repeat instructions.

Example prompts​

Publish a new doc:

Write a Markdown implementation note for the payments migration,
publish it with OpenDocs, and give me the shareable URL.

Update an existing doc:

Pull the latest version of our API changelog from OpenDocs, add the
new rate limiting section, and publish the update.

Publish with specific settings:

Write up the database schema changes as Markdown, publish it to
OpenDocs with the slug "db-schema-v3" and tags "database, migration",
and return the URL.

Common workflows​

One-shot documentation​

The simplest pattern — ask OpenClaw to write and publish in a single task:

opendocs publish payments-migration.md --json

OpenClaw writes the file, runs the command, and returns the URL.

Iterative updates​

For docs that evolve over time, have OpenClaw track the postId:

# First publish
opendocs publish api-changelog.md --json
# Returns: { "postId": "abc123", "url": "..." }

# Later update
opendocs update abc123 api-changelog.md --json

Ask OpenClaw to include the postId in its response so you can reference it in follow-up tasks.

Team-wide publishing​

For workspace docs, OpenClaw can publish with workspace visibility (the default) so everyone on your team sees the doc immediately:

opendocs publish rollout-plan.md --json

If you want a public URL to share outside your team:

opendocs publish rollout-plan.md --visibility public --json

Tips​

  • Use SKILL.md — OpenClaw retains the full publishing workflow across sessions when configured with the skill file
  • Always use --json — OpenClaw parses structured output cleanly and can extract the URL and postId automatically
  • Return the postId — ask OpenClaw to include it in its final answer for any doc you expect to update later