AGENT SKILL

skillshare

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, import MCP settings, manage targets, audit skills, recover backups, or troubleshoot Skillshare configuration and sync. Covers global and project modes, noninteractive automation, and guidance for the terminal UI.

License 许可
MIT
所属仓库
ham-zax/webharness
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

name
skillshare
metadata
{ "version": "v0.25.5" }
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, import MCP settings, manage targets, 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]

02 资源文件 16

03 SKILL.md 正文

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.
  • 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 for scope, version checks, and agent setup.
  • MCP uses its own receiving targets and source definitions. Read 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 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 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 and 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.

Install, update, and sync skills

skillshare install user/repo -s pdf,commit
skillshare install user/repo --track -b develop --all
skillshare sync
skillshare check --json
skillshare update my-skill
skillshare sync

For project setup, use init -p, then install -p and sync -p. Rehydrate configured remote dependencies with install without a source. For full flag details and agents, read install.md and sync.md.

To use a local skills checkout in place, run skillshare link <path> --enable, then sync; skillshare unlink <name> removes only the link. Read TROUBLESHOOTING.md for how such links are followed.

Disable or remove

skillshare disable 'draft-*' --dry-run
skillshare disable 'draft-*'
skillshare enable 'draft-*'
skillshare uninstall my-skill
skillshare sync
skillshare trash restore my-skill
skillshare sync

Run the requested operation, not this entire example sequence. Quote glob patterns so Skillshare receives them unchanged. Disabling uses ignore rules; uninstall uses trash.

Move skills into folders

skillshare move my-skill frontend --dry-run
skillshare move my-skill other-skill frontend
skillshare sync

Use move instead of mv for installed skills: it keeps their install records, so nothing is downloaded again. It does not sync; run sync afterwards. Read install.md for refusals and project mode.

MCP settings

skillshare mcp import --from claude --json
skillshare mcp add docs --url https://example.com/mcp --target claude --no-tui
skillshare sync mcp --dry-run --json
skillshare sync mcp

--target is singular and repeatable. A preview does not apply changes. For revisions, editing, import conflicts, credentials, backups, and human-operated TUI commands, read mcp.md.

Complete plugins

skillshare plugin list --json
skillshare plugin add ./my-plugin --target claude --dry-run --json
skillshare plugin disable demo --target claude --no-tui
skillshare sync plugins demo --dry-run --json

Run only the requested operation. add installs a whole native package; import adopts an existing installation. Plugin enable/disable saves sync selection only; the next sync plugins installs or removes the managed target. It is excluded from sync --all. Inspect targetDefinitions for supported operations and scopes; format discovery alone does not mean installation is supported. Read plugins.md before applying changes.

Skill hubs

skillshare hub add https://example.com/hub.json          # Save a hub source
skillshare hub add https://example.com/hub.json --label my-hub  # With custom label
skillshare hub add git@ghe.corp.com:team/skills.git --label ghe  # SSH/private/GHE hub source
skillshare hub list                                      # List saved hubs
skillshare hub default my-hub                            # Set default hub
skillshare hub remove my-hub                             # Remove a hub
skillshare hub index --source ~/.config/skillshare/skills/ --full --audit  # Build hub index

The active follow_source_links setting also applies to hub index (including --source), built-in dashboard search, and Hub draft candidates.

References

Read the matching file for command flags, examples, and limitations. Avoid loading all references for a single task.

Topic File
Native agents, selection, ignore rules, and recovery native-agents.md
MCP configuration, imports, TUI, and recovery mcp.md
Native hooks, code bindings, scopes and recovery hooks.md
Complete plugins, native lifecycle, and sync selection plugins.md
Init flags init.md
Sync/collect/commit/push/pull sync.md
Install/update/uninstall/move/new install.md
Status/diff/list/search/check status.md
Security audit audit.md
Trash trash.md
Operation log log.md
Targets targets.md
Extras (rules/commands/prompts) extras.md
Backup/restore backup.md
Troubleshooting TROUBLESHOOTING.md

04 同仓库更多 Skills

ham-zax
ham-zax/webharness

x-content

Create, rewrite, critique, select formats for, discover opportunities for, and learn from X/Twitter content and X Articles for a technical AI-native developer/builder account. Use when turning ideas, source posts, releases, benchmarks, results, conversations, authenticated For You or creator-watch opportunities, or project evidence into an Original, Quote, Thread, Reply, or Article; reviewing article titles/outlines/visual briefs/launch hooks; improving drafts; choosing additive contributions from live X context; or learning from own-account outcomes. Own content intelligence only; compose with agent-browser for live X state and Growth OS for discovery provenance, approvals, measurement, and publication.

★ 0
ham-zax
ham-zax/webharness

writing-plans

Create detailed implementation plans for multi-step software work before editing code. Use when requirements or a specification must become concrete file-level tasks, interfaces, acceptance criteria, risks, rollout, or explicitly required validation. Default to no test creation, test modification, test execution, TDD, regression-test, or coverage work unless the user, authoritative specification, or mandatory repository policy explicitly requires testing.

★ 0
ham-zax
ham-zax/webharness

systematic-debugging

Root-cause debugging for concrete technical failures including bugs, failing builds or tests, integration issues, performance regressions, and unexpected behavior. Use before proposing or implementing a repair when diagnosis is required. Reproduce the symptom, trace the responsible owner, maintain one leading causal hypothesis, and falsify it with the smallest direct evidence. Compose with Causal Coding for source mutation; testing is opt-in and requires independent authorization.

★ 0
ham-zax
ham-zax/webharness

skill-creator

Guide for creating and updating high-quality skills by translating workflows, conventions, and reusable processes into well-structured skills. Includes context, use case examples and spec for skills. Use this skill whenever a user asks to create, update, edit, improve, package, or troubleshoot a skill, and also for conversational questions about skills in ChatGPT (e.g., "What are skills?", "What can I use skills for?", "What are the best skill use cases for me?", "Where can I find my skills?").

★ 0
ham-zax
ham-zax/webharness

reflexion

Self-refinement, multi-perspective critique, verification, and durable lesson curation adapted from NeoLabHQ Reflexion. Use when the user asks to reflect, self-review, critique, double-check, verify and improve prior work, run a rigorous review, memorize lessons, or says "then reflect" after a coding, analysis, or writing task. Supports repository-aware evidence gathering and works without subagents or Claude hooks.

★ 0
ham-zax
ham-zax/webharness

ponytail

Enforce Ponytail's lazy-senior-developer approach for coding, fixing, refactoring, design, dependency choices, and explicit Ponytail modes such as review, audit, debt, gain, and help. Prefer YAGNI, existing code, standard library, native platform features, existing dependencies, low reader load, and the smallest correct diff. For source mutation, keep Causal Coding authoritative for scope, testing authorization, verification cadence, and stopping. On connected WSL/Linux targets, compose with MCP Harness Router and use `wsl-web-harness` for authoritative repository work.

★ 0