225 Commits
Author SHA1 Message Date
Willie 7d9d7a8971 feat(backup): list and clean up project snapshots from the CLI
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
2026-09-28 19:29:49 +08:00
Willie 4c66a06efd docs: document backup management and file history
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
2026-09-28 19:26:38 +08:00
Willie 892d3f5153 docs: sync AGENTS.md and Windows copy-fallback docs with recent fixes
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
2026-09-28 16:57:03 +08:00
Willie 81ed0f1529 docs(extras): document shared-file ownership, --as, and restore behavior
Refs #299
2026-09-28 15:37:03 +08:00
Willie 42c1051b88 docs: describe Windows file links and the new AGENTS.md controls
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
2026-09-28 13:57:40 +08:00
Willie daf77b037f fix(target): keep skills another target still syncs when removing one
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.
2026-09-28 01:58:29 +08:00
Willie 95f168feda fix(upgrade): say how to take back a skill left owned by root
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.
2026-09-28 01:36:42 +08:00
Willie 5d1f1dc724 fix(mcp): write pi-mcp-adapter servers to mcp-adapter.json
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
2026-09-27 18:05:26 +08:00
Willie 8399e06d07 docs: describe the single-panel AGENTS.md tab
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.
2026-09-27 10:45:25 +08:00
Willie 86fb63fd4b docs: document sharing AGENTS.md from the dashboard
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.
2026-09-27 04:17:41 +08:00
Willie 779ec26ff5 fix(upgrade): elevate only the binary replacement with sudo
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.
2026-09-27 02:10:00 +08:00
Willie 2be314a1dd feat(ui): filter and group skills by folder
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.
2026-09-26 21:25:32 +08:00
Willie a7e009bb9e feat(ui): rework the skills tree as a tree with a detail pane
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
2026-09-26 21:02:36 +08:00
Willie bc01ff1b3e feat(server): let tracked-repo skills take dashboard targets
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
2026-09-26 21:02:28 +08:00
Willie 11ccf30a18 docs(git): describe how pull and push handle two machines
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.
2026-09-25 03:00:15 +08:00
Willie 4a2464a712 docs(extras): describe collect --force and copy-mode behavior
Refs #291
2026-09-24 00:05:55 +08:00
Willie 33063dee45 docs(ui): describe the MCP tab on a target's page
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.
2026-09-23 00:38:44 +08:00
Willie e1bf171528 docs(mcp): describe the Pi settings line and project conflict import
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
2026-09-22 20:51:05 +08:00
Willie b561b51457 docs: describe stopping MCP management and unmanaged servers
Also explains how an Agent entry of the same name is taken over.

Refs #290
2026-09-22 19:08:51 +08:00
Willie 41912ba7ab docs: describe in-place sync buttons
Refs #289
2026-09-22 15:17:24 +08:00
Willie bb57a9af9c feat(targets): add account targets for a second Claude, Codex or Pi config directory
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
2026-09-22 11:21:35 +08:00
Willie 78b587c845 docs: name MCP buttons as the dashboard shows them, and fill an upgrade gap
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.
2026-09-22 02:46:04 +08:00
Willie 4b89e81fdd docs: cover the project MCP row, the piOptions box and upgrade progress
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
2026-09-22 02:40:02 +08:00
Willie 8b22b2edbc docs(mcp): describe piOptions for pi-mcp-adapter
Refs #289
2026-09-22 02:33:08 +08:00
Willie 8a9fb92ff1 docs(mcp): describe a disabled entry that follows the project's targets
Refs #289
2026-09-22 01:17:59 +08:00
Willie 9824ea54ea docs(mcp): document keeping a server without syncing it
Cover the empty targets list, --target none, how it differs from leaving
targets out, and what the terminal and the dashboard show for it.

Refs #289
2026-09-21 23:21:24 +08:00
Willie 5044b58eea fix(mcp): reuse an OpenCode project config kept in .opencode
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
2026-09-21 22:23:18 +08:00
Willie b75b4d6e6a docs(mcp): document taking over an entry from a removed config
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
2026-09-21 21:20:52 +08:00
Willie e0c1111b79 feat(plugins): add a plugin without choosing Agents yet
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.
2026-09-21 17:18:03 +08:00
Willie 2289058647 docs(agents): document converting agents with an extension
Also drops the note that the dashboard collect page is skills-only; the
target page has collected agents for a while.

