Commit Graph
2154 Commits
Author SHA1 Message Date
Willie 24151fa1bd feat(ui): richer markdown preview
Markdown previews rendered much of what people write as plain text:
HTML such as <details>, GitHub alerts, ::: containers, emoji shortcodes
and markdown-it's ==mark==/++ins++/^sup^/~sub~. Tables squeezed short
columns until words broke, and file previews joined single line breaks
even though the tool reads the file as written.

HTML now renders through a sanitizer, since previews show skills from
anyone. A leading --- block counts as frontmatter only when it is YAML,
footnote links resolve, short inline code no longer splits at hyphens,
and outside links open in a new tab so the dashboard stays open.
2026-09-29 18:03:37 +08:00
Willie ebbaba28fa chore: release v0.21.17 v0.21.17 2026-09-29 15:51:02 +08:00
Willie fd0df76d1a fix(ui): group the Sync page's in-sync and ignored lists
Both lists were one comma-joined line. With project targets named
<project>@<tool> mixed in with global ones, and every ignored name
repeating its folder, they were hard to scan. In-sync targets now show
as logo chips, global apart from each project's, and ignored names are
grouped by their ignore file and folder.
2026-09-29 15:46:13 +08:00
Willie 9bbbc9e56a docs: add 0.21.17 changelog entry 2026-09-29 15:46:13 +08:00
Willie fc5fd21a83 fix(ui): show Pi's logo in its brand colors
Pi's logo is now coral, blue and yellow, so the black mask we drew no
longer matched what users see from Pi itself. The icon is pi.dev's own
logo cropped to the mark.
2026-09-29 15:35:59 +08:00
Willie 2a00b6f5d4 docs: describe taking over matching MCP entries and extra name defaults
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
2026-09-29 15:35:58 +08:00
Willie fd3bc824f3 feat(targets): edit other files a target's tool reads from its page
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
2026-09-29 15:25:06 +08:00
Willie 012e24f639 fix(ui): keep the focus a dialog field takes with autoFocus
useFocusTrap ran after its children mounted and moved focus to the first
focusable element, so a dialog's autoFocus field lost focus to the close
button. The trap now leaves focus alone when it is already inside.
2026-09-29 15:25:00 +08:00
Willie 0aa6900050 fix(mcp): take over an Agent entry that already matches on sync
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
2026-09-29 15:23:07 +08:00
Willie b99c7153c1 fix(ui): show the MCP tab for the antigravity-cli target
Antigravity's docs say the app, IDE and agy CLI read one MCP file,
~/.gemini/config/mcp_config.json, which skillshare already manages under
the antigravity name. The dashboard looked the file up by target name,
so the antigravity-cli target never got an MCP tab. It now maps to
antigravity, the way droid maps to factory.
2026-09-29 12:37:59 +08:00
Willie 2543c47148 chore: release v0.21.16 v0.21.16 2026-09-29 12:19:16 +08:00
Willie 80fcac9ac9 docs: add 0.21.16 changelog entry 2026-09-29 12:13:15 +08:00
Willie 5530aaebe5 docs(sync): explain the warning for targets that undo each other's sync
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.
2026-09-29 12:13:15 +08:00
Willie 0931078e2a fix(targets): stop treating Antigravity as a reader of ~/.agents/skills
Antigravity's docs list only ~/.gemini/config/skills as the desktop app's
global skills folder, and an independent test found it does not read
~/.agents/skills. The entry made the dashboard claim Antigravity still
sees universal's skills after switching its own skills off.
2026-09-29 11:45:48 +08:00
Willie e48784f16b feat(sync): name targets that sync one folder with different filters
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.
2026-09-29 11:45:48 +08:00
Willie 34db034262 fix(targets): stop reporting a target's own skills folder as another source
A codex target pointed at ~/.agents/skills shares that folder with
universal, so it holds one copy of each skill. The target page still said
codex also reads universal's skills and every skill shows up twice. A
folder the target itself syncs into no longer counts as another source;
with skills off, reading universal's folder is still reported.
2026-09-29 11:45:48 +08:00
Willie 4c5ba72f38 fix(ui): say a tool finds duplicate skills instead of showing them twice
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.
2026-09-29 11:45:39 +08:00
Willie deafea7693 fix(plugin): allow Codex logos up to 1MB
Real plugin logos exceed the 256KB cap (ponytail ships a 554KB PNG), so
the dashboard fell back to the default icon for them.
2026-09-29 11:29:41 +08:00
Willie a996a5bbfd feat(plugin): show version and Codex logo for plugins with no Agent
A plugin added without choosing an Agent has no binding, so the
dashboard had nowhere to read its version from and always drew the
default icon.

