Skip to content

Guide · Agent skill

How to use the Mubu Live Bridge CLI agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

cli-anything-mubu is an agent skill that teaches an AI agent how to use a command-line tool connected to the Mubu outlining app on your own computer. After reading this guide, you will know how to install the skill, how to ask for things in plain language, which commands the agent runs, and which safety rules protect your live notes.

Mubu Live Bridge CLIHKUDS/CLI-Anything · Apache-2.0

Quick start

  1. 1Check prerequisites. Confirm Python 3.10 or newer is installed and that the Mubu desktop app is open with an active session on this computer.
  2. 2Install the skill. Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder, or upload it under Settings → Capabilities → Skills in the Claude apps.
  3. 3Install the CLI. From the agent-harness source tree, run pip install -e . so the cli-anything-mubu command is available.
  4. 4Set the daily folder. Optionally set MUBU_DAILY_FOLDER so daily helpers work without arguments.
  5. 5Ask a read-only question. Ask the agent to find your daily note or search your notes, so it uses discover and inspect commands.
  6. 6Preview an edit. Ask for a change, check the dry-run payload, and only run it with --execute once it looks right.

What is an agent skill and what does this one do?

An agent skill is a folder containing a SKILL.md file that gives an AI agent instructions for a specific task. This skill does not add a new app to your computer. It teaches the agent how to run the cli-anything-mubu command-line tool against your local Mubu data.

With the skill installed, the agent can list your folders and documents, find your current daily note, search outline text, and inspect the node structure of a document. It can also change live Mubu content, such as adding, editing or deleting outline nodes. The tool is designed to preview those changes first and apply them only when told to.

  • Discover: list folders, documents, recent documents and the current daily document
  • Inspect: show a document tree, search note text, list live nodes with node ids
  • Mutate: create a child node, update node text or delete a node, dry-run by default
  • Session: save a current document or node so later commands reuse it

Install the cli-anything-mubu skill

You can add the skill in one of three ways. Download the ZIP from this page and unzip it so the skill folder containing SKILL.md sits in your personal skills folder at ~/.claude/skills/. Or place it in a project's .claude/skills/ folder if you want the skill limited to one project. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills.

The skill only teaches the agent. The command-line tool itself is packaged from the agent-harness source tree, and the SKILL.md file gives this install command from that tree.

  • Requires Python 3.10 or newer
  • Personal install: unzip into ~/.claude/skills/
  • Project install: unzip into the project's .claude/skills/ folder
  • Claude apps: Settings → Capabilities → Skills, then upload the ZIP
pip install -e .

Set up Mubu and the CLI before first use

The tool reads local Mubu data and talks to the live Mubu API, so the desktop app must be ready on the same machine. The source lists these prerequisites: an active Mubu desktop session on this machine, and local Mubu profile data available to the CLI.

If you want to use the no-argument daily helpers, set the MUBU_DAILY_FOLDER environment variable. Otherwise pass a daily-folder reference explicitly in each command. The CLI can run as a single command or as an interactive session; without a subcommand, it starts a REPL.

  • Python 3.10+
  • Mubu desktop app open with an active session on this computer
  • Local Mubu profile data accessible to the CLI
  • Optional: MUBU_DAILY_FOLDER set for no-argument daily helpers
cli-anything-mubu python -m cli_anything.mubu

Ask for things in plain language

You do not need to type commands yourself. Ask the agent for a result and it should choose the discover or inspect commands first. These example requests show the kind of task the skill covers. The source does not list fixed trigger phrases, so describe what you want in your own words.

Good requests name the thing you care about: a folder, a document, a daily note or a piece of text. For example, ask it to find today's daily note, search your notes for a word, or show the structure of one document before any change is made.

  • Find my current daily note and summarise the open items in it
  • Search my Mubu notes for the phrase project timeline
  • List the documents in my Work folder
  • Show me the outline structure of the document called Meeting notes
  • Find the node that says Budget and show its node id

