/skillshare

name: skillshare
description: |
  Manage skills, agents, extras, hooks, plugins, and MCP connection settings with the Skillshare CLI.
  Use when the user asks to configure or run Skillshare, install or sync resources
  across AI tools, manage shared memory notes, review a session for lessons or dream over saved memories,
  import MCP settings, manage targets and project folders, audit skills, recover backups,
  or troubleshoot Skillshare configuration and sync. Covers global and project modes,
  noninteractive automation, and guidance for the terminal UI.
argument-hint: "[command] [target] [--json] [--dry-run] [-p|-g]"
metadata:
  version: v0.30.5

Skillshare CLI

Use Skillshare to maintain a source and distribute resources to configured targets. Read only the reference relevant to the requested operation; the routing table is below. Check `skillshare <command> --help` if the installed version differs from these examples.

Scope and resource selection

• Global config: `~/.config/skillshare/config.yaml`. Project config: `.skillshare/config.yaml`

or `skillshare/config.yaml`; hidden wins when both exist. Use `-g` or `-p` explicitly when location matters instead of relying on auto-detection.

• Skills are directories containing `SKILL.md`; agents are single Markdown files.

Source paths can be customized. Use the configured sources instead of assuming defaults.

• Tracked `skills/<known-agent>/<skill-path>/SKILL.md` copies form one logical skill

per repository/prefix/suffix. Merge/copy select the exact agent variant (including aliases and account `agent:` identity). Recognition requires the same suffix under two distinct canonical agents. Compatible targets sharing a folder select the union of their agent identities; a universal-only target does not infer an agent. Status counts logical skills and physical variants; lists and sync operations retain physical names. Explicit targets/overrides and physical filters still apply. Whole-directory symlink mode exposes all variants. See [sync.md](references/sync.md).

• Use native agents targets for agents. Use extras for arbitrary file resources or when

flattening/content transformation is required; `extension:` works only on extras targets.

• Shared memory notes live in the `memory` extra. Use `extras memory` to manage Markdown

notes and reading guidance; nested paths such as `wiki/architecture.md` are supported. Read [extras.md](references/extras.md) for scope, version checks, and agent setup. For a session retrospective or Dreaming across saved notes, read [memory-review.md](references/memory-review.md). The host agent performs the review; Skillshare never launches or schedules an agent.

• MCP uses its own receiving targets and source definitions. Read [mcp.md](references/mcp.md)

before editing MCP settings or importing native configurations. Its Agent notes cover what is specific to Claude Code, Codex, OpenCode and Pi: scopes and files, names and credentials they refuse, Pi's built-in MCP and `piOptions`, OMP's native MCP and preserved enable/disable lists, the portable `tools` policy, upgrading Pi settings from 0.22, turning a global server off in one project, `mcp.projects` for many folders from one config, and `mcp serve` for Agents that cannot reach the synced skill folders.

• Plugins keep their native components together. Read [plugins.md](references/plugins.md)

for installation, import, sync selection, updates, and native compatibility limits across Claude, Codex, Cursor, Antigravity, Pi, OMP, and OpenCode, including Pi packages from pi.dev and OMP marketplace plugins and standalone extension selection.

• Hooks preserve each Agent's native event map or extension/plugin code. Read

[hooks.md](references/hooks.md) before import, synchronization or recovery.

Execution rules

1. **Choose noninteractive inputs.** Supply names and selection flags supported by the specific command. Use `--no-tui` for plain output or `--json` where supported. Do not add `--force` simply to avoid a prompt: it can overwrite conflicts or override audits. 2. **Keep previews separate from writes.** Use `--dry-run` where supported. After changing skills or agents, sync the intended resource and scope. MCP and hooks mutations save source only unless `--sync` is supplied; `sync --all` also includes extras, MCP and hooks, but excludes plugins. 3. **Inspect audit blocks.** Review findings before choosing an override. `install --json` permits overwrite and selects all when no skill/agent filter is given, but retains the audit gate; it is not merely an output format. Read [install.md](references/install.md) and [audit.md](references/audit.md) before using it for automation. 4. **Use the matching recovery mechanism.** Uninstalled skills go to trash; native MCP entries use MCP backups. Do not substitute filesystem deletion for CLI uninstall. 5. **Keep credentials out of MCP definitions.** Use `{fromEnv: VARIABLE}` references. Managing settings does not require resolving secrets, copying OAuth credentials, starting servers, or probing their tools. 6. **Respect operation scope.** Local configuration work does not imply permission to commit, push, or publish. Run those commands when included in the user's request.

Common workflows

Inspect and diagnose

skillshare status --json
skillshare list --json
skillshare diff --json
skillshare doctor --json
skillshare mcp --json

`doctor` exits 1 when it finds errors. Audit uses `--format json`; JSON flags and TUI availability vary by command. See the relevant reference rather than assuming parity.

For automatic release checks and notices, use `skillshare updates off` / `on`. `skillshare updates check` explicitly checks the CLI version even when automatic checks are off; see [status.md](references/status.md#updates) for the shared preference and environment override. Installed resource-source checks are separate.

Track a