Record the source version on the package when it is added, and let
rows without one ask their source once. Read interface.logo from the
Codex manifest (inside the plugin, image types, 256KB max) and draw
it in the list and in the add preview, falling back to the default
icon.
2026-09-29 11:25:50 +08:00
Willie d5015d7bab chore: release v0.21.15 v0.21.15 2026-09-29 10:31:18 +08:00
Willie 2636564c4f docs: add 0.21.15 changelog entry 2026-09-29 10:26:49 +08:00
Willie 90ed47d468 fix(ui): show a single file's source as one path in Add extra
The source folder and the file name sat in separate fields with a
preview line underneath, so it was hard to see which file would sync.
One "Source file" row now reads as the path itself (folder, separator,
file name), which makes the preview line redundant. The source type
labels now say "skillshare extras folder" and "Custom location" so the
choice is clearer.
2026-09-29 10:26:49 +08:00
Willie feab67ab11 fix(ui): list existing source folders as tags instead of a native datalist
The browser's datalist drew its own arrow and a black popup that matched
nothing else in the dashboard. Folders other single-file extras use are
now tags under the field; a click fills it in, and typing still names a
new folder.

Refs #300
2026-09-29 10:02:49 +08:00
Willie 01f7bc65cd fix(targets): give kilocode its documented AGENTS.md location
Kilo Code had no instruction file in the target list, so the dashboard
guessed ~/.kilocode/AGENTS.md from the target name, a folder Kilo never
reads. Kilo documents ~/.config/kilo/AGENTS.md globally and AGENTS.md at
the project root, which both the CLI and the VS Code extension read; a
custom path stays available through the target's instructions setting.

Refs #302
2026-09-29 10:01:19 +08:00
Willie d757afbb61 feat(extras): let several single-file extras share one source folder
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
2026-09-29 09:43:29 +08:00
Willie d9c55a5d4b docs(target): document switching skills off per target
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.
2026-09-29 05:13:06 +08:00
Willie e0882217ab feat(targets): list copy-mode copies apart when skills are switched off
Switching skills off keeps copy-mode copies, since they are real folders the
user may have edited, but they were listed as the user's own items. The tool
still loads them next to wherever it now reads skills from, so each skill
shows up twice. The CLI, the preview and the dashboard dialog now list them
separately and say to delete them if the tool reads the same skills
elsewhere, leaving that choice to the user.
2026-09-29 05:13:06 +08:00
Willie 2598359bae fix(ui): keep target notes, previews and card actions from blending together
Targets tied to a folder were shown as chips right above the include field,
where they read like filter patterns and wrapped awkwardly; they are now one
sentence in a note. The filter preview gets its own heading so it reads as
the result of the fields above it. The dashboard shows skills-off targets as
off instead of by mode. On the AGENTS.md card, the one-item menu becomes a
plain button, actions follow the same order in every state, Save appears
only when there is something to save, and the own-file note no longer says
only one tool reads a file others also read.
2026-09-29 05:03:49 +08:00
Willie 7bc8bd6634 fix(targets): count what a skills-off folder still holds and refuse mixed flags
With skills off, analyze only counted unmanaged folders, yet the tool still
loads the links a target sharing the folder keeps and the copies copy mode
leaves behind, so the report showed fewer skills than the tool reads.

`target <name> --skills=false` combined with include/exclude flags applied
the filters and silently dropped the switch, because filter updates return
first. The switch removes links, so the mix is now refused instead.
2026-09-29 05:03:49 +08:00
Willie 46b23cd2ad feat(targets): let a target keep its instructions with skills switched off
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.
2026-09-29 04:51:24 +08:00
Willie 0ff337899c docs(migration): add a path for moving from npx skills
Users who installed skills with npx skills had no migration steps; the FAQ only covered running both tools side by side. The new section maps where npx skills keeps its files and lock file, then walks through backup, collect, optional reinstall from the lock file, and sync. Behavior was checked in an isolated devcontainer environment: collect skips symlinks, plain sync preserves real directories in the universal target, and sync --force replaces them after backing up the target. Translated for zh-Hant, zh-Hans, ja and ko.
2026-09-29 04:12:03 +08:00
Willie 8e61590ed3 chore: release v0.21.14 v0.21.14 2026-09-29 00:56:25 +08:00
Willie 7ac7f1f7d7 fix(extras): describe single files and folders accurately in copy
Extras now hold single files as well as folders, but some copy still
spoke only of folders: the zh-TW page title and several tour strings
called extras "directories", and the Add extra name hint promised the
name becomes the folder name even when a custom source folder is used.
The list TUI's sync and collect confirmations named the target folder
instead of the file a single-file extra writes, and its remove prompt
said only config is removed although single-file targets are restored.

Refs #300
2026-09-29 00:54:00 +08:00
Willie 40a4423124 docs: add 0.21.14 changelog entry 2026-09-29 00:30:25 +08:00
Willie 41a560f84d docs(install): cover tree/HEAD links and pinned web URLs everywhere
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
2026-09-29 00:30:25 +08:00
Willie 3248aad384 docs(extras): document single-file extras for any file
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
2026-09-29 00:27:53 +08:00
Willie 00f51adbda feat(extras): create and manage single-file extras from the CLI and dashboard
Single-file extras (file + per-target as) already worked in the sync
engine, but the only way to create one was editing config.yaml or the
dashboard's AGENTS.md tab, so they looked like an AGENTS.md-only feature.
Syncing a file such as Pi's APPEND_SYSTEM.md required hand-written config.

- extras init gains --file and --as; the init TUI asks Folder or Single
  file. Validation runs before anything is written, and init neither
  creates the source file nor syncs.