Run the commands that the agent uses

The agent typically follows a fixed order: discover, then inspect, then mutate. Commands print output that an agent can parse when you add --json. You can run the same commands yourself to check what the agent sees.

Resolve the current daily note from an explicit folder reference with the daily-current command. Inspect live nodes with daily-nodes and a --query anchor, then save the document with session use-doc before any mutate command.

  • discover daily-current '<daily-folder-ref>' --json resolves today's document
  • inspect daily-nodes '<daily-folder-ref>' --query '<anchor>' --json lists live nodes
  • session use-doc '<doc_path>' stores the document as current context
  • session status --json recovers saved context
cli-anything-mubu --json discover daily-current '<daily-folder-ref>'

Preview an edit before applying it

Mutation commands are dry-run by default. The command builds the outgoing payload and shows it to you, but nothing changes in the live document until you add --execute. Inspect the payload first, then decide whether to run it again with --execute.

Prefer --node-id and --parent-node-id over matching text, because text matching can hit the wrong node. Always verify the result after a live change. The source also notes that even a same-text update can advance document version history.

  • create-child, delete-node and update-text are the mutate commands
  • Dry-run is the default; --execute applies the change
  • delete-node removes the full targeted subtree, not only one line
  • Check the document after execution to confirm the postcondition
cli-anything-mubu mutate update-text '<doc-ref>' --node-id <node-id> --text 'new text' --json

Safety notes: scripts and network access

This skill runs scripts and uses the network. The CLI works with local profile data and sends live changes to the Mubu API when you execute a mutation. Treat it as a tool that can change your real notes, not as a read-only viewer.

Keep these rules in mind: use discover and inspect for reading, use --json when an agent parses output, and do not run unattended bulk edits on important documents. Use a test document for your first mutation.

  • Only run mutate commands on documents you can afford to change
  • Never use delete-node on a parent node unless you intend to remove everything under it
  • Read the package TEST.md and README.md for stricter operational detail, as the SKILL.md suggests

What people use it for

  • Find today's daily note and pull out the lines you wrote there
  • Search across your latest Mubu backups for a phrase you half remember
  • Check the outline structure of a long document before reorganising it
  • Update one node's text in a document you have already reviewed, using its node id
  • Set up a repeatable daily-note routine in a scripted workflow with dry-run checks

Frequently asked questions

How do I install the cli-anything-mubu skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder for one project. You can also upload the ZIP in the Claude apps under Settings → Capabilities → Skills. The CLI itself is installed from the agent-harness source tree with pip install -e .

What do I need to run cli-anything-mubu?

You need Python 3.10 or newer, an active Mubu desktop session on the same machine, and local Mubu profile data that the CLI can read. Setting MUBU_DAILY_FOLDER is optional and only needed for no-argument daily helpers.

Is cli-anything-mubu free and what is its licence?

The item is listed under the Apache-2.0 licence. Check the licence file in the source repository for the full terms before you use or redistribute it.

Can the agent change my Mubu notes?

Yes, through create-child, update-text and delete-node. These commands are dry-run by default and only apply a change when you add --execute. delete-node removes the full targeted subtree, so review the payload carefully.

Why does the command not work even though it is installed?

The tool depends on a running Mubu desktop session and local profile data on the same machine. Open Mubu, confirm you are signed in, and check that Python is 3.10 or newer. Also check that the daily folder reference is passed or MUBU_DAILY_FOLDER is set.

Is there an official Mubu API alternative, and how does this compare?

This is a community-built bridge that reads local data rather than a documented public API, so it is not an official Mubu integration. If you need a supported integration for a team, look at the options Mubu itself documents rather than relying on this bridge.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you are a Mubu user who wants an AI agent to browse, search and read your notes, or a developer who wants to automate outline edits with dry-run checks. Pick something else if you need an official, supported Mubu integration, or if you want unattended bulk edits to important documents, since delete-node and live edits can change real content.

Download the skill