openclaw-stow

Deploy OpenClaw configuration files to the home directory using GNU stow symlinks.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-stow-diazmelgarejo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-stow
Source: https://github.com/diazMelgarejo/orama-system/tree/main/bin/orama-system/skills/openclaw-skills/skills/openclaw-stow
Command: npx skills add https://github.com/diazMelgarejo/orama-system --skill openclaw-stow-diazmelgarejo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stow.

What problem does it solve? Manually copying OpenClaw configuration files into the home directory causes drift and conflicts, especially when the gateway rewrites runtime files like jobs.json. This Skill deploys repository-managed OpenClaw configs as deterministic symlinks with GNU stow, handling the known cron conflict before stowing. ## Core Features & Use Cases - Deterministic Symlink Deployment: Applies repository-managed OpenClaw files to the target home directory using stow with --no-folding semantics. - Cron Conflict Handling: Removes the transient ~/.openclaw/cron/jobs.json file before stowing so cron remains stable after gateway restarts. - Dry-Run and Verification: Supports a dry_run mode to preview changes and detects unresolved conflicts before mutating anything. - Use Case: After manually editing managed OpenClaw config files or pulling updates, run this Skill to redeploy symlinks, then follow up with openclaw-restart to load runtime changes. ## Quick Start Deploy my OpenClaw configuration to the home directory with stow, resolving the jobs.json cron conflict first and confirming the symlinks were created.

Frequently Asked Questions about openclaw-stow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy OpenClaw config files with GNU stow?

Run stow with --no-folding against the target home directory after removing ~/.openclaw/cron/jobs.json. The Skill validates stow availability, detects unresolved conflicts with a dry run, and confirms critical symlinks exist.

Why does stow fail on the OpenClaw jobs.json file?

The gateway startup rewrites jobs.json, replacing the symlink with a regular file, which blocks stow. Remove ~/.openclaw/cron/jobs.json before stowing so the symlink can be recreated cleanly.

Can I preview stow changes without modifying files?

Yes, set the dry_run input to true. The Skill runs stow with -n -v to preview the deployment and exits without mutating anything, letting you resolve conflicts first.

Do I need to restart OpenClaw after stowing configs?

Yes, a successful stow only updates symlinks on disk. Pair this Skill with openclaw-restart so the gateway loads the new runtime configuration.

What are the limitations of stow-based OpenClaw deployment?

Stowing from the wrong directory creates valid symlinks in the wrong place, and dry-run output may show stale conflicts from paths outside OpenClaw scope. Always verify the target root before deploying.