Nethür skills registry & MCP

Nethür ships version-matched agent skills, updates them from the app, and exposes read-only guides through the CLI.

Nethür ships skills that agents load into their skill directories. The app installs them with the default agent setup; you do not need a public registry or a GitHub account. Each skill is a short discovery stub that tells the agent when to engage Nethür and how to load the full, version-matched guide from the running CLI. Command flags live in the binary so they cannot drift from the app version.

Bundled Nethür skills

SkillUse it for
nethur-cliWorktrees, terminals, files, automations, embedded browser.
orchestrationMulti-agent Runs, tasks, supervised workers, messages, gates.
computer-useDesktop apps via accessibility trees and safe UI actions.
nethur-linearLinear ticket read/write through nethur linear.
nethur-emulatoriOS Simulator control.
nethur-emulator-androidAndroid emulator/device via adb.
nethur-per-workspace-envPer-workspace environment recipes (nethur.yaml).

Hybrid stubs vs the live guide

After Nethür installs the skill, agents see a short stub that says:

  1. Resolve the CLI executable for this session (NETHUR_CLI_COMMAND, nethur-dev, Linux nethur-ide, else nethur).
  2. Load the full guide: nethur skills get <topic> (or --full for the long guide).
  3. Prefer --json and do not invent flags from memory.
bash
nethur skills list
nethur skills get nethur-cli
nethur skills get orchestration --references
nethur skills get orchestration --reference recovery-and-cleanup
nethur skills get orchestration --full
nethur skills get nethur-linear --json

A guide's action gates name conditional references. --reference <name> prints one of them alone, so an agent pays for the kernel plus that document instead of the whole package; --references lists the names. The name may be bare (recovery-and-cleanup) or spelled as the guide writes it (references/recovery-and-cleanup.md). --full still prints the kernel plus every reference.

Add --json when an agent needs deterministic output for automation. skills show is an alias for skills get.

Keep skills up to date

When Nethür ships a newer skill package than the one installed globally, the app can:

  • Show an update available nudge for skills Nethür installed (and Needs attention when a copy is out of date somewhere the updater cannot safely rewrite).
  • Open Update skills — list of placements and skip reasons, with a checkbox per skill. Nethür's own skills start ticked; a same-named skill installed from somewhere else is marked Not from Nethür and starts unticked. The selected skills are reinstalled in the background from the set bundled with the running Nethür build (no embedded terminal), so the guide always matches the app version.
  • Keep the run in the background: closing the dialog does not cancel it. A status-bar segment shows progress (spinner while running, brief success check, persistent failure until you act). Click the segment to reopen the dialog.
  • Surface freshness on Settings → Agents for installed skills (global install rail), including Details when a row needs review.

Manual equivalent:

bash
nethur skills update --all

On headless hosts (SSH, containers, CI, nethur serve) with no Settings UI, use the local CLI wrappers — they use the bundled skill set, add non-interactive flags, and do not need a running Nethür runtime:

bash
nethur skills install                                      # list installable names
nethur skills install --skill nethur-cli --skill orchestration
nethur skills install --skill nethur-cli --agent claude-code,codex
nethur skills install --all --dry-run
nethur skills update --all
nethur skills update --skill nethur-cli --dry-run
  • Default scope is global (--global); pass --local for the current project only.
  • install copies the bundled skills to the agents Nethür detects on the host (plus the shared .agents/skills directory). Use --agent <name>[,<name>…] or --agent universal to override; if no agent is detected, --agent is required.
  • update refreshes the installed copies from the same bundled set. With no agent detected it targets only .agents/skills instead of refusing.
  • --dry-run prints the resolved command; --json is only valid with listing / --dry-run.

Prefer the in-app updater when Nethür offers it so the same global placements the app scanned get rewritten. Rows marked Skipped explain why that skill cannot be updated automatically (for example a read-only folder or a link pointing outside Nethür's skill folders) — fix the placement, then re-check.

Install and delete from the Skills page

When an in-app install asks for a workspace target, search the picker by workspace name or by kind (worktree / folder). The agent picker separates directories Nethür always includes from additional agent directories you can select, so you can review the exact installation targets before continuing.

To remove a scanned skill, open its actions menu and choose Delete…. For several skills, open the page's More actions menu, choose Delete skills…, and select the eligible results. Nethür explains why a copy cannot be deleted—for example because it is bundled, plugin-managed, read-only, or outside a removable skill folder—before you confirm. This is separate from Manage installs, which manages copies installed from shared links.

Share private skills between hosts

Open Skills → Share skills to publish one skill or a bundle behind one unlisted, revocable link. Publishing requires your Nethür account. Review the included files, scripts, executables, digest, and optional release notes before you publish; each published version is immutable, so later local edits do not silently change what recipients install.

Anyone with an active link can inspect and install the shared skills without signing in, so treat the link like a credential. A recipient reviews the exact version, chooses all or a subset of its skills, then selects global or workspace scope on this computer, a paired Nethür runtime, WSL, or an SSH host. Existing modified skills default to Keep local. Use Skills → Manage installs to update, roll back, or remove copies Nethür installed, and Settings → Share Skills to copy or revoke your active links. Revoking a link blocks future access but does not remove copies already installed.

Agents can publish an explicitly named set from the CLI after you enable the separate, default-off Settings → Share Skills → Allow agents and the Nethür CLI to publish skill links permission:

bash
nethur skills installed --json
nethur skills share --skill frontend --skill testing --bundle-name "Team Toolkit" --json

skills installed returns safe selectors without exposing local paths. skills share accepts exact discovery IDs or unambiguous names; it does not accept arbitrary paths or --all.

nethur-cli

bash
nethur skills install --skill nethur-cli

After install, load the version-matched command guide with nethur skills get nethur-cli. See Nethür CLI.

orchestration

bash
nethur skills install --skill orchestration

Use this when an agent should coordinate other agents through Runs, tasks, supervised workers, and decision gates. See Orchestration. Always load nethur skills get orchestration --full before mutating orchestration state — the legacy orchestration run command is retired.

computer-use

bash
nethur skills install --skill computer-use

Use this when an agent needs to inspect and operate local desktop app windows. See Computer use.

nethur-linear

bash
nethur skills install --skill nethur-linear

Agents should load nethur skills get nethur-linear before mutating tickets. Covers issue --full, save-issue, list-issues, relations, completion attach+comment flow, and untrusted-ticket rules. Existing linear-tickets installs still resolve. See CLI reference → Linear.

nethur-emulator

bash
nethur skills install --skill nethur-emulator

Use this when an agent should control an iOS Simulator from inside Nethür through nethur emulator commands.

nethur-emulator-android

bash
nethur skills install --skill nethur-emulator-android

Use for adb-connected Android AVDs/devices: list/boot, tap/swipe/type, hardware buttons, install/launch, permissions, accessibility tree, logcat. Load details with nethur skills get nethur-emulator-android.

nethur-per-workspace-env

bash
nethur skills install --skill nethur-per-workspace-env

Use when setting up or debugging per-workspace environment recipes in nethur.yaml. See Ways to run Nethür.

Discovery sources

Nethür's skill UI scans installed skill homes for Claude, Codex, Agent Skills, and OMP (~/.omp/agent/skills), so skills placed there show up without a manual symlink.

Add your own skills

Custom skills can be placed in the agent's skill directory; Nethür indexes the standard skill homes. Company-specific skills can be shared by an administrator instead of being pulled from a public registry.

MCP servers

Model Context Protocol (MCP) servers expose external tools to compatible agents. Register MCP endpoints under Settings → Integrations → MCP; those tools appear inside agent CLIs that support MCP.