The in-sync and ignored lists were grouped earlier, but the list of
resources that exist only in targets was still one comma-joined line.
It merged every target's names, so a reader could not tell which target
held a resource before collecting it.
Each target now gets its own group with its logo chip and count, and
each name carries a skill or agent icon.
The picked tool drew a rounded inset ink ring inside the list, which
looked like a card dropped into the rows and clashed with the dashed
separators in Playful. It now uses .ss-r.sel, the tinted fill that the
collect and install dialogs already use for a selected row.
The server put a fixed English sentence into the sync warnings, so the
dashboard showed it untranslated in every locale. The sync response now
reports the overlap as a path_overlap count, and the dashboard renders
it from the locale files with a button that opens the Health Check page.
The pull flow keeps the English sentence because it only shows raw
warning strings.
The page subtitle already says nothing is written until you press Sync,
so the playful-only hand note repeated it. The Kalam hand font has no
CJK glyphs, so in Chinese, Japanese, or Korean the note fell back to a
large system font squeezed into 150px and read as stray text.
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.
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.
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.
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
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.
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
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.
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 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.
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.
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
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
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.
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.
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.
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
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
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.
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.
`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.
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.
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.
The Backups tab only listed target snapshots and was hidden in project
mode, while file backups had no view at all and MCP backups sat in a
dialog on the MCP page. The tab now has three sections: target folders
(filter, copy path, delete one snapshot), files (each version with why
it was taken, a diff or full-text preview, and restore) and MCP (grouped
by agent config, opening the existing restore dialog). It is shown in
project mode too, scoped to the project.
Refs #299
Single-file extras in a project sat in the Folders tab and looked like
folder extras: a folder icon, folder modes and a flatten switch, with
no import mode and no sync on add. They now appear as shared-file cards
on the project AGENTS.md tab, reusing the global location rows and Add
location dialog with project-relative paths. The Folders tab lists only
folder extras in both modes, so the file-name field added there is gone.
The CJK location counts now say "locations", since the card header has
no heading next to it to give "2" its meaning.
Refs #299
An edited location only showed a hint, with no way to settle it. It now
gets the same collect and reapply note as a target row. The remove
dialog closes before removing, so the refetch no longer asks for the
preview of a location that is gone.
Refs #299
Show locations outside the tool list under the shared file, with an add
dialog for folder, file name and mode, a restore preview before removal,
and localized errors. The project Extras page takes a file name for
single-file extras.
Refs #299
Every rider row repeated the same line under its path on the AGENTS.md page, which is about instructions, not skills. The origin now shows when hovering the tool name.
Refs #299
"Run a sync" did not say where. The copy option now points at the Sync button that appears above the targets when the shared file changes elsewhere.
Refs #299
The copy option reused the Skills folder-copy text and glued a second sentence on with a space, which read oddly in Chinese. It now has one sentence about copying the shared file.
Refs #299
Mode changes, attach and the other AGENTS.md actions returned English
sentences, so a zh-TW dashboard showed "backed up ... before replacing
it" and "... is a directory" untranslated. Warnings are now
{code, params, message} and every instructions error carries a code,
so the dashboard shows them from i18n and falls back to the English
message for unknown codes. CLI output is unchanged.
Also from the Windows re-test:
- replacing a user's junction says so and where it pointed;
- status, doctor and sync agree on identical unowned copies (kept, not
linked), and an identical copy no longer suggests --force;
- the targets list shows a Developer Mode tooltip when file links are
unavailable;
- file names are taken from Windows paths too.
Refs #299
Updating many resources gave no sense of progress, and a failure was
easy to miss among the rest. The status card now shows a progress bar,
the row being updated gets a moving line and a pop when it finishes,
and blocked or failed updates move to their own section with a
one-line reason. Motion is off under prefers-reduced-motion.
A real directory at a target path showed the generic drift hint ("sync
will change it back") although sync refuses to replace a directory. The
assignment now carries reason "directory" and the row says to remove or
rename the folder.
The restore plan read "personal stay" in English because the kept-files
line had no singular form.
Refs #299
Connect-all still planned to switch a target that another shared file
holds in copy mode (the API marks only links as linked_shared), which
would silently take it from that file. Any link or copy assignment now
marks the target as held, so the switch step is gone.
The header tabs sat on the strip's divider; they are now centred with
room under the underline.
Refs #299
Exploratory testing of the dashboard found edits lost without warning,
Cmd+S saving the page editor through an open dialog, and a connect-all
plan that would write an import through another shared file's link.
- Unsaved edits now ask before leaving the target tab, closing the edit
dialog, or reloading.
- Cmd+S does nothing to the page editor while a dialog is open.
- Connect-all skips targets already held by another shared file
(linked_shared), and 409 instructions_target_held shows its reason.
- Mode and attach warnings (such as a backed-up edit) show in a toast.
- Restore wording matches what restore does; the per-file connect time
was dropped because the record is per target file.
- Convert defaults to a new shared file; a new file is selected at once;
an unknown ?file= falls back and fixes the URL.
- The collapsed shared-file card scrolls instead of clipping.
- Change location is disabled while a shared file holds the target.
Refs #299
Every AGENTS.md box showed its size and view switch differently, which
read as clutter. One header strip now carries the live line count and
the Preview/Source switch everywhere; the read-only card opens in
Preview since that is what people read first.
The target page editor now saves with Cmd/Ctrl+S. An open editor
claims the shortcut so it no longer jumps to Sync while editing.
Read-only raw text wraps instead of scrolling sideways.
Refs #299
The edit/preview switch existed only on the target page, so the shared
file's editor, the new-file dialog and the read-only card still showed
raw Markdown. They now share one tab component: Edit | Preview in the
editors and Source | Preview on the read-only card, with previews built
from the unsaved draft.
The read order also listed rule folders such as claude's rules/*.md with
"0 files" for everyone who does not use them; empty folders are now left
out and a folder appears once it holds files.
Refs #299
Saving a shared AGENTS.md in the dashboard only wrote the source, so every
target in copy mode (including the Windows copy fallback) kept the old
content until someone found the sync button. Saving now rewrites that
file's copy targets through the regular extras sync, so an edited copy is
still backed up first, and the toast names the copies it updated. Link and
import targets already read the source and are left alone.
Refs #299
The AGENTS.md tab picked each target's mode for the user (import where
supported, a link elsewhere), which left Windows users without Developer
Mode no way out of a broken link and gave no copy option. Restore replaced
a file without showing what would come back, and only custom tools could
change which file a target reads.
- Each connected target gets a mode picker (import, symlink, copy); symlink
is unavailable when the machine cannot create file links, and a target
whose file is a folder link says so.
- Restore opens a preview of the file after restore and its diff.
- Every supported target can change its file location and name in a
dialog, with reset to default.
- The target file tab is a single column with the read order on one line,
a tinted managed import block, soft wrap, and an edit/preview switch;
universal lists the files of the tools that read its skills.
- The convert dialog shows only the methods that apply and a ready preview.
Refs #299
With only universal configured, tools such as Codex, Gemini CLI and Pi
still read skills from ~/.agents/skills, but none of them reads
~/.agents/AGENTS.md, and their own instruction files had no page and
could not take a shared AGENTS.md. Universal's AGENTS.md tab now offers
the installed ones in a dropdown, and the shared AGENTS.md list includes
them. A tool is listed once per file and disappears when it becomes a
target of its own.
Cline and the Warp Agent CLI read ~/.agents/AGENTS.md itself, per their
docs, so they now share universal's file.
Git opens every HTTPS failure with "unable to access", a bad certificate
or a 403 included, and a missing git-lfs says "command not found". Those
were reported as a network problem or a missing source and sent the user
to the wrong fix; they now fall back to the general failure.
Discovery of a managed plugin is also cached per plugin, since two
plugins of one source can have snapshots at different commits.