Some tools, such as Codex, look for project skills only up to the Git root
of the folder you open. When one workspace folder holds several checkouts
or worktrees, skills synced to the workspace are not seen inside them, and
registering each checkout by hand repeats the same settings many times.
`project add <root> --scan DIR` registers the root and each Git checkout
found below the scan folders as ordinary project entries with the same
settings, in one write. No scan setting is saved; rerun it after a new
clone. It only adds: a checkout already registered with the same settings
is kept, one with different settings or its own .skillshare/ is skipped
with the reason, and a name clash derives the name from the path. A scan
folder that is missing or cannot be read is skipped with a warning so one
unreadable folder does not block the rest. Rows carry a root-relative path
and a skip code so the dashboard can explain them in its own words.
Dashboard:
The dashboard should offer what `project add --scan` does, so a workspace
with many checkouts can be set up without the terminal.
The Add project dialog gains "Also add each checkout inside this folder"
with the folders to look in. Review runs the scan as a dry run through the
new POST /api/projects/scan and lists each folder as Added, Kept or Skipped
with a translated reason and a link to a project whose settings differ;
nothing is written until it is confirmed. The write scans again and counts
what it actually added, so a checkout registered in the meantime is not
reported as new. MCP and Hooks, when picked, are set up for each added
project. Without an explicit storage choice the default follows
projects_storage, as the CLI does without a flag.
Closes#953
Release-As: 0.30.12
* refactor(ui): isolate resource operations and cancellable reads
Keep resource toggle rollback and move reconciliation outside the view. Preserve the preview and revision protocols and distinguish cancelled resource reads from connection failures.
* refactor(ui): standardize JSON requests across dashboard APIs
Keep HTTP verbs, paths and payloads visible at each endpoint without repeating serialization. Preserve bodyless requests, raw JSON imports and streaming responses, and cover the extras request contracts.
* refactor(ui): share sync eligibility and upgrade recovery
Use scoped plans for sync counts and writes, share restart polling, and restore only the edited target field when a resource write fails.
* fix(ui): show pending MCP source migrations in sync preview
Render the migration counted by the global plan rather than an empty preview when no MCP target file changes. Cover the mismatch through the rendered sync page.
Format the dashboard with Oxfmt and use tsrs for project builds and Oxlint type analysis. Fix the initial typed findings and check formatting and typed lint in CI to keep new changes consistent.
Removing a project keeps its mcp.projects and hooks.projects entries on
purpose: they are separate lists that no project command edits, and the
dashboard lists such a folder on its own. But nothing said so. The CLI
warned "mcp.projects still contains root X" with no next step, and the
dashboard dialog only mentioned it for a machine-local project, so a
removed project's MCP settings looked like a cleanup bug.
The CLI warning now names the settings and where to remove them. The
remove dialog says they stay and that removing the leftover row deletes
them, except when only this machine's copy goes and config.yaml's
project remains. project.md, ui.md and the skill reference describe it.
* fix(ui): show each MCP server's Agents once and animate target pickers
MCP server rows drew the same Agent logos twice: a stack inside the
n/N pill and a row of chips under the name, so a list of servers read
as a wall of repeated icons. Rows now keep only the pill's stack, as
plugin rows do. Opening the pill shows the toggles with each Agent's
name, and Pi's exposure mode moves to a tag beside the Pi toggle.
The toggles of MCP rows, MCP defaults and plugin rows popped in and
out. They now grow and shrink with Reveal, and the pill chevrons
rotate, matching the hooks pages.
The MCP and dashboard reference pages and their four translations
described the chips; they now describe the logos on the count button.
* fix(ui): stop disclosure folds animating under reduced motion
The reduced-motion reset named only .ss-collapse, which .ss-collapse.grow
and .ss-collapse.grow.shut outrank with their own transitions. So every
Reveal fold, now including the MCP and plugin target pickers, still grew
and shrank for people who asked for less motion. Naming both selectors
in the reset lets it win.
* fix(ui): fold and simplify a project's MCP targets, animate Agent ticks
A project's MCP tab opened its Targets picker instantly, under a bare
label, with a segmented "Same as global / Choose for this project"
control above the toggles. It now reads like the global MCP defaults: the
setting and its pill on one row, the toggles folding in below. While the
project inherits, the global targets show ticked and the first tick
starts the project's own list from them; a small "Back to global" link
returns, still behind the confirm dialog. The unused key behind the old
control is dropped from every locale.
That first tick used to leave the toggles blank until the refetch landed,
so a second tick in that gap saved from an empty list, and a failed save
left an empty own list on screen. The list just sent now stays on screen
until the saved one comes back, and a failed save shows the config again.
Agent toggles on MCP and plugin rows snapped their check badge in and
out. The badge now pops in and shrinks away with transitions, only fades
under reduced motion, and the half-lit hover is limited to fine pointers
so a tap on a touch screen doesn't leave it behind.
* fix(ui): let Back to global drop a list that has not come back yet
The first tick on an inheriting project saves an own list, but the
project's targets stay undefined until the refetch lands. Back to global
read those stale targets, saw no list, skipped the confirm dialog and
the write, and the saved list came back with the refetch. It now goes by
the list on screen, so it asks and then saves the reset as usual.
The Latest callout still named 0.30.10. Point it at Pi package sharing and the in-place Antigravity and Copilot hook edits, in every translated README.
The ja, ko, zh-Hans and zh-Hant plugin guide and the dashboard page table never described Share. Add it with the Pi packages it now lists, using the dashboard's own label for the ask option.
The "Hooks in targets" dialog could change or remove a hook without
importing it only when the Agent keeps hooks as events of one settings
file. Antigravity blocks and Copilot hook files had to be imported first,
even though both are plain configuration the dialog can address exactly.
Candidates now carry the block or file they were read from (source), and
NativeEdit uses it: an Antigravity edit replaces or removes the whole named
block, keeping enabled: false; a Copilot edit rewrites only the file's
hooks key or deletes the file. Both keep the preview diff, the stale-file
check, the backup, and the hook stays unmanaged. Code hooks (Pi, Oh My Pi,
Amp, OpenCode) still need importing.
Dialog rows are keyed by source, so two Copilot files that read as the same
hook name (lint.json, skillshare-lint.json) can no longer be removed
together. Copilot rows show the file name, the editor names the file, and
removal says the file is deleted.
Share listed only the plugins added from an HTTPS Git source, so a Pi
setup made of npm packages could not be passed on from the dashboard.
Pi downloads an npm package itself, and `plugin add npm:<package>` needs
a Pi target. The dialog now lists the npm Pi packages after the plugins,
each under its own heading, and copies
`skillshare plugin add npm:<package> --target pi -g --no-tui` for them.
The built-in target is named because the sharer's own may be an account
only they have. With the ask option ticked, the command leaves the
target to the prompt. Packages Pi has from Git or a local path are not
listed.
Plugins stay first in the copied line, so a machine without Pi still
adds every plugin before the first Pi package stops the list.
Release-As: 0.30.11
* fix(ui): keep the page width steady when its scrollbar comes and goes
The styled 8px scrollbar takes layout width even where the system uses
overlay scrollbars. Whenever the page stopped needing to scroll (a short
tab, a filtered list) or a dialog locked scrolling, the bar vanished and
the whole page grew 8px wider, then shrank again.
The page itself now uses the system scrollbar: an overlay one takes no
width, and a classic one keeps its gutter reserved. Scrolling areas
inside the page keep the styled scrollbar.
* fix(ui): list custom targets in the skill target menus
"Available in..." and "Set targets" built their list from the known
tools and kept the installed ones. A target with a custom name is in no
built-in list, so it could not be picked from the dashboard, and the
order changed between openings because the known tools come from a map.
The menus now list the configured targets, sorted by name.
The Latest callout still named 0.30.9. Point it at the Codex hook trust
that 0.30.10 ships, in every translated README, and add the author of
#914 to the contributors.
The squash commit of #829 carries this footer in the middle of its
message, followed by co-author trailers, so Release Please did not read
it and moved the release to 0.31.0. Keep the next release on the patch
version the maintainer asked for.
Release-As: 0.30.10
Without file-link privilege (Windows without Developer Mode) merge mode
copies agents and tracks the copies it wrote. A file a tool already had
with the same bytes as the source was not tracked, so it was kept, and
--force kept it too: the identical-content check ran before the force
check. init's "kept local agents: X (sync agents --force replaces them)"
then named a file --force could never take over, on every run.
With --force the file is now recorded as skillshare's, so later syncs
update it. Without --force nothing changes.
Also: the five-name cap written twice is one helper, sync.ListNames,
and doctor.md says when a recorded broken link is reported as a broken
symlink (the behavior from #942).
init syncs agents quietly, and an agent file a tool already had under an
agent's name was kept without a word: init said "Synced" while the tool
went on loading its own file. A plain sync shows this only as a count.
The quiet agent run now returns a line per tool that names the kept
files and the command that replaces them, and init prints it with the
skill warnings. In symlink mode what is kept is the whole agents folder,
so the line says that instead.
Closes#938
Three previews disagreed with what sync does to a link no skill or
agent maps to.
The agent diff, in the CLI and the dashboard, listed every orphan link
as a removal. Agent sync prunes a link only in merge mode, and only when
it is broken or points into the source, so a live link to another
location was listed forever. Both diffs now ask the function prune uses.
The CLI diff listed no orphan links at all for merge-mode skills, so a
skill removed from the source showed nothing until sync pruned its
link. It now lists the links sync.OrphanLink says prune removes.
doctor called a broken link "did not create, kept" whenever OwnsLink was
false. Prune also removes a broken link under a name the manifest
records in any form once no skill maps to it, so doctor told the user to
delete by hand a link that sync removes. It now reports those as broken
and suggests sync. An empty source counts as "every entry is an orphan";
only a failed discovery turns the check off.
Closes#939Closes#940Closes#941
The Sync page predicted which orphan links sync would remove with its
own copy of prune's rule. The copy had already drifted once (#914), and
it still disagreed in two cases: prune treats a link it cannot follow,
such as a loop, as broken, while the page only counted a missing
destination; and prune keeps a link whose target it cannot read.
The decision now lives in sync.OrphanLink. Prune and the dashboard diff
both call it, so a later change to the rule reaches both. Prune's
results, warnings and dry-run text are unchanged. LinksIntoSource, added
for the dashboard's copy, is no longer needed and is removed.
* fix(ui): pick nothing by default when taking over hooks from targets
The hooks import dialog is also where a hook is edited or removed in its
target file without importing it, but it opened with every hook ticked,
so managing removals could import the rest by accident. It now opens
with nothing selected, and its entry points are named for what they
show ("Hooks in targets", "Not managed yet") instead of "Import".
The review step stacked three scroll areas (dialog body, file list,
diff) and listed each removed hook three times. The dialog body is now
the only thing that scrolls, hook names are listed once, a file card
shows a count per action, and its diff opens on request. The other hook
previews share the component: their diffs still start open but lose the
inner scroll and gain the same toggle.
Adding or editing a hook now uses the same command cards as editing one
in a target: collapsible, with a multi-line editor that can be expanded.
A collapsed card with a missing field is marked. The variable buttons
append to the command there instead of inserting at the cursor.
A missing OpenCode CLI showed the raw exec error when reading its hooks;
it now says the command was not found and what to do.
* fix(ui): explain a missing OpenCode CLI in hook plan warnings
The sync preview, Sync page and target hooks views show the same
failure as a plan warning, wrapped as "target X: detect OpenCode API
...; its hook bindings are skipped". That form still put the raw exec
error in parentheses. It now says the command was not found, that the
bindings are skipped, and what to do. Other detection failures keep
the existing message with the detail.
* fix(ui): fetch each repository once when the dashboard updates skills
Updating many skills from the Updates tab cloned the repository once per
skill and reinstalled every one, so 31 skills from 8 repositories took over
a minute where `skillshare update --all` takes 16 seconds, and unchanged
skills were reported as updated.
The update stream and the update-all endpoint now group the request's
skills by repository and branch and go through install.UpdateSkillsFromRepo,
as the CLI does. A skill that already matches upstream is left alone and
reported as up to date; the Updates tab shows and counts it that way.
Results still arrive in request order, which the dashboard relies on.
Updating a single skill and switching its branch still reinstall. Those
paths now also pass the configured parse options to the installer.
* fix(ui): keep one thing moving while an update runs
An update showed a spinner in the status card, a progress bar, a spinner
on the active row and a moving line under it, all at once. The bar also
sat empty while a repository was fetched, and was removed in the same
render as the last result, so it never reached the end.
The bar is now one shared component. A faint runner shows work before
the first item finishes, the fill moves with a transform, and when the
run ends it reaches the end, holds, then fades and gives its space back.
The status card icon stays still and ends with a check that draws
itself. The active row is marked by a light sweeping its status text
instead of a spinner and a line. Backup, install from config, the plugin
update dialog and pending Doctor checks follow the same rule.
* fix(ui): fetch each repository once when the dashboard updates skills
Updating many skills from the Updates tab cloned the repository once per
skill and reinstalled every one, so 31 skills from 8 repositories took over
a minute where `skillshare update --all` takes 16 seconds, and unchanged
skills were reported as updated.
The update stream and the update-all endpoint now group the request's
skills by repository and branch and go through install.UpdateSkillsFromRepo,
as the CLI does. A skill that already matches upstream is left alone and
reported as up to date; the Updates tab shows and counts it that way.
Results still arrive in request order, which the dashboard relies on.
Updating a single skill and switching its branch still reinstall. Those
paths now also pass the configured parse options to the installer.
* fix(ui): keep checkouts and recorded sources when updates share a fetch
Grouping a dashboard update by repository sent every skill through the
discovery installer. A root skill kept as a Git checkout was replaced by
a plain copy, losing its repository, and an updated skill had its source
recorded in the repository's canonical spelling, which a project
declaration written with another spelling no longer matches.
A checkout now updates on its own by pulling, as before, and an updated
skill keeps the source its record had, as updating one skill does.
The Latest callout still named 0.30.7. Point it at the hooks import
dialog change that 0.30.9 ships, in every translated README, and add
the reporters of #921 and #922 to the contributors.
Choosing "No limit" for a skill, a folder or a selection still showed
"… now available in All": the toasts put the old "All" label into the
"available in {target}" sentence. That is the wording #925 found
misleading, and it no longer matches the option's name.
Give the no-limit case its own sentence in each of the three toasts
and drop the "All" label nothing else uses.
* fix(ui): count symlink-mode targets in the Skills list
A symlink-mode target links the whole source folder, so every skill is
live there. The skill detail page and the Sync page count it, but the
Skills list read only `synced` matrix entries: the Targets column, the
tree pane and the target filter left such a target out, and the Agents
page reported a symlink-mode agent target as not supporting agents.
A skill whose targets all had skills switched off was labelled "No
agent targets", wording meant for agents. It now reads "Skills off".
Nothing else reaches that label any more, so the key is removed.
The list now applies receivesSkill, the same rule as the other pages.
Closes#926
* fix(ui): rename the "All" target option to "No limit"
The option clears a skill's own `targets:` field. Labelled "All", it
read as "synced to every target", so a skill showing "All" next to a
single target icon looked like a bug (#925). "No limit" says what the
field does and pairs with the existing "Limited" tag.
Closes#925
The sync matrix reports a target as `na` both when it is in symlink
mode and when skills are switched off for it. The skill detail page
read every `na` as symlink mode, so a skills-off target showed
"Symlink mode, filters do not apply" with its switch on and counted
toward "4 of 4", although nothing syncs there. Next to a Skills list
that shows only the targets the skill reaches, the two pages
contradicted each other (#925).
Use receivesSkill, the rule the Sync page already applies, so only a
symlinked folder counts as carrying the skill, and label the other
case "Skills off".
* feat(hooks): browse, edit and remove unmanaged hooks in the import dialog
The import dialog listed every target's hooks in one long scroll of
full commands, so it was hard to read and hard to tell which target a
row belonged to. It also offered no way to change a hook without first
handing it to skillshare.
The dialog now shows one target at a time from a rail, with two-line
rows that open to the full commands. A hook that lives as an event in a
target's settings file can be edited or removed in place: the change
stays pending, a review step shows the file diff, and only then is the
file written, with a backup that restores it. The hook stays unmanaged.
The write is a new operation in internal/hooks (PreviewNativeEdits and
ApplyNativeEdits) that addresses elements by content, refuses anything
a ledger record holds, and reuses the existing backup and journal path.
Whole-file hooks, Copilot files and Antigravity blocks still have to be
imported first.
* fix(hooks): keep repeated restores and retries from writing a hook twice
Two ways an unmanaged hook could end up in a target file twice:
Restoring the backup of a removal a second time appended the hook
again. An unmanaged hook has no ledger record, so nothing marked the
backup as restored. PreviewRestore now reports a conflict when the
removed hook is already in the file.
When the dialog's native write succeeded and a later import failed, the
retry compared each pending change with the row it was made in. An edit
that moves or adds a command under another event comes back as other
rows, so the change stayed pending and was written again, and the new
row was picked for import. The dialog now drops every change once the
write went through (or reports files it already applied), and keeps
only the rows picked before as imports for the targets it wrote.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(hooks): tell a restored hook from a surviving twin, keep unwritten edits
The check that refuses a second restore of a removed unmanaged hook
looked for any unmanaged hook with the same content. When one of two
identical hooks was removed, the survivor made the first restore look
done. A removal that shifts later hooks is stored as an update plus a
removal, which the check did not cover, and a restored hook that was
imported afterwards no longer counted, so those backups could still
restore twice. Every change to an unmanaged hook now records how many
identical hooks the write left, and a restore is refused only when the
file holds more than that.
When a native write failed after its first file, the dialog dropped
every pending change, including those of files the write never reached.
The failure response now lists the applied files in error_params, and
the dialog drops only the changes of those files. Pasted candidates are
no longer unpicked by a write to the target they were pasted for.
* fix(ui): show a hook row's edit and remove actions once
An open row in the import dialog showed the pencil and trash icons next
to the labelled Edit and Remove buttons below, which do the same thing.
The icons now hide while the row is open; their space is kept so the
chevron stays where it was clicked.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(hooks): count surviving twins for every backup, not only native edits
Only the native edit preview recorded how many identical hooks a write
left, so the backup a restore writes had no count. Undoing a restore
through Backups was then refused whenever a hook with the same content
was still in the file. The count now happens where every backup is
written.
* fix(ui): keep the row icons as the only edit and remove actions
The labelled Edit and Remove buttons under an open row repeated the
icons and stood out too much, so they are gone and the icons stay
visible on open rows again. Each icon now has a tooltip that says what
it does.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(ui): put the import dialog's hooks on one card, with fewer lines and fills
The dialog mixed a grey rail, a grey footer, grey expanded rows and a
divider around every region, and the editor stacked its own Cancel and
Done above the dialog's. It read as cluttered, and a long JSON line
pushed the editor's controls out of the dialog.
The dialog now sits on the page background with the hook list, or the
editor, as one card. Rows are separated only by the list separator, the
row icons are neutral until hovered, and code is the only sunken fill.
One row is open at a time, and a single command no longer repeats its
event as a heading.
While a hook is edited, the dialog's footer holds the editor's actions,
so there is one row of buttons and Cancel returns to the list instead
of closing the dialog with the draft. Commands are sections of the card
and wrap instead of scrolling sideways. The dialog is larger.
The hint is one line, the edit note moved to the footer, and the name
field is labelled by where the name is used.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
* fix(ui): give the import review step the same card-on-ground look
The review step still had the white body, the grey footer and the
bordered summary box, so it looked like a different dialog from the
list it follows. It now sits on the page background with the summary
as one card, and the removal tile is neutral with only its icon in the
danger colour.
* chore: release as 0.30.9
Keep the next release on the patch version the maintainer asked for,
instead of the 0.31.0 that Release Please derives from the feat commit.
Release-As: 0.30.9
Windows has no sh on PATH, so every panel exec failed with "program not
found". A default Git for Windows install puts only Git\cmd on PATH, so
when sh cannot start the panel asks `git --exec-path` for the Git root
and uses its bin/sh.exe, which sets up the MSYS PATH itself. The shell
found is kept per machine, because a space's machine can run a
different OS than the window.
Under that sh, jobs printed their temp folder as /tmp/..., which Herdr's
native readTextFile cannot open, so every job waited out its 15 minutes.
READY now prints the cygpath -m form (C:/...) when cygpath exists; MSYS
sh accepts it too, and other platforms are unchanged.
Closes#922
prompt-injection-1 kept reporting ordinary source lines as CRITICAL
prompt overrides: `root: Path = Path(".")` (#921), docstring arguments
such as `root: Repository root containing the manifests.`, and typed
parameters with a name default. #376 and #750 each added value shapes
to the exclude. Measured on 5,573 real Python files and 33,006 Markdown
and config files, widening the exclude again cleared no line, and a
docstring entry cannot be told from prose by any value pattern.
In a source file a lowercase label word is a parameter, field or
docstring entry, so the built-in rule now matches only uppercase labels
there. The file extension decides, never a shebang, so a text file
cannot switch the check off. Markdown, text, config and extensionless
files, and Markdown code fences, keep the case-insensitive match. A
custom regex under the same ID is used as written.
This reverses the earlier choice that a lowercase `system: "..."` in a
non-Markdown source file stays CRITICAL.
Closes#921
When Agents hold different definitions of one server, importing one
Agent's version was refused with "unresolved conflicts prevented
adoption", because any conflict in the plan blocked it, including
another Agent's. The source was saved anyway, so the Agents that had
matched the old definition now conflicted, and importing from them
flipped the source back. Replace with source sent one resolution at a
time, so with two conflicts the plan stayed blocked and the dialog
could never apply.
Gate adoption only on the resolved entries' own conflicts, in the API
save and in the interactive CLI import. Replace with source now settles
every conflict of that server at once. After a conflict import, a
translated hint names the Agents in the same scope that still need
Replace with source, and the remaining adoption error is translated.
The Git and CLI groups listed command names on one line with no
summaries, so finding the command for a task meant opening each one's
help. Give them a row and summary like every other group.
Since #880, the Dashboard lists a tracked repository that is recorded in
metadata but not cloned on this machine, marks it "No checkout on this
machine", and its Uninstall removes only the record and audit acceptances.
The Dashboard row in the ui reference still described only checkout
uninstalls, so readers could expect the repo to move to trash.
Follow-up to #905.
The conformance script builds and serves skillshare and runs npm ci, which
the repository only allows inside a container, but nothing stopped it from
running on the host. It now refuses outside a container, with the same check
scripts/hooks/git-e2e.sh uses. Nothing referred to the script either, so the
testing topic now says when and how to run it.
The translated mcp reference pages left out the example URI the English page
gives for a skill root. All four now carry it.
The streaming UTF-8 check in the package loader was only exercised with a
rune split one byte before the read boundary. Two fixtures in the existing
directory test add the 2+2 and 3+1 splits, so a mistake in the carried-over
bytes shows up as a wrong MIME type.
The desktop app shows the dashboard in an iframe and passes its theme as
?theme=, which holds one value: it cannot ask for Dark + Clean or Playful
dark. Where the iframe's localStorage is not kept (WebKitGTK on Linux), the
dashboard then started with another theme, flashed it, and reported it to
the app as if the user had picked it (runkids/skillshare-app#128).
?mode= and ?style= now name one axis each and win over ?theme=, in both the
pre-paint script and ThemeContext, through one parser. The dashboard also
posts theme-init to its parent when a page starts, before the first
theme-change reports, so the app can tell a starting theme from a user's
choice even when the dashboard reloads itself.
The index and the draft builder read a skill's tags with different readers,
so the same SKILL.md could publish different tags depending on the path:
- The index accepted only the comma form (tags: git, workflow). A YAML list
became "[git" and "review]", and a block list produced nothing.
- Drafts accepted only a YAML list, so the documented comma form produced no
tags, and metadata.tags replaced the root field. After #901 the index
ignores metadata, which made the two disagree there as well.
Both now call readSkillTags. It reads the root field only, in either form:
a list comes from the decoded frontmatter, and the comma form from the
existing line scan. The scan also unwraps a one-line list, so a skill whose
frontmatter YAML rejects on another line (for example an unquoted colon in
the description) no longer publishes bracketed fragments.
Tags under metadata are custom data and are not read by either path. The
skill format page says so in all five locales.
Follow-up to #901.
IsRootFrontmatterLine took the caller's trimmed line only to test for blank
and comment lines, and its callers disagreed on how they trimmed it
(ParseSkillName trimmed spaces and tabs on the left, the rest trimmed all
whitespace). The helper now trims the raw line itself, so there is one
definition of a blank line and one argument fewer to get wrong.
Two tests added in #901 covered behaviour that change did not touch. The
ParseFrontmatterFields row is removed, and the ParseFrontmatterMap test is
reduced to the one case that guards what the skill format page promises:
nested metadata mappings and lists are kept.
Docs: the skill format page now recommends metadata for custom fields, but
the "Version tracking" example in creating-skills still showed top-level
version and author. It now matches. The sentence saying sync preserves
existing last_edited values is shortened, because skillshare has no such
field and the wording suggested it does. Both edits are applied to en, ja,
ko, zh-Hans and zh-Hant.
Uninstalling the _team checkout matched every tracked entry grouped as
"team", so a repo installed with --into team (team/_b) lost its record
and audit acceptances too. Since #880 keeps declarations that have no
checkout on this machine, reconcile could no longer restore that record,
and the next push removed it on every machine; only trash restore of
_team brought it back.
#880 already excluded _-prefixed repo directories from the legacy match
for unlink and declaration-only removal. Move that guard into
inLegacyRepoGroup so checkout uninstall and its trash copy follow the
same rule.
Fixes#898
TestDoctor_JSON_StreamDefersPluginCheck required the pending plugins
row to follow hooks directly. Git status also runs in the background
in a streamed doctor and is recorded at whichever check comes next,
so on a fast runner its result can land between hooks and plugins,
and the test failed on ubuntu CI (seen on #880). The order the test
guards is unrelated to Git, so leave git_status out of the list.
* fix(doctor): stop the plugin check from holding back later checks
The dashboard's Doctor page streams checks as doctor finds them, but the
plugin check asks each Agent's native CLI what is installed and can take
many seconds. Checks run in order, so backups, trash and the version
checks waited behind it while the page showed only an unlabeled skeleton
row, with nothing saying which check was still running.
When doctor streams, the plugin check now runs in the background. It is
streamed first as a "pending" row in its place, the checks after it
stream as soon as they finish, and its result follows. The full result
keeps the check in its original place. Text output and plain --json run
it inline as before.
The dashboard shows a pending row as the check's name with a spinner and
"Checking", replaces it in place when the result arrives, keeps it
visible under every filter, and drops the unlabeled skeleton while it is
shown. The /api/doctor/stream reference documents the pending row.
* fix(doctor): show the skill scan and Git status as running
Doctor scans the skill source before it streams its first check, and
runs git status on the source inline. On a large source either can take
seconds, and the dashboard showed only an unlabeled skeleton meanwhile.
A streamed doctor now sends a pending "source" row before the scan, and
runs the Git check in the background like the plugin check, so the
checks after it no longer wait. A finished background check is recorded
at the next check instead of at the end, so its row does not stay
pending after its result is known. The pending row now holds the
check's place in the result while it runs.
The 0.30.7 release adds `audit --respect-accepted`, so the README
"Latest" callouts in every language now point to it, and the release's
external reporter joins the contributors list.
An install whose audit cannot run, for example because audit-rules.yaml
does not parse, now fails with "audit scan failed", and --force does not
override it. The troubleshooting page only suggested --force for audit
errors, so it gains an entry for this error in English and the four
translated docs. The zh-Hant audit page also had the new
--respect-accepted flag row left in English.
* fix(install): report reinstalls from the same repo as skipped
checkExistingConflict read only the legacy .skillshare-meta.json
sidecar, which installs no longer write, so reinstalling a skill from
the same repo was reported as "already exists" and counted as failed,
contrary to the documented skip. It now reads the skill's record in
.metadata.json, falling back to the sidecar, and skips only the same
skill of that repo: another skill installed under the same name stays
a conflict instead of being reported as installed.
The dashboard logged an existing agent as installed and a same-repo
skill as failed. Batch installs now return those as skipped and log
them as skipped_skills, passing --into so a reinstall into a group
folder finds its record; the install dialog warns that they are
already installed. A same-repo tracked reinstall returns 409 and is
logged as skipped instead of a 500 logged as failed.
ss search installs, batch and single, log the names they skip, and
the Herdr panel reports skipped names like failed ones. The install
docs and their translations say that only the same skill is skipped.
* fix(install): install requested agents when the only skill is skipped
Reinstalling a single-skill repo with `-s alpha -a helper` returned as
soon as the skill was skipped as already installed, so the requested
agent was never installed while the command reported success. Both
single-skill branches now continue to the agent phase, as the
multi-skill path already does.
After #884, an install without --force keeps existing skills and agents
and names them in the --json skipped array, but the operation log
recorded only installed and failed names, so `ss log` could not show
what an install kept.
Record the kept names as skipped_skills for CLI installs and for the
dashboard's install-from-config action, and list them in `ss log`.
The config install starts with an empty list, so the dashboard log
shows no "null" when nothing was kept.
* fix(audit): report audit-rules load errors in global scans
The global scan entry points (ScanSkill, ScanSkillWithFollow,
ScanSkillFiltered, ScanFile) dropped the error from Rules() and scanned
with no pattern rules. One bad regex in the global audit-rules.yaml
turned every pattern check off with no warning, so audits reported
fewer findings than they should have (#879). Project mode already
returned the error.
Return the error from the global path as well, and name the failing
file in it: parse errors from loadUserRules and compile errors from
Rules() and RulesWithProject now carry the path. When a project scan
fails to compile, the global file is blamed only if it fails on its
own, so a project file that disables a broken global rule still loads.
The cached markdown split now takes the rules its caller already
loaded instead of loading them again and dropping the error.
* fix(install): block installs whose audit cannot run
Once global scans return rule-load errors, install treated the error as
a warning and installed the skill with no audit at all. update already
fails closed on a scan error, and --force there accepts findings, not
an install nobody could check.
A scan error now blocks skill, agent and tracked-repo installs and
removes what was installed. --force does not override it;
--skip-audit still bypasses scanning. The error wraps the new
install.ErrAuditScanFailed rather than audit.ErrBlocked, so install
output and the dashboard do not offer a --force retry that cannot help.
upgrade reinstalls the built-in skill with --force, which deleted the
old copy before the audit ran. A typo in audit-rules.yaml would have
left users without the skill, so upgrade now stages the download
through the update path and keeps the installed copy when the audit
fails.
update --all counted the new error as a silent skip. It is now listed
under "Blocked by security audit" with its reason and makes the run
exit non-zero. The install warning summary that counted "audit scan
error" warnings is removed, since nothing emits them any more.
Fixes#879
An install source typed as a URL can carry a token in its userinfo or
query, and operations.log stored it as typed, so anyone reading the log
or the dashboard's log view could see the credential (#878).
Redact in oplog.Write, which every CLI and dashboard writer goes through:
the source, oldSource and newSource args lose their userinfo, query and
fragment, and the message loses the same parts where an error echoes
them. The redaction reuses update's redactRepoURL, moved to
install.RedactRepoURL. It now also covers git+https:// and ssh://
passwords, and a source typed without a scheme such as
user:token@host/owner/repo, which install clones over HTTPS.
logInstallOp logged args[0] as the source, which is a flag when one comes
first (install --into team <url> logged "--into"), so the message was
never redacted. It now logs the parsed source.
Fixes#878
Release the pending fixes and the audit --respect-accepted addition as a
patch release, as the maintainer requested, instead of the 0.31.0 that
Release Please derives from the feat commit.
Release-As: 0.30.7
* fix(plugin): verify native support only for changes that run a command
prepareChange probed native command support before applying the
intentional skip rules. When the probe failed under update --all, the
change was marked as a failed target, so the later skip never applied.
An imported Grok plugin always hit this: Grok updates require native
trust, so every update --all exited nonzero even though Grok plugins are
documented as updated natively. #853 patched the same ordering for
imported OMP plugins only.
Run the probe after the skip rules instead, so a skipped change is never
verified, and drop the OMP-specific exemption it made redundant. Host
errors and changes that do run a native command still fail as before.
* docs(plugin): align OMP removal wording and runbook pass criteria
The translated plugin references said OMP removal requires a
scope-matching native registration. English, and the code, only require
that a registration match when one is present; a retry after native
uninstall proceeds from the retained cache. The runbook's Pass Criteria
also did not cover the two scenarios #853 added as steps 4 and 5.
* feat(audit): honor findings accepted with --force via --respect-accepted
install and update --force record the findings a user accepted in
audit_accepted, but audit ignored that record. A skill installed with
--force therefore kept failing `skillshare audit` in CI with no way to
let the accepted findings pass (#869).
audit --respect-accepted marks those findings as acknowledged. They stay
in every output (JSON acknowledged: true, a text/TUI note, "(accepted
earlier)" in Markdown, SARIF external suppressions), but they are counted
in summary.accepted instead of their severity and no longer fail the
audit. Without the flag nothing changes, so existing CI gates keep their
behavior. A changed file or snippet produces a new key and blocks again.
Tracked repositories record acceptances at the repo root with paths
relative to it, so ApplyAcceptedFindings walks up from each skill to
match them. The install, update and edit gates use the same function and
now honor repo-wide acceptances for skills inside tracked repos too.
The dashboard always honors accepted findings: the Audit page mutes them
and counts them apart, the skill Audit tab collapses them, and the
Dashboard attention card no longer lists a skill whose only blocking
findings were accepted. The CLI JSON summary and the server summary share
Result.CountOpenBySeverity so both count accepted findings the same way.
The oplog records the accepted count and the log views show it.
* fix(audit): match acceptances when a single file is scanned
A single-file scan names its findings by the file's base name, but the
ancestor lookup used the file's whole path as the prefix, so it hashed
SKILL.md/SKILL.md instead of the recorded SKILL.md. Auditing a skill file
directly with --respect-accepted, and auditing agents inside a tracked
repository in the CLI or the dashboard, still failed on unchanged
accepted findings. For a file target the prefix is now the file's own
directory.
* fix(ui): show health checks as they finish instead of after the slowest
The Doctor page waited for the whole `doctor --json` run before showing
anything. One slow check, such as plugin checks waiting on a native CLI
that does not answer, kept the page on a skeleton for 30 seconds, and the
server's 30-second write timeout could cut the response off entirely.
`doctor --json` now prints each check as a {"check": ...} line when the
internal _SKILLSHARE_DOCTOR_STREAM variable is set, before its usual
result. The new GET /api/doctor/stream relays those lines as Server-Sent
Events and sends the full result as `done`; it has no write deadline and
stops doctor when the client leaves. The page shows checks as they
arrive and replaces them with the final result.
* fix(ui): show the server's reason when a stream fails
The audit, diff and doctor streams send an `error` event with the reason,
but the shared EventSource helper treated it like a dropped connection
and showed only a generic message. It now uses the reason the server
sent, and keeps the generic message for a real disconnect.
* fix(doctor): skip Git reads in the hooks check when no hooks are configured
The hooks check loaded the full hooks inventory, which also scans
unmanaged native and Git hooks twice: about 12 git calls even with no
hooks configured, none of which doctor reports. Doctor now reads the
hooks section first and previews a sync only when there is something to
check.
Point every README release notice at check --exit-code and check --all, the headline CI changes in 0.30.6, and credit tomerzcod7 (#852) and ErykJakubik (#858), whose reports led to the git hook and project config fixes.
The security change in #861 added its provider-token paragraph twice to the install command page in all five locales; keep one copy.
The website builds for all five locales and context validation passes.
The row says skills check exits 1 on updates or local changes, while the Skillshare cell listed only check and update, which reads as if Skillshare cannot gate CI on drift. check --exit-code (#865) does that.
check <name> --json printed its warnings and the group expansion note on stdout before the JSON, so the output could not be parsed. When no name or group resolved it then printed an empty result and exited 0, while text mode exits 1, so a CI gate with a mistyped name passed.
With --json, check now exits 1 with an error object when nothing resolves, lists skipped names in a warnings field when some do, and reports every other failure (bad flag combination, missing config) as the same error object. Text mode is unchanged.
check --all is documented as checking both skills and agents, but it ran the skills check only. With --exit-code now available, a CI job using check --all --exit-code passed while an agent had drifted.
--all now runs both checks: the text output has a Skills and an Agents section, --json adds an agents array beside tracked_repos and skills, and --exit-code counts both. check --json and check agents --json keep their shapes.
--all is rejected together with names or --group. It used to be ignored there, and agents have no name filter, so honoring it would check one skill and every agent.
Before #863, `install <repo> -s <skill>` recorded "<repo>/<path>" as the
skill's source. GitLab, Bitbucket and file:// sources parse that string as
another repository, so every path that parsed the recorded source failed
for those skills: `update` of a single skill, `install <name> --update`,
the dashboard update, and the local-changes diff. #863 only changed what
new installs record.
The record still holds the repository and the path, so RecordedSource
rebuilds the source from them when the written string parses as a
different repository, and the reinstall writes the record back in the
form that parses.
In project mode the config entry that declared the old string follows the
rewritten record, because teammates install from the config. An entry a
teammate changed stays as it is, and so does a record a batch update only
respelled. The config is reloaded first: `update --prune` saves it through
another copy, and saving the stale one brought pruned skills back.
`hub draft` and `hub index` published the old string as it was written;
they now publish the source that installs the skill.
Closes#862
check exits 1 only when an item could not be checked, so a CI job that wants to fail on pending updates or local edits had to parse --json.
--exit-code makes a check that ran cleanly exit 1 when any skill, tracked repository or agent is not up to date. Only items whose status is local are left out, and the default exit status is unchanged. The operation log still records such a run as successful. The flag is rejected with --diff.
Bind provider credentials to canonical or explicitly configured HTTPS origins and preserve that policy across remote consumers. Reject cross-site credentialed reads, linked fallback directories, and discovered-agent writes outside the source; audit staged content before rooted atomic publication.
Add boundary regressions, private Git update coverage, stable cross-platform fixtures, and aligned documentation. Verified the integrated main baseline with all executed CI checks passing.
* fix(install): record a per-skill source every host can install again
`install <repo> -s <skill>` joined the repository and the skill path with
a single "/". GitLab and Bitbucket URLs have no fixed depth, so the parser
read the result as a longer repository path, and file:// URLs only split
on "//". The recorded string is what a project's config.yaml shares, so
`install -p` on a fresh clone tried to clone a repository that does not
exist.
Whole-repo file:// sources now join with "//", and GitLab or Bitbucket
sources typed without ".git" or a web URL marker join with ".git/". The
other hosts keep their form.
`install --update` still recognises a record in the old form, but only
when its recorded repository and path agree, because on these hosts the
same string can also name a repository of its own. The dashboard's
install dialog matched installed skills by rebuilding the old form, so it
now accepts each form the server writes.
Closes#859
* fix(ui): mark hub results installed under the new recorded source
A hub entry that names a repository and a skill was matched against the
installed skills by an exact source or a "<source>/" prefix. A GitLab or
Bitbucket repository typed without ".git" is now recorded as
"<source>.git/<skill>", so the search row and the preview kept offering
Install, and a second install hit the already-exists warning.
The matcher now accepts the ".git/" join as well. This is the same class
as the discovery list fixed in the previous commit: both rebuild the
recorded source in the dashboard. No other dashboard or Go code matches a
recorded source by prefix.
* docs(comparison): re-pin the npx skills comparison to v1.8.1
The comparison and migration pages cited skills v1.7.6. Since v1.8.0
the restore command links restored skills into agent directories, so
the page's statement that it does not was wrong. The page also did not
say that `skills install` with no source is the same restore command,
that matching skills only get their missing agent links, or that
`skills check` exits 1 on updates or local changes.
Re-pin both pages and their four translations to the v1.8.1 tag commit
and correct those statements against its CLI reference. The lock paths
and fields the migration guide names are unchanged in v1.8.1.
* chore: ignore .feature-radar/
The feature-radar skill keeps its tracking notes, including assessments
of other tools, in .feature-radar/ at the repository root. They are
local working notes and should not be committed to the public
repository.
In project mode the committed config.yaml is what teammates install from, but
it could disagree with what a machine actually has (#858):
- `uninstall -p` and the dashboard's single-skill and tracked-repo removal
left the skill's entry in config.yaml, so a later `install -p` brought it
back. They now drop the entry and the lock pin through one shared
config.ForgetProjectSkills, as the uninstall docs already promised.
- Installing a skill again from another source or branch (after an uninstall,
or over the copy with --force) updated only the gitignored .metadata.json.
config.yaml kept the old source and skills.lock.json ended with the old
source and the new commit. Installs from a named source (CLI install,
search, dashboard) now compare the records from before and after the
command and let the config entry follow the skills it actually reinstalled.
Install from config never rewrites an entry from local records, so a
teammate's edit survives on a machine that has not updated yet.
- Reconcile removed every config entry that had no folder and no record. On a
fresh clone nothing is installed yet, so `install <source> -p` deleted all
the other declared skills. An entry now goes only when the skill was
installed here and its folder is gone, when it was moved, or when a command
removed it; `move` passes the old paths and `update --prune` cleans the
config itself.
Preserve the complete Layout while adding a standalone Mod named skillshare. Generate both packages from one canonical mod and protect custom layouts and usage meters during installation and updates. Keep release versions aligned and route native Herdr instructions separately within existing context budgets.
Reject invalid audit output and CLI errors before accepting absent findings, including integrity and traversal checks. Require completed mutation runs to fail the single and batch update gates rather than accepting unrelated failures.
Build gate mutations with a private Go overlay and binary so failures cannot leave source or the shared binary weakened. Add regression coverage for assertions, signal checks, and source/binary isolation to every red-team Make target.
* fix(git): keep a caller's GIT_DIR out of skillshare's git commands
Git exports GIT_DIR, GIT_WORK_TREE, GIT_INDEX_FILE and related variables
to hooks that run in a linked worktree. Every git process skillshare
started inherited them, and those variables override the directory the
command runs in. Run from a post-checkout or post-merge hook, skillshare
therefore acted on the hook's repository instead of its own: install's
sparse clone turned on sparse checkout there (a later merge removed every
file outside the skill's path), the remote tree check's `git init --bare`
made it a bare repository, install's reconcile recorded its origin and
branch, and push staged and committed into it.
internal/gitenv builds git commands without the variables that
`git rev-parse --local-env-vars` lists for choosing a repository, work
tree, index, object store or config file. GIT_CONFIG_COUNT and
GIT_CONFIG_PARAMETERS stay, because users pass credentials through them
and install's token auth appends to the existing count. Every git call in
cmd/skillshare, internal/install, internal/git, internal/check and
internal/config now goes through it, and plugin runCommand starts native
CLIs from the same environment because they run git as well. The hooks
service keeps its own stricter filter.
Closes#852
* test(gitenv): fail on new git commands that bypass gitenv
Each git call site converted for #852 is safe only because it goes
through gitenv.Command, and about half have no test of their own. A
future exec.Command("git", ...) would silently bring the bug back, so a
syntactic guard now rejects one outside gitenv, hooks and testutil,
mirroring the sourcefs and sourcewalk ratchets.
The Environ test also checks a lowercase name, since Windows environment
names are case-insensitive, and compares against literal keys so that
removing one from repoVars fails it. The wiki records the rule.
* fix(herdr): load panel resources progressively
Publish independent resource and source reads as they finish so a slow native plugin inventory cannot block the entire panel. Preserve cached rows while keeping pending and failed sync states explicitly unconfirmed across scopes and previews.
Keep machine upgrade and pull/sync spinners on their owning actions, and cover partial reads, retries, scoped failures, and rendered states with regression tests.
* fix(herdr): retain actionable overview rows during refresh
Keep previously actionable cached rows in an unconfirmed section while their reads are pending or failed, rather than hiding them when their sync state becomes unknown. Cover both states with a rendered regression test.
The manual check result sat in a detached note below the card, with
Update now floating beneath it, so the outcome read as unrelated to the
setting. The row now shows the installed CLI and skill versions, the
check status with its time, and the next action together, and wraps on
narrow screens. Copy is updated in every locale.
Release-As: 0.30.6
Refresh all README release notices and route agents to the new updates command. Clarify that desktop policy controls require a compatible App release; the CLI upgrade alone cannot change older desktop builds.
The website builds for all five locales, context validation and skill validation pass. The documentation diff passed five local review passes.
Add a global automatic-update preference with an environment override, CLI controls and dashboard settings. Suppress automatic release checks and cached notices while retaining explicit checks and upgrades.
Recheck policy before publishing in-flight results, preserve structured JSON errors, and reject incomplete manual checks. Include schema, completion, localization, documentation and regression coverage.
Closes#846.
The docs still showed the old `{"skills": [{"name", ...}]}` layout, which
no current release writes; the file is `{"version", "entries", ...}`
keyed by path. Readers comparing the docs with their own file had no way
to tell what `audit_accepted` or `target_overrides` are for.
tracked-repositories also said project mode records `tracked: true` in
`.skillshare/.metadata.json` so teammates get it, but that path does not
exist and project mode gitignores the metadata files (#760); the flag
lives in `.skillshare/config.yaml`.
The example `type` is `github-subdir` because a subdir install records
that, and the field table omits `into`, which nothing writes.
The per-Agent update summary in the sharing guide and the built-in skill named every Agent except OMP, which could not update before #837. Say that an OMP update removes its own installation and reinstalls the reviewed commit, as the command reference already does, in English and the four translations.
Auditing a parent skill checked every Markdown file's bundled references
against the scan root. A nested skill's `references/ok.md` was looked up
under the parent and reported as a dangling link, and its `../SKILL.md`
stayed inside the parent and was not reported as an escape, so a parent
audit disagreed with a direct audit of the child.
Each Markdown file now records the nested skill that holds it, and its
references are resolved and contained within that skill.
doctor scans a nested skill on its own and again inside its parent, so
it repeated the child's findings. It now reports each finding once.
Closes#834
* feat(herdr): enable and disable skills and agents from the panel
The Library lists disabled skills under Off, but the panel had no way
to turn one back on or to turn one off: that meant leaving Herdr for
the CLI or the dashboard.
A skill's or agent's preview now offers Disable, or Enable when it is
disabled. It asks first, then runs skillshare disable / enable with the
entry's own path, the pattern the dashboard writes, so enable removes
exactly what disable added. The next sync applies the change.
Exit 0 only means the entry's own line was written or was not there. A
glob, a folder pattern or a negation in the .local file can still
decide the other way, so the panel reads the list afterwards and
reports an entry that did not change instead of claiming success.
The confirm dialog shares the hook dialog's branch under the role
"able": "toggle" is already the tab-bar button's role, and an overlay
opened with it draws that button.
* feat(herdr): show an operation's outcome before skillshare answers
Every operation waited for the CLI and then for the next full read
before a row moved, so a click looked like nothing happened for
seconds.
The panel now lays its running requests over the rows it has read. A
disable, an enable, an uninstall and a hook change show their outcome
at once, and a finished install lists its skills without waiting for
the read. An update and a sync can be stopped by an audit or a failed
target, so their rows only say "updating…" or "syncing…" rather than
claim a result.
A request that fails is dropped and the rows go back. Otherwise the
first read that starts after the request ended replaces the guess; a
read already in flight when it ended is followed by another, which
also closes the gap where the post-operation refresh was skipped and
the list stayed stale until the next poll.
Git sync, upgrading skillshare and updating the panel are not guessed:
their result depends on the remote.
* refactor(herdr): decide the pending requests' fate in the model
Which optimistic rows survive a read, when an update's rows give way to
the checks, and whether another read is needed were decided inline in
main.js, which the node tests cannot load. herdr/AGENTS.md asks for new
logic in tested modules and main.js kept to views.
shownRows, endedRequests, afterRead and afterChecks now hold those
decisions in model.js; main.js only stores the list. Tests cover a
request ending during a read, a read newer than the request, an update
waiting for the checks, a failed request dropped, and another machine's
request.
Expose selected skill names and repository-relative paths in dry-run JSON so the panel follows CLI discovery, ignore rules, and canonical names. Refuse ambiguous plans and treat nonzero install exits as failures even with legacy JSON output.
Closes#838
Release-As: 0.30.4
* feat(herdr): name the targets behind a collapsed map line on hover
The Overview map draws at most six lines, so with more targets the last
line reads "2 others" or "+3 more" and the panel never says which ones.
Finding out meant opening a preview's Targets tab.
Resting the pointer on such a line now opens a hover card listing those
targets with the same dot, mark, name and state a line of its own would
show. It uses the kit's HoverCard, so there is no motion of our own to
tune: a hover this frequent should stay quiet.
* test(herdr): close the collapsed-line test after the merge
The Library lists disabled skills under Off, but the panel had no way
to turn one back on or to turn one off: that meant leaving Herdr for
the CLI or the dashboard.
A skill's or agent's preview now offers Disable, or Enable when it is
disabled. It asks first, then runs skillshare disable / enable with the
entry's own path, the pattern the dashboard writes, so enable removes
exactly what disable added. The next sync applies the change.
Exit 0 only means the entry's own line was written or was not there. A
glob, a folder pattern or a negation in the .local file can still
decide the other way, so the panel reads the list afterwards and
reports an entry that did not change instead of claiming success.
The confirm dialog shares the hook dialog's branch under the role
"able": "toggle" is already the tab-bar button's role, and an overlay
opened with it draws that button.
With a newer release published, the panel's header drew "Update panel"
on top of the folder and machine pill: at the panel's 400px the row has
no room for both, and the pill did not shrink, so the two overlapped.
Seen in a running Herdr with version.js set below the latest release.
The pill is now a plain element that shrinks and ends in an ellipsis,
so the button, the version and the close button keep their place.
panels.png gains the button in the first view, drawn as the running
panel shows it, with the pill shortened.
The panel had no version and no way to update: a user had to copy the mod folder again by hand and could not tell when a newer one existed.
The panel now carries version.js, the skillshare release it shipped with, which Release Please rewrites in every release. While shown it asks once an hour where GitHub's "latest release" link lands and offers "Update panel" when that release is newer. It compares against the published release, not main, because the panel parses the CLI's --json output and a panel from main may need an unreleased CLI.
The update clones only the mod's folder at that tag and copies it over the installed one. It first checks the folder holds the running panel's version, keeps the replaced files once in .bak-update-<version>, and holds every machine's lock until the reloaded panel returns it, because Herdr's reload ends every running task.
* feat(herdr): answer "what needs me" first and preview every row
The panel listed every resource in one long tab and put the detail of a
row in text under it, so the first screen never said whether anything
needed a sync, and a 400px column filled with wrapped lines.
Overview now leads with one headline, one Sync button and a map from the
source to every target, and lists only what needs attention. Library
holds the full lists. A row carries a name and one short state; clicking
it opens a preview dialog with its document, its targets and its
details, so nothing is crammed into the list. MCP previews show the
names of env, header and token entries, never their values.
Target names come from `status` as well as `diff`, because `diff` leaves
out targets that share another target's folder. A machine with
uncommitted or unpushed work offers Sync both ways, since a plain pull
would refuse there. Warnings and errors now clear after 8 s instead of
staying until closed. Dialogs draw their own card and fade in and out.
The map's lines, the target list and the machine's action live in
model.js with tests; rowSub and the hideDisabled filter had no caller
left and are removed.
* fix(herdr): list only the targets a previewed item can reach
The preview's Targets tab was wrong in two cases.
A skill already on some targets but new to one has the state "missing",
and the preview treated that state as "waits everywhere", so targets
already in sync were marked as needing a sync. Only the targets the
item's drift names wait now.
An agent's preview listed every configured target, including ones that
take no agents, as in sync. The loader now keeps the targets that take
skills and the ones `status` reports for agents apart, and the preview
uses the list for the item's kind.
* feat(herdr): sync from Library's waiting group
The redesign left Sync only on Overview, so someone reading the Library
list had to switch tabs to act on the rows in front of them. The
"NEEDS SYNC" header carries Sync again, for the scopes its rows wait in;
when only a hook notice has native changes, its header carries it.
* fix(herdr): keep Sync in Library's toolbar and stop the panel shrinking past its tabs
Sync on the "NEEDS SYNC" header only existed while something waited, so
with everything in sync Library had no way to sync at all. It now sits
in the toolbar beside the filter, primary while something waits.
The panel could be dragged down to 320px, where the tab row no longer
fits beside the scope switch and the switch is cut off. The column's
minimum is 380px, and the tab row is a little tighter.
* fix(herdr): sync every scope a target still waits in from Library
Library's Sync chose its scopes from the waiting rows alone. A target can
wait with no row left, as after uninstalling a project skill that a
copy-mode target still holds, so with All shown and one global row
waiting, Sync ran in the global scope only and left the project copy in
place. Overview already added the scopes with a waiting target.
Both now take their scopes from one model helper, syncScopes, which
covers waiting rows, waiting targets and the nothing-waiting fallback.
* refactor(herdr): finish the review's open findings on the panel
The first review left confirmed findings listed but unfixed, and the
commits after it were never reviewed. This closes both.
The map now counts a waiting MCP server, plugin or hook on the targets
it waits on, so its lines no longer stay green under a headline that
says something waits. A skill's Targets tab takes its targets from
status when status names them: diff also lists targets that take agents
alone. Library's Sync stays disabled until a scope has been read;
before that it sent an empty scope list and reported a sync that never
ran.
The map's trunk and lanes, the two pill switches, the placeholder block
and its pulse each had two or more copies in main.js and now have one.
The Overview headline, a machine's remote line and its waiting targets
move to model.js with tests. README's layout snippet names the 380px
minimum the layout file already has.
* fix(plugin): let OMP and Pi plugin updates through without uninstalling (#833)
Every OMP update was blocked, because OMP's native upgrade replaces cache
folders that projects outside its inventory may still use. The only way to
move an OMP binding to a new commit was to uninstall first. An update now
runs the same pair a source change already uses: the scoped removal
adapter (cache kept), then an install under a fresh marketplace and cache
identity. A refresh always takes a new identity, because OMP installs from
the catalog it cached when the marketplace was added, and that catalog
still names the old version. If the removal cannot be verified, the
update is blocked; update --all still skips it with the reason.
Pi was blocked whenever the catalog plugin name differed from its
package.json name. That happens after an upstream npm rename, for example
when npm refused the original name. Pi installs by path, and Skillshare
keys the binding by the catalog name, so the npm name never reaches
either, and the check only stopped working installs.
Updating one package across several Agents stopped every Agent as soon as
one was blocked. Each failing Agent is now reported with its reason while
the others update, and the command exits non-zero. A single --target, or
a package with no other Agent to update, stays blocked as before, so a
dry-run still fails when nothing would update.
* fix(plugin): let one update --all refresh several OMP packages
Every OMP removal proves itself against a fingerprint of the whole native
registry and lock. In a single update --all plan, the first package's
removal and reinstall rewrite those shared files. The second package's
removal therefore saw "OMP native files changed", so only one OMP
package could update per run. The same applied to a sync that replaced
the sources of several OMP packages.
A removal now also fingerprints only its own installation: its registry
entry, its lock entry, its package manifest and its runtime link. After
an earlier change in the same apply has written to that OMP target, the
removal re-reads the files and runs every ownership check again. It goes
ahead only if that own fingerprint still matches the preview. A change
outside Skillshare to the package's own entries still blocks it. Without
an earlier write in the apply, the full-file check is unchanged.
The fake OMP in the tests now merges installs into the registry and lock
and lists them in a stable order, as the real one keeps other plugins.
Scripts and the herdr panel could not tell why an uninstall or install
failed: uninstall --json had no error field, project mode ignored --json
(printing text and still prompting), and a multi-skill or config install
in which every skill was blocked exited 0.
- uninstall --json (skills and agents, global and -p) sets "error" with
each failed name and reason; skills exit non-zero when all fail,
agents when any fails. Project mode now emits pure JSON, including on
the first run that initializes the project.
- uninstall -p agents parses its flags instead of treating --help or an
unknown flag as an agent name, and uninstall agents --json is logged.
- install exits non-zero, naming each skill and reason, when every skill
from a source or from config fails; installed or skipped skills make it
a partial success that still exits 0. Config installs show each
failure's reason, and the dashboard logs an all-failed run as an error.
- herdr asks for JSON in project scope and shows the CLI's error.
Compare npx skills v1.7.6 against verified capabilities instead of an install-only model. Position Skillshare around broader resource management and document experimental restore and npm sync limits.
Clarify migration ownership, backups, source tracking, ref preservation, and initialization safety across English and four translations.
A third of the repository's visitors arrive from herdr.dev and land on
herdr/skillshare, where the README opened with install steps and no
picture, and never said what skillshare is or linked back to it. The
recipe's first paragraph, which the Herdr gallery shows as the layout's
description, did not mention the Machines tab.
The preview was also stale: it predated the Hooks kind and the
List / By source switch. Redraw it from the design board, add a
three-view picture for the README, and refresh the copies that follow it.
install --json printed empty skills and failed lists with exit code 1
when the whole install failed, for example when the security audit
blocked a tracked repository or a single skill. Scripts and the herdr
mod could see that it failed but not why, and the mod already reads an
error field that was never set.
The install JSON now carries the command error in an omitempty error
field, in global and project mode. The install docs also stop saying
--json implies --force: it only permits overwriting, and the audit gate
still applies unless --force is given.
Tracked install and update audit the whole repository root, and the
scanner treated every file below a hidden directory as header-only. Skills
that discovery finds in hidden directories, such as .curated/<skill> and,
since #801, a repository-root .agents/skills/<skill>, were therefore synced
to every target without a text scan.
The hidden-directory boundary is now measured inside the skill that holds
a file, so those skills get the text scan they already get when audited one
by one, while target copies such as .claude/skills and hidden folders
inside a skill stay header-only.
Release-As: 0.30.3
Share portable MCP definitions with Hermes through its native YAML configuration while preserving unrelated settings and managed-entry safeguards.
Support explicit Hermes homes and native OAuth options without copying credential state, and expose the target consistently in the dashboard, schemas, completions and documentation.
Refs #825
The Clean style read flat next to the Apple-style design: menus, the
shortcut HUD and the stuck toolbar were opaque slabs, and most layers
vanished the instant they closed. Pages, cards and the sidebar stay
solid; only layers that float over content become translucent, and
prefers-reduced-transparency turns them solid again.
Menus now fade out instead of unmounting at once (usePresence), the
segmented-control pill slides between segments, and switches, the pill
and the tree divider move on critically damped or lightly bouncing
spring curves. Dialogs and the floating selection bar are often
unmounted by their callers, so exitGhost plays their exit on a frozen,
inert copy; no copy plays when the page goes with them, and reduced
motion gets a short fade. Toast, collapse and row-exit timings follow
the motion spec, and the toast countdown pauses in place on hover.
With git_root: root, commit and push aborted on every tracked skill repo
because NestedRepos flagged any directory with its own .git. Tracked repos
are listed in the managed .gitignore block, so git add -A never stages
them, and the suggested remedy (renaming .git to .git.disabled) breaks
skillshare update for those repos.
NestedRepos now asks git check-ignore about each nested repo and leaves
out the ones git ignores and does not track. A repo already committed as
a gitlink is still reported, since staging would update it. Paths are
checked one at a time because git refuses a whole batch when one path
lies inside a gitlink, and any git error keeps the warning.
Closes#820
docker-sandbox-online failed whenever a commit landed on main while
TestUpdate_TrackedRepo was cloning runkids/skillshare (about 45 seconds).
The update then pulled that commit and the audit rejected the candidate:
.devcontainer/bin/dev-servers was an absolute symlink to
/workspace/.devcontainer/dev-servers.sh, which escapes the checkout. The
same block hits anyone who tracks this repository and updates it.
Point the symlink at ../dev-servers.sh, which resolves to the same file in
the devcontainer. The test no longer expects "up to date", because a
concurrent push is outside its control; it checks that the update
succeeds and passes --force for the same reason the install does: the
repository carries audit fixtures, and the test covers track and update
mechanics, not audit policy. The token-auth variant gets the same --force.
The severity counts are filter toggles but had no hover, press or
selected look, so an active filter showed only as a blue number. The
scanning note and the LOW/INFO rows popped in and out, shoving the
results around; they now grow in and shrink away. The note waits 400ms
before growing, so a quick rescan after a threshold change no longer
bobs the list down and back up. The scan progress bar eases forward like
the other bars, and Playful's hover lift is limited to fine pointers so
a tap does not leave a control stuck out of place.
The filter's label sat above the select, so in a row centred on the
whole field the "showing 5, hiding 13" counts floated between the label
and the box. The name now goes inside the trigger as a prefix, as on
the audit rules page, so the select and the counts share one line. The
control keeps its accessible name.
Every page faded in over 200ms while sliding up 8px. Moving between
pages in the sidebar is the most frequent action in the dashboard, so
the slide made each click feel slow and shifted the content the user
was comparing. Pages now use animate-page-in, a 120ms opacity-only
fade, which softens the swap without delaying it or moving anything.
The shared fade, dropdown and dialog entrances also ignored
prefers-reduced-motion and kept sliding or scaling. Under reduced
motion they now keep only their fade; a dialog changing step still
swaps without animation, as before.
The frontend wiki and the UI style skill told contributors to put
animate-fade-in on page roots; they now name animate-page-in and keep
animate-fade-in for in-page reveals.
Release-As: 0.30.2
The switch knob now slides by transform, but the mixed state still
centred it with justify-content. Going from on to mixed moved the knob
to the centre at once while its 14px transform eased back to zero, so
for a few frames it stuck out past the track's right edge. A folder
switch in the skill tree hits this when one child is turned off.
Mixed now centres the knob by transform too, so every change between
off, on and mixed is a single slide that stays inside the track.
Several controls changed state with no motion, which made them feel
unresponsive: a button gave no sign it was pressed, a switch knob jumped
to the other end, the bulk-selection bar popped in, and the copy menu on
the memory page appeared at once. Toasts also left sideways although
they come in from below.
Buttons now scale down slightly while pressed; playful buttons sink
onto their hard shadow instead. Switch knobs slide across the track,
the bulk bar rises from the bottom edge, the memory copy menu uses the
existing dropdown entrance, and toasts leave the way they came in, in
200ms. Reduced-motion settings keep the bulk bar and toasts to a fade.
The skill detail page kept two fixed columns at every width: the
SKILL.md view beside a 330px info card, and a 240px file tree beside
the file viewer. On a phone the info card covered the content and the
content column shrank to a few characters. Below 1024px the columns
now stack.
The tab bar's preview/raw toggle squeezed the tabs onto two lines at
phone width; controls that do not fit now wrap above the tabs and stay
right-aligned, so the tabs keep their underline. The project Hooks tab
already wrapped this bar with its own flex-wrap, which the shared rule
now covers.
The page header kept the title and its action buttons on one row, and
the buttons do not shrink. At phone width the buttons took most of the
row, so the subtitle was squeezed to one character per line (the Skills
page at 390px). The title now keeps at least 280px and the actions wrap
below it when they do not fit; desktop layout is unchanged. The Hooks
page's own flex-wrap override is no longer needed.
After an install, the warnings dialog put lines like "audit findings
at/above block threshold (CRITICAL); proceeding due to --force" and
"recorded 1 accepted finding(s)" in the findings list as rows with an
info icon, in untranslated English. They read like findings without a
severity, and a forced install showed each skill's status twice among
its findings.
Status lines now sit in a note above the list, grouped by skill, and
the four audit status lines the installer writes are translated. The
list holds only findings.
Credential-access rules match whole lines, so a Python docstring that
named ~/.aws/credentials in a `cat` example counted as a CRITICAL read and
blocked the mcp-sentinel skill at the default threshold (#817).
In .py files, a built-in CRITICAL credential-access match on a comment-only
line, or inside a string that is a whole statement such as a docstring, is
now HIGH: it still shows, and still blocks under a HIGH threshold. A small
tokenizer decides this and keeps CRITICAL wherever it cannot be sure the
line never runs: argument, assigned and bracketed strings, f-strings and
their replacement fields, code before a trailing comment, files that read
__doc__ or use bare CR line breaks, and explicit severity overrides.
A lowered finding carries severityContext "python-inert" (JSON, SARIF,
`audit rules --format json`), and the dashboard, CLI text output, both
audit TUIs, install/update warnings and the markdown report say it was
lowered from CRITICAL, so it is not mistaken for a changed rule.
Closes#817
On a Homebrew install the dashboard runs from a versioned keg that `brew upgrade` removes, so the restart after "Update now" exec'd a deleted path. It now restarts through <prefix>/bin/skillshare, which Homebrew keeps linked to the installed version.
Fixes#815
The pending range adds one small dashboard button (#814) and a plugin
check speed-up (#812). The maintainer wants it shipped as 0.30.1 rather
than the 0.31.0 a feat commit would select.
Release-As: 0.30.1
The Hubs page keeps a hub's skill list for two minutes and does not
refetch on window focus. The server reads the index fresh on every
request (git hubs are re-cloned), so after someone pushes an updated
skillshare-hub.json the only way to see it was to wait or reload the
whole page.
A refresh icon button next to the filter refetches the list on demand.
It spins and is disabled while loading; the current list stays on screen,
and a failed fetch shows the existing error note above it. Your own
(draft) Hubs are local and do not get the button.
* perf(plugin): check every plugin at once and skip sources that did not move
The Plugins page's update check read every Agent CLI, cloned and hashed
every source, and asked npm about every package one after another, so it
grew with each plugin added. A single Agent CLI that stopped answering
held the whole page at "Checking for updates" with no way to tell which
plugin was stuck.
The check now asks every Agent and checks every plugin at the same time.
Plugins share one read of each Agent and each source, so an Agent with
many plugins is still asked once, and a plugin waits only on its own
Agents, including when proving its own leftover installs. Before downloading a remote source with no pinned ref, the
check asks the remote which commit its default branch points at with
`git ls-remote` and reports no update when that is the installed commit.
A check of three unchanged GitHub plugins on two Agents went from 4.3s
with three clones to 0.6s with none.
The dashboard reads the check from a new stream, GET
/api/plugins/check/stream, that sends each plugin as soon as it is
checked. The page marks rows as they arrive and counts progress in the
header. The stream stops waiting after 60 seconds: a plugin bound to an
Agent that has not answered by then shows "Check failed" with the
reason, and plugins on other Agents are unaffected. There is no limit on
how many plugins run together, because plugins waiting on a hung Agent
would otherwise hold every slot and starve the rest.
A cancelled command did not return when the Agent CLI was a shim that
starts the real client, such as an npm, mise or volta wrapper: killing
the shim left the child holding its output, so the command waited until
the child exited and no timeout took effect. Commands now stop waiting
for output two seconds after they are cancelled; a command that exits on
its own while a helper keeps its output open still counts as answered.
* fix(ui): offer every update the Plugins page shows in the update dialog
The header counted updates from the per-plugin marks, but the update
dialog offered only the targets in the last completed check's plan. Two
cases left the header saying Update N with nothing to tick in the dialog:
a first check that broke off after finding an update never set the plan,
and a recheck that could not reach an Agent kept that Agent's earlier
update while the plan said blocked.
The dialog's plan is now derived from each plugin's last answer together
with the kept updates, so a kept update stands in for the blocked or
missing answer and both always agree. A broken-off check also keeps the
answers it did receive.