- extras list and add-target show the full source and target file paths.
- POST /api/extras accepts file and per-target as, with the same
  connection checks as add-target.
- The dashboard's first Extras tab becomes "Folders & files" and lists
  every extra except AGENTS.md files; Add extra can create a single file
  with a per-target file name.
- Assigning shared AGENTS.md files now only attaches or detaches AGENTS.md
  extras. Before, saving on the AGENTS.md tab restored and removed any
  other single-file extra linked to the same instruction file.

Refs #300
2026-09-29 00:27:48 +08:00
Willie 13a93242f8 feat(ui): redesign the Hubs page around one list with in-place editing
Previewing a hub from the builder landed on an empty "pick a hub" state:
the builder and the browser kept separate copies of the drafts and the
browser's copy went stale. Merging both into one page removes the split,
so your own hub is shown exactly as others will see it and edited in place.

Hub entries can now be added from any repository URL, not only from
installed skills, with a branch or tag picked from the remote. The version
is written into the source URL, the only place the hub format keeps it,
and a new /api/hub/refs endpoint lists refs and rewrites sources so the UI
never builds tree/<ref> URLs itself. Skills added from installed ones keep
the version they were installed from.

Draft reads and saves read refs from the URLs only, so opening a hub never
waits on a remote. Added hubs get unique labels, since the default hub is
stored by label.
2026-09-28 23:39:19 +08:00
Willie cbaa140289 feat(website): link llms.txt files from the footer
The files were only discoverable by agents that already know the
convention. A footer link lets readers find the URL to hand to an AI tool.
Absolute URLs are used because the files exist only at the site root and a
pathname link would be locale-prefixed on translated pages.
2026-09-28 23:09:19 +08:00
Willie 2782294b01 feat(website): generate llms.txt and llms-full.txt at build time
AI coding agents and docs tooling increasingly look for /llms.txt to get a
site overview without crawling HTML. A local plugin builds both files from
the docs plugin's loaded content in sidebar order, so they never drift from
the published docs and need no extra dependency. Only the English build
emits them, since translated locales would otherwise duplicate the content.
2026-09-28 22:58:33 +08:00
Willie 83aca529f2 docs: credit the contributor behind pinned web URL installs
Refs #293.
2026-09-28 22:27:01 +08:00
Willie 529a8f2771 fix(install): keep config installs on the recorded branch
Installing from config set the branch only when one was recorded, so a
legacy entry with a tree/<tag>/... source and no branch was pinned to
that tag, while update kept it on the default branch. Use
ApplyRecordedBranch like the update paths do. Settling the ref up front
also lets web URL entries from one repo share a single clone again.

Refs #293
2026-09-28 22:12:09 +08:00
Willie 72b6a38dfd fix(install): treat tree/HEAD web URLs as the default branch
GitHub links to tree/HEAD/... when it means the default branch. Since
URL refs became clone refs, HEAD was taken as a branch name: with a
subdir the ref lookup failed, without one git clone --branch HEAD
failed. These URLs installed fine before, so keep them on the default
branch.

Refs #293
2026-09-28 22:12:09 +08:00
a352b8d243 feat(install): pin skills to a tag or commit from their web URL (#293)
* 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>
2026-09-28 22:08:16 +08:00
Willie 918cb4eec5 feat(ui): group folder backups by day and restore per folder
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.
2026-09-28 21:51:17 +08:00
Willie d572ba3b32 perf(backup): walk each snapshot once when listing backups
The list endpoint walked every snapshot to size it, then walked all of
them again for the total. With thousands of files and a cold file cache
(right after an upgrade, for example) the Backup page took visibly long
to open.

Each snapshot folder is now walked once for both its size and file
count. Backup and total sizes are sums of those, and the per-folder
counts are returned as `entries` so the dashboard can show what each
folder holds.
2026-09-28 21:51:11 +08:00
Willie fcb83d90d2 fix(ui): keep the upgraded UI cached when restarting after an update
`skillshare upgrade` already downloads the new version's UI assets, and
that download removes older versions. Restarting with clearCache then
deleted the fresh assets, so the new server had to fetch them from GitHub
again before it could answer. On a slow connection that outlasted the
dialog's 20-second reconnect wait and left the page looking stuck.

If the pre-download failed, the restarted server still downloads the
assets because none are cached.
2026-09-28 21:51:07 +08:00
Willie 66f8cf3368 fix(ui): use singular wording when a count is one
Counted labels such as "{count} skills" had only a plural form, so the
dashboard showed "1 skills", "1 of 1 targets", "1 backups" and similar.
Each such label now has a .one and a .other form in every locale, and
the call sites pick by count, as the rest of the dashboard already does.
2026-09-28 21:08:26 +08:00
Willie 49a52498e9 docs: add current screenshots and diagrams to the guides
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).
2026-09-28 21:02:12 +08:00
Willie a911064cb3 fix(ui): stop saying Backup is hidden in project mode
The project-mode note on the dashboard still said Git sync and Backup
are not shown, but Settings › Backup now appears in project mode,
scoped to the project.
2026-09-28 21:02:12 +08:00