Refs #267
2026-09-21 13:31:44 +08:00
Willie 3873f1f060 docs(mcp): describe turning a global server off from mcp.projects
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
2026-09-21 11:08:11 +08:00
Willie b75977135a feat(mcp): turn a global server off for Claude Code from mcp.projects
Claude Code keeps its per-project off list in ~/.claude.json, the same file
its user-scope servers live in. The plan keyed desired entries by file path
alone, so one file could carry only one native target, and mcp.projects had
to refuse a disabled entry for Claude Code rather than write that list.

Key the plan by file and target instead. Apply already rereads the file per
plan, and sectionDigest hashes only the target's own section, so two plans
on ~/.claude.json fold in order without further machinery.

A change now carries the mcp.projects root it belongs to. Its path no longer
says, because a project's off switch is written outside that project folder,
and the dashboard needs the root to keep the switch out of the global server
list and to show a pending badge on the project it came from.

Codex stays refused. It merges the project file field by field, so a switch
for a server its global config lacks leaves an entry with no transport and
stops Codex loading its config at all.

Alongside this, the dashboard gets a named "Turn off a global server" action,
so adding a switch and adding a server are two choices up front rather than
one form that asks afterwards. Two older glitches go with it: a project's
target toggles sprang back while the list was still empty, and the expanded
config editor stayed open when a tab arrived from the URL.

Refs #286
2026-09-21 10:55:37 +08:00
Willie 0b3eedfd6c docs(projects): explain the project lockfile
Teams need to know that skills.lock.json is meant to be committed, which
commands move a pin, and how it relates to the config.yaml manifest.
Covers project-skills, install, update, uninstall, declarative-manifest
and project-setup, in English and the four translated locales.
2026-09-21 04:31:22 +08:00
Willie 1fb23f1e59 feat(analyze): measure what each target actually loads
The analyze numbers were drifting from what tools really see. Symlink-mode
targets expose the whole source folder, so .skillignore'd skills still load
but were left out; merge/copy targets often hold skills the user dropped in
by hand that skillshare never counted; and chars/4 undercounted CJK text by
roughly four times.

Route the CLI, TUI, web handler and sync summary through one
sync.TargetSkills so the three copies of the filter logic cannot disagree
again. Disabled skills stay in the discovery with Disabled=true and are
priced for symlink targets; unmanaged folders in a target are reported as
Local. Token estimates now charge one token per wide rune.

The dashboard keeps the chosen target in the URL so target and project
pages can deep-link into the analysis, lists project targets after own
targets with their tool icon, and tags local/disabled rows. Select gives
single-select icons a key to silence a React warning.
2026-09-21 04:17:26 +08:00
Willie 449fe40d6f fix(targets): move goose and openhands to .agents/skills
Both tools now document ~/.agents/skills and <project>/.agents/skills as
their skills locations and keep the old directories only for backward
compatibility. Writing to the old path next to `universal` makes them read
every skill from two places.

Global configs pin absolute paths, so they are unaffected and keep their
overlap warning. Project configs store target names only, so an existing
project follows the new default on its next sync while the links it created
in .goose/skills or .openhands/skills would stay behind and show up as
duplicates. Project sync now removes those leftovers from also_scans
directories that no configured target writes to.

That directory belongs to another tool, so the cleanup runs the prune with
ManagedOnly: only symlinks into the source and manifest-tracked folders are
removed. The flat-name heuristic would otherwise delete hand-made folders
such as `_drafts`. Targets with an explicit path are skipped, and --dry-run
only previews.

Refs #135
2026-09-21 02:55:18 +08:00
Willie 7d26726a5e feat(targets): split antigravity-cli into its own target
The Antigravity CLI (agy) reads ~/.gemini/antigravity-cli/skills and
never the app's ~/.gemini/config/skills, so treating it as an alias of
antigravity synced skills to a directory it does not read. Give it its
own targets.yaml entry with the correct path.

