SkillshareCAUTION
📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing.
Overview
📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing.
538d7bd06c35OBSERVED · 2026-10-18Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| claude-code | mentioned | |
| claude-desktop | mentioned | |
| codex | mentioned | |
| copilot | mentioned | |
| cursor | mentioned | |
| gemini-cli | mentioned | |
| windsurf | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
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, 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.25.13
---
# 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](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
```bash
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
```bash
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](references/install.md) and [sync.md](references/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](references/TROUBLESHOOTING.md) for how such links are followed.
### Disable or remove
```bash
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 patterTrust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (1 observation(s))
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (7)
.agents/skills/skillshare-changelog
.agents/skills/skillshare-cli-e2e-test
.agents/skills/skillshare-code-review
.agents/skills/skillshare-devcontainer
.agents/skills/skillshare-implement-feature
- `prompt-injection-5`: generic disclosure restrictions using `don't` or `do not` followed by `tell the user` are HIGH in all file types. These can be advice or concealment; no framework, repository,
| `options` | `{<client>: {field: value}}`: other Agents' native per-server fields written as given, e.g. `codex: {default_tools_approval_mode: approve}`, `claude: {timeout: 600000}`. Values: scalars,Gates applied: no_behavioural_pass.
538d7bd06c35full audit observations/trust-audit/skill/runkids__skillshare.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-18 | 538d7bd06c35 | CAUTION | B | 89 | first audit |
Questions
What does the Skillshare skill do?
📚 Sync skills, agents, MCP, plugins to all AI CLI tools with one command and simplify team sharing.
Is Skillshare safe to install?
With care. The audit graded it B (89/100) and found 7 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Skillshare access on my machine?
The audit observed that it reaches the network and reads or writes files. Each of those is consistent with what it says it does. Secrets in the source: none found.
Which assistants does Skillshare work with?
Its documentation mentions claude-code, claude-desktop, codex, copilot, cursor, gemini-cli and windsurf. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (538d7bd06c35), read on 2026-10-18. The repository is watched, and a new audit runs when it changes — this is the first audit.
Add this badge to your README
Shows this page's audit result and links back to it. It updates when the audit does.
[](https://modelsatlas.com/skills/runkids/skillshare/)
Not your listing, or something out of date? Claim or update your listing.