Since 191bdec3 a dashboard sync keeps going after a skills target
fails, but the Sync row only described the happy path. It now says what
the page actually shows: failures as warnings with the run marked
partial, an error when every skills target fails, and an extras failure
that stops before MCP is written.
uninstall now fails a tracked repo whose git status cannot be read
unless --force, but the command page and built-in skill still described
only the uncommitted-changes check. The recent list, status, sync,
update and uninstall changes were also English-only, while this site
updates every locale alongside the English page.
status and list discarded the error from the uncommitted-changes check,
so a tracked repo whose git status could not be read was shown as
up-to-date. They now show it as unknown with a warning naming the repo
and error; status --json sets the existing status and message fields.
The commands still succeed, since they only report.
update discarded the error from the uncommitted-changes check, so a repo
whose git status could not be read was treated as clean and pulled over
whatever local edits it had. It now fails that repo with "failed to check
git status: <err>" unless --force, matching uninstall and the Web API.
Batch update counts these as failed instead of skipped and exits non-zero.
`sync extras` already exits non-zero and logs "partial" when a target
fails, but `sync --all` only printed a warning and exited 0, and its
--json path ignored extras errors entirely. The Web API always logged
"ok". Both now follow the CLI: `sync --all` exits non-zero on an extras
failure in text and JSON, global and project, without holding back MCP;
the Web API oplog records the error count with status "partial", or
"error" when every target that ran failed. The HTTP status stays 200.
The MCP guide still said an Agent's existing server always shows as a
conflict once added to the source; a matching one is now taken over on
sync. The Extras reference now says a single file's name follows its
file name until one is typed.
Refs #303
Refs #300
Pi and OMP read APPEND_SYSTEM.md next to their skills, and editing it
meant leaving the dashboard. A target page now shows extra file tabs:
built-in ones come from targets.yaml `files:` (APPEND_SYSTEM.md for pi
and omp), and users can add their own, including files in subfolders.
Paths stay inside the tool's folder; three tabs show and the rest move
to a menu. "Share with Extras" opens Add extra prefilled with the file's
folder and name, so the same file can be shared across tools.
A single-file extra's name now defaults to its file name without the
extension (APPEND_SYSTEM.md -> APPEND_SYSTEM) until the user types one,
and the hint suggests the file name, as the #300 reporter asked.
Refs #301
Refs #300
Importing a server from an Agent without ticking that Agent, then ticking
it later, left the Agent's entry unmanaged for good: the plan reported it
as unchanged, recorded no ownership, and so unticking the Agent had
nothing to remove. Nothing on the page said why, because the server's
name was now defined in the source.
Such an entry is now planned as adopt. Sync records it as managed without
rewriting the file, so the takeover is visible in the preview and happens
only when the user syncs. A server the person turned off in the Agent
itself is still never claimed.
Refs #303
sync now names two targets that write one folder with different filters,
but nothing told users searching for "sync keeps showing the same
changes" why it happens or how to fix it. The troubleshooting page covers
the symptom, the sync filter notes say shared folders need matching
filters, and the built-in skill points agents at the printed command.
When two targets sync skills into the same folder with different include
or exclude filters, each sync adds what one wants and prunes what the
other filters out, so the folder never settles and sync keeps showing the
same changes. The only hint was a vague overlap count.
sync, doctor and the dashboard's Sync page now name the targets and the
folder, and suggest turning skills off for all but one (universal when it
is among them) instead of removing a target. The Sync page offers the
existing stop-syncing dialog in place. Targets with identical filters are
not reported.
Pi keeps the first skill with a given name and warns, and Gemini, Amp and
others pick one by precedence, so telling users every skill "shows up
twice" was wrong for most tools. The notes and docs now say the tool finds
each skill twice, which holds whether it lists both or keeps one.
A single-file extra added from the dashboard with the shared source got
<extras dir>/<name> as its folder, so a second file in the same folder
needed the same name and was refused as a duplicate. Project mode had no
source setting at all, so it could never share a folder.
The add dialog now has a source folder field that defaults to the name,
and project extras accept a source relative to the project root, from the
dashboard and from `extras init -p --source`. Paths shown for single-file
extras also keep the folder's own separator, so Windows paths no longer
mix backslashes with a slash before the file name.
Refs #300
Covers `--skills`, `--no-skills` and `skills.enabled`, what each sync mode
does to the folder when skills go off, and the dashboard switch, so users
of a tool that reads another target's folder know how to avoid duplicate
skills.
Some tools only need skillshare for AGENTS.md, MCP or agents, while their
skills folder is managed elsewhere or shared through another target.
Syncing skills into those folders duplicated what the tool already reads,
so a target can now turn skills off (`target <name> --no-skills`, the
dashboard switch) and sync, diff, status and doctor skip its skills.
Switching off warns about the other tools that read the same folder.
The target list also gains tools that were missing, with colored vendor
logos where their licenses allow it, and zencoder/replit default paths
follow their current documentation.
The dashboard's target pages get the matching UI: universal is pinned as
the shared folder when adding a target, the add dialog lists what will be
written, and the AGENTS.md tab shows where the file comes from in one card
with an in-place switch between shared files.
tree/HEAD/ links now install from the default branch, but the install
page did not say so. The built-in skill reference and the translated
install and hub-index pages also lacked the pinned web URL behavior, so
agents and non-English readers could not learn how to pin a skill or a
hub entry to a tag or commit.
Refs #293
The single-file extras docs only showed AGENTS.md, which read as if that
was the only supported file. Lead with a generic example (Pi's
APPEND_SYSTEM.md), document extras init --file/--as and the full-path
list output, show how several extras can pick files from one shared
source folder in global mode, and describe which dashboard tab lists
which extras.
Refs #300
* feat(install): pin GitHub tree/blob URLs to their ref
Hub entries only carry a source URL, so a team hub had no way to pin a
third-party skill to a reviewed tag or commit. The parser already read
tree/<ref>/ and blob/<ref>/ URLs but discarded the ref, installing from
the default branch instead of the version the URL names.
Keep that ref as Source.Branch. An explicit --branch (CLI) or branch
(API body) still overrides it; the server handlers now only override
when a branch is given. Batch installs group by repo and ref so two
pinned versions of one repo get separate clones.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs(install): describe pinning hub sources to a tag or commit
Explain that a GitHub tree/<ref>/ source URL pins the install, in both
the hub index guide and the install reference.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat(install): pin GitLab/Bitbucket URLs and resolve refs containing "/"
Pinning should not depend on the host, so GitLab (-/tree/<ref>/) and
Bitbucket (src/<ref>/) web URLs now keep their ref too.
Taking the first path segment as the ref broke branch names containing
"/": tree/feature/x/skills/foo cloned branch "feature" and failed. When
the first segment is not a branch or tag on the remote, the longest
matching one is used instead. A ref the remote does not have fails
with a hint to use --branch, rather than silently installing the
default branch. A saved branch that covers more of the path (from
--branch or config) moves the subdir without asking the remote.
The grouped-install round-trip test pinned -/tree/main/ against a repo
on master; the ref used to be ignored, so its branch is now renamed.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* docs(install): cover GitLab, Bitbucket and "/" branches in URL pinning
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix(install): keep web URL refs correct on reinstall, --branch and grouping
Review of the slash-branch resolution found four gaps:
- A saved branch equal to the whole URL tail (tree/feature/x) did not
move the subdir back, so every reinstall or update looked for "x".
- An unrelated --branch with a slash-branch URL kept the parse-time
subdir (x/skills/foo) instead of the URL's real one.
- Grouped installs copy the source to a repo root; resolution then put
the subdir back and discovery looked under a doubled path. Grouping
also keyed on the unresolved first segment, so tree/feature/x and
tree/feature/y could share one clone. Web URLs with a ref now install
on their own, and resolution leaves a repo-root copy at its root.
- A skill named after the parse-time subdir kept that name once the
path turned out to be all ref (tree/feature/x named the skill "x").
The unknown-ref error now reads as a missing ref first, since a stale
ref (tree/master after a rename) is more common than a slash branch.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* fix(update): keep legacy installs on the default branch
Skills installed before URL refs were honoured got the default branch
and recorded no branch. Single-skill update re-parses the recorded
source, so it moved them to the URL's ref (or failed on a stale one,
with a hint to pass --branch, which update does not accept), while
update --all rebuilds from RepoURL and kept the default branch.
ApplyRecordedBranch treats an empty recorded branch as the remote
default and drops the URL's ref. It replaces the branch handling at
every site that reinstalls from recorded metadata: CLI and server
update for skills and agents, and tracked-repo rehydration.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* perf(search): share one clone across pinned hub skills from a repo
Any web URL with a path after its ref installed on its own, so a hub
listing many tree/<tag>/ skills from one repo cloned it once per skill.
groupByRepo now resolves each URL's ref before grouping, with a
RemoteRefs cache that lists each remote's refs once, and groups by
repo and resolved ref. Only refs containing "/" (whose subdir the
discovery match cannot re-derive) and refs that fail to resolve still
install alone. A resolved source is marked settled so the grouped
clone does not resolve it again, and ApplyRecordedBranch settles the
subdir from a recorded branch without asking the remote.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Willie <egg358358@gmail.com>
Every row repeated the same row of target chips, so recent backups were
hard to tell apart, and restoring meant picking a backup and then a
folder in a second dialog step.
Backups are now grouped by day with a compact row per backup. Opening a
row lists each folder with its file count and size and its own Restore
button; Copy path and Delete moved into that panel.
The page also says what it is doing: a list-shaped skeleton with
"Loading backups…" while the list is read, and a progress note while
Back up now runs, instead of a generic card skeleton and a lone button
spinner that read as a frozen page.
The dashboard screenshots predated the Projects page and showed codex at
its old path, and the guides for dashboard-only features (AGENTS.md
sharing, MCP, plugins, backups, hubs) had no pictures at all.
- Re-shoot the dashboard screenshots (docs and README copies) and add
ones for targets, extras, shared AGENTS.md, MCP, project MCP, plugins,
backups, hubs and project mode.
- Add diagrams for sharing AGENTS.md, MCP sync and migrating with
collect; fix codex's path in the getting-started diagram.
- Replace terminal screenshots with real output as text, and remove
images nothing referenced.
- Fix text that no longer matched the dashboard (project mode, hub
navigation, backup list output).
The dashboard lists a project's agent snapshots, but `backup --list -p`
and `backup --cleanup -p` were refused with "not supported in project
mode", so the CLI could only see the global folder. Both now work on
.skillshare/backups/ with -p.
Refs #299
Describe the new backup commands (--delete, backup files list/show/
restore), the reasons recorded with file backups, and the three sections
of the dashboard's Backup tab, and point the AGENTS.md backups section
there instead of telling readers to copy files back by hand.
Refs #299
Document local preserved counts, the junction replacement warning,
the Convert dialog without a picker, the folder-in-the-way hint and
update progress so the docs match the dashboard and CLI.
Refs #299
The docs said Windows always links with NTFS junctions and needs no admin
rights, which is only true for folders. Explain that single files need
Developer Mode for symlinks and otherwise sync as tracked copies, with the
warning line users will see and the folder-icon symptom from the issue.
Cover the per-target mode picker, the restore preview, changing a target's
file location, the single-column file tab with edit/preview, universal's
file list, and switching back to import. Also correct status and doctor
output that no longer matched the code, and the doctor "Link not
supported" advice, which pointed at Developer Mode although that check
creates a folder junction.
Refs #299
Codex and universal both write to ~/.agents/skills. Removing one of them
unlinked that folder, turning the other's synced skills into local
copies it no longer managed. Removal now leaves the folder alone while
another remaining target uses it, in the dashboard, the CLI, the TUI and
the dry-run preview.
Before v0.21.10 an upgrade that needed sudo wrote the built-in skill as
root, so every later skill upgrade failed with a bare "permission
denied". The error now adds the chown command for the skills source.
pi-mcp-adapter 3.0 no longer reads Pi's mcp.json, which it leaves to
Pi's upcoming built-in MCP support, and reads mcp-adapter.json in the
same folder instead. Servers synced for the adapter were landing in a
file it ignores, so they stopped loading.
Adapter servers now go to mcp-adapter.json in the global, project and
account folders; pi-mcp-extension still reads mcp.json. The next sync
removes the entries Skillshare had written to mcp.json and leaves the
user's own. If the user already renamed the file as Pi's warning
suggests, Skillshare keeps owning the entries that arrived unchanged
instead of reporting them as someone else's. Import and the unmanaged
scan read both files.
Refs #298
The guides still walked through the old list and detail page, so the
labels and steps no longer matched the dashboard.
Also fix two Korean bold labels that rendered with literal asterisks:
a closing ** after an ellipsis followed directly by a Hangul particle
is not a valid closing delimiter in CommonMark.
The shared AGENTS.md workflow is dashboard-only, so users had no written
reference for how shared files attach, what restore puts back, or where
drift backups go. Adds a how-to page in every locale, documents
single-file extras and the target `instructions` key, and brings the
translated extras collect section up to date with English.
When the binary lived in a root-owned directory, upgrade re-ran the whole
command under sudo. The built-in skill download, UI asset cache, and oplog
then landed in the user's home as root-owned files, and a later git pull
of the skills source failed with "unable to unlink old
'skillshare/SKILL.md': Permission denied".
The sudo child now only receives an internal --replace-binary=<version>
flag that downloads and swaps the binary. The parent waits for it and
does everything else as the invoking user. The needs-password hint shown
by the CLI and dashboard drops its sudo prefix, since a fully root
upgrade reproduces the same breakage.
Skills installed with --into land in folders, but the list and cards
views could only filter and group by source, so there was no way to
look at one folder at a time or see the folders side by side.
Add a Folder filter next to Targets and a Folder option to Group. A
skill's folder is its parent path, a tracked repo counts as one folder,
and skills at the source root group under "Root". The filter is hidden
when everything lives in one folder. Agents get the same controls.
Turning a whole folder or tracked repo off meant ticking every skill
in it, and the tree rows mixed table columns with indentation.
The tree view is now an explorer tree beside a detail pane. Click a
folder, repo or skill to select it; Cmd/Ctrl-click adds, Shift-click
selects a range. The pane turns the whole selection on or off with one
switch, sets its targets (tracked repos included), and lists each skill
with its own switch. Counts and disabled markers show on hover, and the
divider between the two sides can be dragged.
Enable/disable toasts now replace each other through a new toast `key`,
so quick on/off clicks no longer leave an outdated "Enabled" on screen.
Refs #295
Setting targets on a skill inside a tracked repo used to be refused,
because writing its SKILL.md leaves the clone dirty and `update` then
skips the repo (or `--force` throws the setting away).
Store those targets in the source's .metadata.json instead, keyed by
the skill's path, and apply them at discovery over the frontmatter.
The clone stays clean, `update` keeps working, and the setting survives
it. Uninstalling a repo or skill drops its entries.
Overrides are saved in the same lock section that writes them: every
API request reloads the store from disk, so saving after unlocking
could lose them, and saving outside the lock raced with other writers.
Refs #295
The pages still told users to inspect conflicts with git status and to
fix diverged tracked repos with git pull --rebase, but pull now merges
diverged history, resolves .metadata.json conflicts on its own, and
undoes the merge on any other conflict, so those steps no longer match
what happens. Also documents the Git Sync page fetch, the Pull count,
and the push_rejected API error in every translated locale.
The Targets row and the -p mode notes did not mention that a target
now lists and switches its MCP servers, nor that its Sync writes every
target's MCP files.
The Pi adapter settings moved from a hover icon to a line on the server
row, and Import from an Agent on a project's conflict now reads that
project's file, so the dashboard descriptions no longer matched.
Refs #289
Refs #290
A target declared with `agent` and `config_dir` is another config directory of a
built-in Agent, such as a second Claude account. Its skills and agents paths are
derived from the Agent's defaults at load time, so the config only records the
directory. The same target name works for MCP (written in the Agent's format into
the account's own file), for plugins (the Agent CLI runs with CLAUDE_CONFIG_DIR,
CODEX_HOME or PI_CODING_AGENT_DIR) and for `mcp import --from`. Removing such a
target warns when MCP config still names it instead of failing later at sync.
The dashboard gains an "another account" mode in the add-target dialog and lists
accounts next to the Agents on the MCP and plugin pages.
Refs #289
The MCP row on the ui page kept English button names in the translated pages,
next to labels that were already translated, and the English page itself said
Import where the button reads Import from a target. Three locales also lacked
the paragraph on upgrading without a terminal to ask for a password on.
The dashboard pages still described the project row without the Agent logos
and the Match the project action, the ui page did not mention where piOptions
is edited, and upgrade did not say the download now reports its progress.
Refs #289
OpenCode also loads opencode.json and opencode.jsonc from a project's
.opencode directory. Skillshare looked only at the project root, so a file
kept there was ignored and sync created a second one beside it. It is
resolved the way Kilo Code's .kilo already is: an existing file is reused
wherever it is, a new one goes to the root, and more than one is refused.
Refs #289
Also corrects a claim that every conflict offers an import action. One held
by another Skillshare config that still exists offers none, because only
that config can release the entry.
Refs #288
Adding a plugin forced at least one target, so keeping a plugin in
Skillshare for later meant installing it somewhere and then deselecting
every Agent by hand.
A package now records its source, so it stays managed with no Agent
bound. Agents are bound later from the same source, installing it as it
is then. Removing the last Agent keeps such a plugin; removing the
plugin itself drops it. In the terminal picker, confirming with nothing
selected records it, while Esc still cancels.
The plugin list also shows the installed version as a tag, and an
update check shows old -> new for plugins whose source has moved on.
The pages still said a disabled entry cannot target Claude Code, and that the
field is project mode only. Both are lifted: the entry is valid under an
mcp.projects root as well, and for Claude Code the switch goes to
~/.claude.json, where Claude Code keeps its per-project off list, leaving the
server definitions in that file alone. Only the global mcp.servers, where no
project is in scope, still refuses it.
The dashboard sentence was stale from an earlier change: the switch is its own
"Turn off a global server" button beside "Add server", shown in project mode
and on a project's MCP tab, not an option inside the add form.
All four locales follow, naming the buttons as the dashboard shows them there.
Refs #286