ClawKit Logo
ClawKitReliability Toolkit
Back to Registry
Official Verified productivity Safety 5/5

openclaw-help

OpenClaw plugin providing a config-driven /help command (safe placeholder-only defaults).

Why use this skill?

Install openclaw-help to manage agent commands safely. Keep your private shortcuts local and secure with our config-driven help menu for OpenClaw.

skill-install — Terminal

Install via CLI (Recommended)

clawhub install openclaw/skills/skills/homeofe/openclaw-help
Or

What This Skill Does

The openclaw-help skill is designed to provide a centralized, highly configurable command interface for your OpenClaw agent without compromising sensitive information. By default, it registers a /help command that outputs structured, placeholder-based documentation. Its primary architectural philosophy is to separate public-facing agent logic from private user data. Instead of hardcoding project-specific shortcuts, team contact details, or internal workflow identifiers into your plugin repository or shared configuration, this skill allows you to maintain generic placeholders in public files while injecting your sensitive, private data locally through your ~/.openclaw/openclaw.json configuration file. It renders help sections dynamically, allowing for clean categorization of commands, memory references, or todo lists, ensuring that your agent's help menu remains useful to you personally without exposing your secrets to the world when you publish your workflows.

Installation

To install this skill, you have two primary options based on your use case:

  1. From the ClawHub registry: Run clawhub install openclaw-help to pull the latest version directly from the repository.
  2. For local development or custom modification: Clone the repository to a local directory, then run openclaw plugins install -l ~/.openclaw/workspace/openclaw-help. After installing, remember to execute openclaw gateway restart to apply the plugin changes to your active agent runtime.

Use Cases

This skill is essential for users who frequently share their OpenClaw configurations across different environments or public GitHub repositories. It is ideal for:

  • Managing private development shortcuts that shouldn't be publicly visible.
  • Keeping team-specific onboarding information or internal documentation in a local-only file.
  • Providing a clean, professional interface for agent interaction without cluttering the main logic with sensitive identifiers like phone numbers, private project domains, or API-related command aliases.

Example Prompts

  • "/help"
  • "/help --verbose"
  • "/help --show-all"

Tips & Limitations

When using openclaw-help, strictly adhere to the OPSEC rule: never commit files containing private commands, phone numbers, or tokens to version control. Always maintain sensitive data in your local ~/.openclaw/ directory. Be aware that this plugin is a presentation layer; it does not encrypt the data in your config file, so ensure your local filesystem permissions are secure. The skill is intentionally designed to be lightweight and does not perform advanced parsing of the shortcuts it displays, meaning you must manage the syntax of your command aliases manually within your configuration file.

Metadata

Author@homeofe
Stars2387
Views0
Updated2026-03-09
View Author Profile
AI Skill Finder

Not sure this is the right skill?

Describe what you want to build — we'll match you to the best skill from 16,000+ options.

Find the right skill
Add to Configuration

Paste this into your clawhub.json to enable this plugin.

{
  "plugins": {
    "official-homeofe-openclaw-help": {
      "enabled": true,
      "auto_update": true
    }
  }
}

Tags(AI)

#productivity#configuration#opsec#cli-helper
Safety Score: 5/5

Flags: file-read