Update Jamdesk Documentation for Openclaw

An automated doc-syncing skill that monitors code changes, writes structured MDX documentation, validates links, and commits changes to Jamdesk repos.

gbourne1
v1.0.1
Jun 11, 2026
2
514
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install update-jamdesk

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install update-jamdesk using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Update Jamdesk Documentation?

The update-jamdesk skill is designed to automate the process of keeping customer-facing documentation in sync with codebase changes. Built for developers using Openclaw Skills, this skill seamlessly bridges the gap between feature implementation and clear, accurate technical writing. It walks the developer and the AI agent through a highly organized workflow: locating configuration files, planning document structure, writing standard MDX content, and executing localized validation.

By leveraging the native jamdesk CLI, the skill checks for configuration schemas and broken links before any changes are committed. Whether your documentation lives in the same repository or an external Git workspace, this skill guarantees that no user-facing API changes, UI enhancements, or CLI commands go undocumented, maintaining high-quality docs without the manual overhead.

Update Jamdesk Documentation Use Cases

  • When implementing new public-facing APIs, CLI commands, configuration options, or UI components that require immediate documentation update.
  • When proactively maintaining technical accuracy after feature updates, ensuring outdated documentation is automatically flagged and resolved.
  • When performing major code deprecations and migrating usage instructions or adding warnings for destructive operations.
  • When updating docs.json navigation schemas and maintaining structured, multi-page technical guides.

How Update Jamdesk Documentation Works

  1. Locate Configuration: Searches up to the Git root for a .jamdesk-docs-path YAML file to identify the documentation folder and preferred Git branch.
  2. Preflight Checks: Checks if the target path contains docs.json, verifies the installation of the jamdesk CLI, and confirms the Git working tree is clean.
  3. Clarify Scope: Confirms the branching strategy (for external documentation repos) and presents a proposed list of new or modified pages to the user.
  4. Analyze & Map Docs: Scans the target directory for existing references, identifying if a change requires a brand-new MDX file, an added section, or interactive components like accordions.
  5. Write Standardized MDX: Generates clean, active-voice Markdown/MDX content with frontmatter descriptions, target-audience context, concrete examples, and verified navigation structures.
  6. Validate & Verify: Executes the CLI tools to check schema validity and uncover broken links, reverting safely if validation issues are detected.
  7. Commit & Push: Prompts the user to commit changes under docs: [action] format, with optional PR generation for external repos.

Update Jamdesk Documentation Setup

Configure the skill in your project by placing a .jamdesk-docs-path YAML configuration file at your repository's Git root:

docs_path: ../customer-docs    # Relative or absolute path to your docs folder
docs_branch: main              # Base branch for documentation updates

Ensure that your target documentation directory includes a valid docs.json file. If you are using Openclaw Skills to validate documentation locally, make sure the jamdesk CLI is globally accessible:

npm install -g @jamdesk/cli

If the CLI is not detected, the skill will gracefully fall back to a manual checklist to verify your frontmatter structure, images, and relative links before completion.

Update Jamdesk Documentation Data Schema & Taxonomy

The skill relies on specific YAML configuration files and standardizes MDX structures as follows:

File / Location Format Description
.jamdesk-docs-path YAML Located at the code repo Git root; stores relative path to the docs repository and the base target branch.
docs.json JSON Located in the target docs folder; defines navigation structures and doc hierarchies.
Page Frontmatter YAML-like Located at the top of MDX files; requires title (<= 60 chars) and a unique, SEO-friendly description (120-160 chars).
Image Assets Binary / Absolute Paths Stored in /images/<feature>/ directory inside the docs repository.

Minimal MDX Document Layout

---
title: Feature Name
description: SEO description (120-160 chars, unique per page)
lastUpdated: YYYY-MM-DD
---

Opening introduction context.

## Prerequisites
- Node.js 18+

## Quick Start
```bash
# Run command

Update Jamdesk Documentation Advanced Features

  • External & Multi-Repo Orchestration: Automatically handles separate branch strategies, diff presentations, and commit flows when your documentation lives in a completely different Git repository.
  • Intelligent Dry-Run Preview: Run with --preview flag to analyze changes, generate documentation mappings, and review prospective creations without modifying active files.
  • Built-in Component Richness: Integrates structured UI components such as <Tabs>, <Steps>, <Accordion>, and <CodeGroup> directly into your generated MDX files.
  • Self-healing Reverts: Restricts checkout reverts strictly to the workspace files written by this specific skill run, protecting pre-existing uncommitted user changes from accidental deletion.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*