A path-less `antigravity-cli:` config entry also failed validation,
because DefaultTargets() is not alias-aware; as a real target it now
resolves to the default path.
2026-09-21 02:36:06 +08:00
Willie 338bc2c2a4 fix(install): harden ref pinning after code review
- Fallback fetch pulled only the default branch because a depth-1 clone
  is single-branch; fetch all heads and tags so an abbreviated SHA off
  the default branch resolves.
- Move the --track guard from CLI flag parsing into InstallTrackedRepo
  so the Web UI is covered too, and reject tags as well as SHAs: both
  leave HEAD detached with nothing for `git pull` to follow.
- An all-hex branch or tag name (e.g. 20240915) was treated as a SHA in
  check and never queried; look the ref up first and fall back to the
  literal SHA only when the remote has no such ref. Full 40-char SHAs
  still skip the network.
- Rename the git package's 7-char shortHash to abbrevHash to avoid
  clashing with install's 12-char helper.

Refs #281
2026-09-21 02:26:55 +08:00
Willie 69d643525d fix(targets): point the codex target at ~/.agents/skills
Codex documents ~/.agents/skills as its user-level skills path and marks
~/.codex/skills as deprecated, while still reading both. It does not merge
skills that share a name, so the default init result (codex + universal)
showed every skill twice in Codex.

The codex target now defaults to the shared directory, keeps the old path
in also_scans, and is detected through ~/.codex. A fresh init therefore sets
up only `universal` for Codex and writes each skill once. Existing configs
keep their pinned path and still get the doctor overlap warning that
suggests removing the codex target.

Refs #135
2026-09-21 02:21:49 +08:00
Willie 85a25f4383 docs(install): document tag and commit SHA pinning via --branch
Refs #281
2026-09-21 02:12:48 +08:00
Willie 67ee35fb4a docs(projects): document the global projects key and when to use it
Global skills already reach every project, so the docs lead with when
`projects` is not needed and compare it with plain global targets and
project mode. The recipe, config reference, MCP and UI command pages
are updated in English and the four translated locales.

Refs #286
2026-09-21 01:52:38 +08:00
Willie 84510545e4 fix(doctor): suggest removing the scanning target for discovery overlap
The cross_target_discovery suggestion pointed users at removing the
writer target (e.g. universal). That target owns a shared directory, so
removing it also hides skills from every other tool that reads the same
path. Removing the scanning target (e.g. codex) only affects that one
runtime, which still receives the content through the shared directory.

Reword the suggestion and the matching docs resolution in all locales.

Refs #135
2026-09-21 00:20:15 +08:00
Willie fee6e491ee docs(mcp): document mcp.projects, directTools and the Projects tab
The mcp reference gains sections for managing several projects from the
global config, the dashboard's Projects tab and Defaults, and Pi direct
tools. It states that a project lists only what differs: a global server
already loads in every project because the Agent merges its global and
project files, a point readers arriving at that section kept missing.

A new recipe, many projects from one config, shows skills and MCP servers
together, since custom path targets already solve the skills half.

The built-in skill's MCP reference is rewritten around the same material so
an Agent editing config.yaml for a user knows these rules.

All of it is mirrored in zh-Hant, zh-Hans, ja and ko.

