ClawHub

Keybindings Customizer

v1.0.0

Use when the user wants to customize Claude Code keybindings, rebind shortcuts, add chords, or edit `~/.claude/keybindings.json` safely.

⭐ 0· 107·0 current·0 all-time
by@wimi321

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for wimi321/claude-code-keybindings-customizer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Keybindings Customizer" (wimi321/claude-code-keybindings-customizer) from ClawHub.
Skill page: https://clawhub.ai/wimi321/claude-code-keybindings-customizer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install claude-code-keybindings-customizer

ClawHub CLI

Package manager switcher

npx clawhub@latest install claude-code-keybindings-customizer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The name/description and SKILL.md consistently describe safely editing Claude Code keybindings (~/.claude/keybindings.json). However, the registry metadata lists no required config paths even though the instructions explicitly reference a specific user config file; this is a minor inconsistency (the skill will need read/write access to that file in practice).
✓
Instruction Scope
SKILL.md instructions are narrowly scoped: read the existing keybindings file, merge changes, preserve schema/docs, validate reserved shortcuts, and report conflicts. There are no instructions to read other unrelated files, call external endpoints, or collect extra data. The instructions are high-level (merge/validate) so runtime behavior depends on the agent implementation; the user should require a preview/diff before writes.
✓
Install Mechanism
Instruction-only skill with no install spec and no code files present. This minimizes disk/write risk and there are no downloaded/installed components to review.
ℹ
Credentials
The skill requests no environment variables or credentials, which is appropriate. It does, however, operate on a user config file in the home directory; the metadata does not declare this config path as required. This is reasonable for the stated purpose but should be explicit so users know what will be accessed.
✓
Persistence & Privilege
always:false and no special privileges requested. The skill can be invoked autonomously by the agent (platform default), which is expected; combine this with the prior note and require explicit user confirmation before modifying files.
Assessment
This skill appears to do what it claims (read and merge changes to ~/.claude/keybindings.json) and does not request unrelated credentials or installs — so it is internally coherent. Before installing or running it, consider these precautions: (1) Confirm provenance — the source is 'unknown' in the registry; prefer skills from known repositories. (2) Require the skill to show a preview/diff of proposed edits and ask for explicit confirmation before writing. (3) Back up ~/.claude/keybindings.json (e.g., ~/.claude/keybindings.json.bak) before allowing writes. (4) Verify the skill only touches that specific file and does not attempt to read other home-directory files. (5) If you enable autonomous invocation for the agent, be aware it could modify the file without prompting — keep autonomous use disabled unless you trust the skill. If the publisher can provide a declared config path (the metadata currently omits it) and an auditable implementation, that would increase confidence further.

Like a lobster shell, security has layers — review code before you run it.

claude-codevk975ncqjdnxfz4dp2jpqefs52n840n55extractedvk975ncqjdnxfz4dp2jpqefs52n840n55latestvk975ncqjdnxfz4dp2jpqefs52n840n55
107downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0
@wimi321
claude-codeextractedlatest
Download

Keybindings Customizer

Use this skill for shortcut rebinding, unbinding, or chord creation.

Workflow

  1. Read the current keybindings file first.
  2. Merge changes instead of replacing the entire file.
  3. Keep schema and docs fields intact.
  4. Validate against reserved and non-rebindable shortcuts.
  5. Explain any conflicts or terminal-level limitations.

Guardrails

  • Never overwrite the full file blindly.
  • Preserve unrelated existing bindings.
  • Flag OS or terminal-reserved shortcuts before saving.

Example Requests

  • Rebind the external editor shortcut.
  • Add a chord to toggle todos without overwriting my keybindings file.

Inputs

  • Requested key changes
  • Existing keybindings file
  • OS or terminal constraints

Outputs

  • Merged keybinding config
  • Conflict explanations

Success Criteria

  • The file was merged, not clobbered.
  • Reserved shortcuts were handled correctly.
  • Schema and docs fields remain intact.

Non-Goals

  • Whole-file replacement for a small binding change

Source Provenance

Derived from src/skills/bundled/keybindings.ts.

Comments

Loading comments...