mulmoterminal-keys SKILL.md skillA

mulmoterminal-keys from receptron/mulmoterminal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add receptron/mulmoterminal/mulmoterminal-keys@git:20261103.0eab616

Pins git:20261103.0eab616 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

receptron/mulmoterminal

Path

server/skills/mulmoterminal-keys/SKILL.md

Versions recorded

21

Latest version

git:20261103.0eab616, committed Nov 3, 2026

First version recorded

Aug 28, 2026

Size

42,938 bytes

Repository stars

261

License

MIT

Bind keyboard shortcuts and fix keyboard/clipboard behaviour in MulmoTerminal. **Writes `keymap`** — Settings → Keyboard shortcuts also sets or clears ONE action's key by pressing it (single keystrokes; a two-key sequence and the `send` list are still written here), and its Recommended keys block adds this platform's starter set. **Explains `copyOnSelect`, `questionPaneEnabled`, `terminalSubmit` and `tmuxPrefix`**, which have their own Settings controls under Terminal keys — point the user at…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Keyboard, shortcuts and clipboard

These settings all live in **`~/.mulmoterminal/config.json`**, and each write is a **partial
`POST /api/config` merge** — write only the key you are changing, so the user's other settings
survive.

**"Partial" means per TOP-LEVEL key, and `keymap` is replaced WHOLE.** The merge is
`body[key] !== undefined ? sanitize(body[key]) : current` (`server/config/app-config.ts`), so
posting

```json
{ "keymap": { "send": [ … ] } }
```

does not add a `send` to the keymap — it **makes that the entire keymap**, deleting every action
binding the user had. Nothing warns, and the reply is a success.

So a keymap write always sends the **complete** keymap: what step 1 read, plus the change. Read it,
merge in memory, post the whole thing. An entry naming an action this version does not know (a typo like
`zoom-toogle`, or a newer release's action) is kept in the file whatever you post, including when you leave
it out (`GET /api/config` does not return it) — to remove one, edit `config.json` directly. Every `keymap` example below shows one setting on its own for
readability — none of them is a body to post as-is unless the user genuinely has nothing else bound.
…

Read the whole file at its exact version.

How to install

mdr add receptron/mulmoterminal/mulmoterminal-keys@sha256:25898c1cdf419c30

[![mdr](https://markdownregistry.com/badge/art_fabc2rwpwqijhkyo.svg)](https://markdownregistry.com/a/art_fabc2rwpwqijhkyo)

Versions

The registry has recorded 21 versions of this file, between Aug 28, 2026 and Nov 3, 2026, about one every 3 days.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_fabc2rwpwqijhkyo
GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/mulmoterminal-keys
GET https://markdownregistry.com/api/v1/blob/25898c1cdf419c30d17ab4921ec8ad755a5c60f167ab9cf4453e154e0445b41f

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from receptron/mulmoterminal

Every file in receptron/mulmoterminal

Browse by kind, by grade A, or by owner.