Refs #286
2026-09-20 23:49:24 +08:00
Willie 4415c7a75a docs(website): pin explicit anchors on headings that will be retranslated
These headings mix prose with technical terms (e.g. '.skillignore
(Optional)', 'Git Authentication', 'Target include/exclude filters')
and are referenced by anchor fragment from other pages. Translating
the prose changes the auto-generated slug and breaks the link, so
pin the current slug explicitly before the next translation batch.
2026-09-20 11:21:14 +08:00
Willie cf36965cea feat(website): add zh-Hant/zh-Hans/ja/ko locales with initial docs translation
Sets up Docusaurus i18n for Traditional Chinese, Simplified Chinese,
Japanese, and Korean: locale config, navbar/footer/sidebar UI chrome,
and translated content for intro, getting-started, understand, and
reference/commands. Untranslated pages fall back to English.

Pins explicit heading anchors ({#id}) on English source pages that are
linked to by fragment, so translated headings don't change the anchor
id and break cross-page links. Converts a handful of relative .md
links that crossed from an untranslated page into a now-translated
one, since Docusaurus resolves those per-locale and they'd otherwise
404 outside English.
2026-09-20 11:08:48 +08:00
Willie a1fc80c9d5 fix(upgrade): explain the password requirement instead of sudo's raw error
After the previous fix the dashboard failed fast but showed the whole
CLI transcript ending in "sudo: a password is required", which does not
tell the user what to do next.

Probe `sudo -n true` before re-executing and return a message naming the
terminal command. The server maps that to an `upgrade.needs_sudo` error
code so the update dialog and the Doctor page can show a translated
sentence in every locale.

Also bound the release download with a client timeout; http.Get had
none, so a stalled connection could hang an upgrade indefinitely.
2026-09-20 11:08:48 +08:00
Willie 296e80b745 docs: document Gitea and CNB tokens and host settings
The platform support merged without any docs, so a private repo on either
host failed with no hint about which token to set, and self-hosted
instances had no way to learn about gitea_hosts or cnb_hosts. Refs #168.
2026-09-20 03:36:56 +08:00
Willie 5923063a44 docs(mcp): cover Codex's shared config and why it has no project switch
Codex's config.toml is read by the Codex CLI, the IDE extension and the
ChatGPT desktop app, so a server synced to codex reaches all three. The
docs never said so, nor that Codex loads .codex/config.toml only in a
trusted project, which is the usual reason a synced server does not show.

Turning off a global server per project stays unsupported for Codex, now
with the reason stated. Codex does merge the project file by field, but an
entry left without a command or url makes it fail its whole config load
with "invalid transport". The project file is usually committed, so one
person's switch would stop Codex for a teammate whose global config lacks
the server. Selecting codex now says this instead of the generic refusal.

Also document how the MCP page detects Agents and that an entry owned by a
config that no longer exists can be taken over.
2026-09-20 02:46:34 +08:00
Willie 6f7ece397b docs: describe the dashboard's manual only tag and field menu
The dashboard now shows which skills are manual only and explains each
frontmatter field in the editor's add menu, but the ui and list pages
still described that state as visible only in the list TUI.

Refs #283
2026-09-20 02:46:34 +08:00
Willie 86ef9788be feat(mcp): turn off a global server for Claude Code and tighten detection
Claude Code takes a whole server entry from one scope, so the lone switch
used for OpenCode, Kilo Code and Pi would replace the server in .mcp.json
instead of turning it off. In project mode a disabled entry for claude now
adds the name to that project's disabledMcpServers list in ~/.claude.json,
the list /mcp edits. It keys apart in the ledger from a user-scope server
of the same name that a global config may own in the same file, and a name
the person turned off themselves is never claimed or removed.

A local scope server of the same name silently wins over what Skillshare
writes, so project-mode plans now report it with the command to remove it.

Checks against each Agent's documentation also showed gaps:
- Detection missed Agents whose MCP file does not exist yet, such as a
  fresh Claude Code install, and listed every Agent in project mode.
  It now looks at the Agent's own folder and at project files.
- Cline moved its settings to ~/.cline/data and honors CLINE_DIR,
  CLINE_DATA_DIR and CLINE_MCP_SETTINGS_PATH; the old VS Code path is
  kept only while it is the one in use.
- Kilo Code ignores a project config that holds an environment
  reference, and Claude Code skips reserved names and reads its own
  credentials as empty for remote servers. These are refused up front,
  and the dashboard preview refuses them too.
- An entry owned by a config that no longer exists could never be
  released; an explicit resolution may now take it over.
- --disabled was accepted by commands that ignored it, and a relative
  XDG_CONFIG_HOME or Cline override was used as given.

Refs #286
2026-09-20 01:32:45 +08:00
Willie caea5cce6a feat(mcp): turn off a global MCP server for one project
A server defined in an Agent's global config could not be switched off for
a single project without editing that Agent's file by hand. A source entry
with only 'disabled: true' now writes the Agent's own off switch into its
project file. Only Agents that merge project entries over global ones field
by field can honour a lone switch, so this is limited to OpenCode, Kilo Code
and Pi with pi-mcp-adapter; other targets and global mode are refused with
an explanation rather than writing an entry that would break the server.

Refs #286
2026-09-20 00:28:57 +08:00