@elvatis_com/openclaw-shortcuts
v0.2.0
Published
OpenClaw plugin: config-driven /shortcuts command with safe placeholder defaults
Readme
openclaw-shortcuts
Enhanced /shortcuts and /projects commands for OpenClaw.
Commands
| Command | Description |
|---------|-------------|
| /shortcuts | Show local shortcuts and helper commands (config-driven, generic by default) |
| /projects | List all local git repos in the workspace with version and GitHub visibility |
Security note
This plugin is intentionally generic by default. Do not hardcode personal commands, group names, phone numbers, or private workflow details into the repository.
Instead, customize the output via plugin config.
Install (dev)
openclaw plugins install -l ~/.openclaw/workspace/openclaw-shortcuts
openclaw gateway restartClawHub
clawhub install openclaw-shortcutsConfigure
The repo stays placeholder-only. You customize /shortcuts locally via plugin config.
Example (using public projects as references):
{
"plugins": {
"entries": {
"openclaw-shortcuts": {
"enabled": true,
"config": {
"includeTips": true,
"sections": [
{
"title": "Public example projects",
"lines": [
"- AAHP - protocol + handoff structure example",
"- BMAS - research project example"
]
},
{
"title": "Your shortcuts (fill in locally)",
"lines": [
"- /<project> - your project shortcut",
"- /<command> - your custom command"
]
}
]
}
}
}
}
}Security reminder: keep private commands, phone numbers, group IDs, tokens, and internal workflows out of the repo. Store them only in local config.
Shared Template
For automation that creates GitHub issues, use src/templates/github-issue-helper.ts.
It provides isValidIssueRepoSlug(), resolveIssueRepo(), and buildGhIssueCreateCommand().
// ===== FEATURE VERSION =====
openclaw-shortcuts
OpenClaw plugin providing a config-driven
/shortcutscommand with safe placeholder defaults.
Current version: 0.1.0
Replaces:
openclaw-help(deprecated — name was misleading; plugin never registered/helpbut/shortcuts)
What it does
Registers /shortcuts in your OpenClaw agent.
Prints:
- Generic placeholder sections by default
- Custom sections injected via local
openclaw.jsonconfig
Security design: The repo ships with placeholder-only content. All personal shortcuts, project names, and command mappings live in your local config — never in the repo.
Install
clawhub install openclaw-shortcutsOr local development:
openclaw plugins install -l ~/.openclaw/workspace/skills/openclaw-shortcuts
openclaw gateway restartConfigure
In ~/.openclaw/openclaw.json → plugins.entries.openclaw-shortcuts.config:
{
"enabled": true,
"includeTips": false,
"sections": [
{
"title": "📁 Projects",
"lines": [
"/<project> - Your project shortcut"
]
},
{
"title": "🛠 Tools",
"lines": [
"/<command> - Your custom command"
]
}
]
}OPSEC rule
- Never put personal commands, phone numbers, group IDs, tokens, or internal workflows into this repo
- Keep all real shortcuts in local config only
Changelog
v0.1.0
- Initial release (merged from deprecated
openclaw-help) - Registers
/shortcutswithrequireAuth: false - Config-driven sections via
openclaw.json - Safe placeholder defaults
License
MIT
