skillshare never fetches submodules, so a gitlink is an empty directory
after any clone. Installing that path reported success with nothing in
it, a path inside it failed with a misleading "does not exist", and
whole-repo discovery dropped its skills without a word.
Refuse a subdir that is or lies inside a submodule, naming the
submodule, its pinned commit and upstream URL, and warn for each
submodule skipped by whole-repo discovery and --track.
Refs #433
Release-As: 0.25.1
The pages added with the block modes covered what they write, not what
the review fixes made them do. The sharing guide still said sync
overwrites a modified target, which is wrong for a block: sync stops
until the edit is collected or the block is rewritten.
The guide, the extras reference and the built-in skill now cover the
block's Collect and Rewrite choices, block statuses, the target file
dialog, what a mode change removes, how restore treats a block, and
the cases a block target is refused. Common errors gains an Extras
section for the four new messages. The --mode help of extras init,
--add-target and the mode command listed only import among the
single-file modes; it now lists prepend and append too.
Refs #436
The AGENTS.md tab and the instructions API only knew import, symlink
and copy, so a tool without @import could hold one shared file and had
to give up its own instruction file to do it.
The mode picker now lists prepend and append first among the modes that
keep the tool's own file, with import; symlink and copy stay blocked
once a target holds another shared file in a managed part. A target
whose file already holds a block defaults the next shared file to
prepend; the first connection keeps the link default the existing
tests and the memory guidance rely on. The row hint says the target
also uses the other files instead of claiming one replaces the other,
and the modified-state note, Collect and Reapply name the block rather
than the whole file, since only the block is read back or rewritten.
The connect and restore previews describe what a block does to the
target file.
Refs #436
Tools without an @import directive (codex, gemini, cursor) could only
take a shared instruction file as a symlink or copy, which replaces the
target's own file. Teams that want one shared AGENTS.md plus the user's
own notes in the same file had no way to express that.
prepend and append write the source into the target file as a managed
block fenced by skillshare:extra markers that carry the source path and
a content hash. Sync inserts the block once and then rewrites it in
place, status reports modified when the block body no longer matches
its hash, Collect copies the edited body back to the source, Reapply
rewrites the block from the source, and restore removes only the
block. Lines outside the block, and markers inside code fences, are
never touched. Several managed blocks (and an import line) may share
one target file; the connection validator only rejects a file when a
replacing mode (symlink, copy, merge) is involved.
Refs #436
Bring the pages, the built-in skill and the translations up to date with
the pending release before the Release PR is reviewed: the README Latest
callouts for v0.25.0; mcp serve, Oh My Pi, DeepSeek Harness and GitLab Duo
in the ja, ko, zh-Hans and zh-Hant pages; the `--` option and the --enable
rollback of link and unlink; the missing serve skip reasons and its
cross-origin refusal; standard naming rules; junctions kept across volumes;
OMP accounts receiving native code hooks; and the 79-target count.
A non-loopback --http listener accepted a bearer token over plain HTTP,
so anyone on the path could read the token and the skills. Off loopback
it now also needs --tls-cert and --tls-key and serves HTTPS; loopback
stays plain, so a TLS-terminating proxy in front still works.
The Agent Skills format caps compatibility at 500 characters, and hosts
that validate entries reject longer ones, so serve skips such a skill
with a warning, as it does for an overlong description.
metadata is deliberately not held to the format's string values: lists
there are common, tool-fallback clients read them fine, and skipping
those skills would hide them from every client to satisfy a few.
A managed project's name may hold spaces, so the Skillshare tab built
`--target my app@claude`, which the save path split into two words and
serve rejected as an unknown target. The command is now joined from
quoted words.
The Agent Skills format caps a description at 1,024 characters, and
hosts validating entries reject longer ones, so serve skips such a skill
with a warning instead of advertising it. The docs list every skip reason.
Serving skills over MCP is meant for people who do not want to type the
command, so Add server gets a Skillshare tab next to the fields and the paste
tabs. It asks only for a name, which skills (all enabled ones, or one skills
target's selection) and the Agents, and shows the command it will run. It
marks the Agents that already get skills by sync, including through another
target's folder such as ~/.agents/skills, and warns when one is ticked,
because that Agent would see each skill twice.
Editing a server that runs skillshare mcp serve opens the same tab, in the
global page and under mcp.projects. The tab is named after Skillshare rather
than skills so it can hold more of what skillshare serves later.
Agents on a disposable VM, in a hosted assistant or behind an MCP gateway can
reach an MCP endpoint but not the folder skills sync to, so they got tools and
none of the user's skills (#428).
`skillshare mcp serve` is a read-only server for the skills skillshare already
manages. It declares io.modelcontextprotocol/skills and implements skills/list,
skills/get and resources/read: one entry per skill, its URI from the source
path, the full frontmatter, and every file with a sha256 digest and size.
--target applies that target's selection, and the source is reread at most
every 5 seconds so install, update, enable and disable show up without a
restart; unchanged files keep their digest. stdio is the default; --http
serves Streamable HTTP and needs SKILLSHARE_MCP_TOKEN off loopback.
Skills the extension cannot carry are skipped with a warning instead of being
published incomplete: a name that breaks the Agent Skills rules or differs from
its directory, more than 512 files or 16 MiB, or a nested skill that is not
served. --check lists them without serving. The naming rules moved to
internal/skillpkg so sync and the server share them.
Few clients support the extension yet, so the server also offers list_skills
and read_skill tools. A client that declares the extension does not see them,
so it never gets each skill twice.
sync.SelectTargetSkills is the one place that turns discovered skills into a
target's selection (enabled, include/exclude, frontmatter targets).
Refs: #428
Reject unsupported client registration values and CIMD client or callback conflicts before syncing invalid settings to Pi. Keep dcr and custom Pi options supported, identify the legacy codemode alias, and document current Pi launch behavior.
Rewrite frontmatter as bytes and read and write target assignments through sourcefs with the discovery follow policy. Refuse nested SKILL.md links with per-skill batch errors or HTTP 400 while regular followed skills remain editable and outside files stay unchanged.
Copy staged directory links as concrete content through the source root, skip dangling links, and reject directory cycles. Preserve the existing skill under a sibling name and restore it if moving or copying the replacement fails so followed checkout updates cannot discard the old content.
Recreate nested links with their stored target text instead of dropping them before removing the original skill. Reuse the junction target resolution and symlink fallback used by moveLink without traversing link contents.
Hub index, built-in search, and draft candidates discovered only the source path, dropping the follow policy used by the inventory. Add optional walk options to the shared Hub functions and pass the operation policy from dashboard handlers and CLI indexing.
Explicit CLI sources use the active config policy while retaining configuration-free indexing. Cover global/project modes, enabled/disabled following, all three handlers, and CLI source overrides; document the behavior in all website locales and built-in guidance.
Standard target naming uses frontmatter names, so matching target entry names misclassified unavailable source skills as broken and suggested pruning. Read the stored link destination, resolve relative paths, and compare it with unavailable source roots; retain name matching only when the link target cannot be read.
Cover absolute and relative destinations and an unrelated broken link whose name resembles a followed skill. Document that standard target names receive the same waiting classification.
Followed worktrees and submodules were discovered as tracked repos but bypassed guards that required a .git directory. Widen IsGitRepo to accept a directory or regular gitdir file and reuse it in discovery and reconciliation. All existing callers classify checkouts or run Git commands; none requires the directory layout, so a separate predicate would retain inconsistent decisions.
Exercise actual followed worktrees in CLI and dashboard update fixtures, including project mode and force retries, and document that they receive the same checkout guards.
A symlink passed as a filepath.Walk root is listed as a single file, so root-of-link skills returned files containing only a dot. Reuse the discovery follow policy to resolve the walk root and compute relative file names from it while retaining logical resource paths.
Cover global/project responses and disabled following, update the existing traversal inventory, and document root-of-link file browsing in all website locales and troubleshooting guidance.
Filtered checks dropped the follow policy when resolving a basename, so a linked checkout visible in an unfiltered check was reported as not found by its name. Forward the operation policy to the resolver and cover both global and project checks against a local Git remote.
Document checking followed checkouts by link name in the command reference and built-in guidance.
Missing-repo discovery ignored the operation follow policy, so tracked metadata added a skipped checkout back to update --all and allowed --force to reset it. Thread the policy through missing-repo detection and its CLI/server callers, including rehydration, so existing followed checkouts remain excluded.
Cover global and project updates with dirty tracked checkouts and force, as well as shared and dashboard rehydration. Document that --force does not override the batch skip.
Discovery callbacks may ignore filesystem errors after a followed target passes its availability probe. Record these failures in the shared Follow policy before dispatching callbacks so sync and reconciliation preserve entries missing from an incomplete inventory.
Keep ordinary vanished-child races tolerated, while treating loss of the target itself as unavailable. Cover both walkers and merge/copy pruning, and document read failures in the English and translated configuration guidance.
* feat(omp): add native Oh My Pi support
Support OMP skills, instructions, MCP, code hooks and guarded extension selection using its verified native contracts rather than Pi aliases.
Add reviewed marketplace plugin installation, cache-preserving scoped removal and fresh-cache reinstall. Align Pi/OMP extension cards and localize inventory guidance while keeping native ownership and read-only constraints.
Include regression coverage, isolated E2E runbooks, documentation and verification policies. Native plugin updates and unverified runtime platforms remain guarded.
Refs #409
* fix(omp): guard runtime ownership and localize inventory guidance
Native install recursively replaces its runtime destination, and a missing cache manifest could leave the real runtime link installed after removal. Bind and recheck an absent reviewed destination, and recover removal names only from verified scope-local links.
Localize fixed backend reasons and warnings across dashboard locales while preserving paths and external diagnostics. Restore the reviewed source in the existing reinstall fixture and record real native verification.
* fix(omp): allow forgetting natively removed plugins
A different plugin can retain node_modules after native uninstall deletes this installation. When its cache, registration and known runtime state are absent, forget only the stale Skillshare binding instead of demanding runtime-name proof for unrelated files.
Extend the existing removal recovery test with a failing-before-fix case that verifies the binding is dropped and unrelated native lock bytes and plugin files are preserved. make check passes.
The linked-root skill guard makes uninstall refuse some first-level links, so generic link-removal instructions could direct users to a command that fails.
Point configuration, FAQ, unlink reference, and built-in skill guidance to unlink or the dashboard Unlink action, preserving target folders for checkout and root-skill links across all five documentation locales.
A root skill discovered through a followed source link occupies the link entry itself. Moving that entry to trash silently unlinks every nested skill instead of removing one skill.
Share the root-skill guard across single and batch API handlers and CLI uninstall, report the unlink action clearly, and preserve explicit unlink and nested skill removal.
Stop parsing mode and command options after -- so valid link names and relative paths beginning with a hyphen can be addressed. Document the unlink form in every command locale and verify that -g and -p after the terminator remain names.
The dashboard section of the ui reference only covered Link folder. Add
the final unlink design so the docs match the shipped UI: the linked
group row, the hover icon button with confirmation, trash restore,
single-skill uninstall inside a link, and the absence of repo actions.
follow_source_links only follows a link that already exists, and the docs
told users to create it with ln -s or mklink /J. The guards then surfaced
only in doctor, after the link existed. Now that skillshare link checks the
target first and picks a junction on Windows, the docs point at the command
and keep the manual way as a note.
Adds command pages for link and unlink, quick-reference and index rows, the
dashboard Link folder sentence, all four translations, and the built-in
skill guidance.
Refs #419
Separate user-owned followed Git checkouts into linked_repos in check and resources responses so the Updates tab renders information instead of tracked errors or retry actions. Refuse dashboard updates before Git runs, including force retries and descendant skills, while leaving managed repositories unchanged.
Keep one follow policy per list and status operation and report its skipped links without hiding healthy inventory. Send JSON diagnostics to stderr and expose sourceLinkWarnings in the dashboard resources response, reusing the sync warning formatter.
The follow_source_links feature touched doctor, update, uninstall,
trash, install and audit behavior without their command pages saying
so, and the ja, ko, zh-Hans and zh-Hant site translations had none of
the new content. Translate every changed page and align the built-in
skill's doctor and troubleshooting references.
The Memory page gained a Refresh button and the active guidance now keeps
short facts as one bullet in INDEX.md, but the walkthrough still said
every durable fact gets its own file. Update it in every locale, and
point the Latest callout in each README at 0.24.6.
Covers the guard order, file links, update --all and dirty checkouts,
--group forms, restore through the link, what Git stages for a link,
the sync and audit JSON warnings, and the junction-chain case in the
Windows runbook.
update --all treated a followed source link as a managed tracked repo:
with --force it ran git reset --hard inside the user's own checkout and
silently discarded their local edits, and an audit-gate rollback would
do the same. --all now skips any tracked repo behind a followed link
with a warning that names the by-name form, which keeps its documented
behavior.
A link into a sync target that is not created yet was reported as a
missing target, which marked the inventory incomplete and held back
pruning for a link that would never be followed. The where-it-points
guards now run on the link text before the does-it-exist check, so such
a link is an overlap and the run prunes as usual.
doctor reported the dangling target links behind an unmounted source
link as broken symlinks and suggested `skillshare sync` to prune them,
while sync deliberately keeps them. Those links are now a warning that
names the waiting source link and carries no prune suggestion.
Record how the junction case is verified through the UTM guest and point the testing topic and the config reference at it, replacing the 'not yet verified' caveat now that the ARM64 run passed.
The unmounted-drive case is the main reason the incomplete-inventory guard exists, so spell out what each command does while the drive is away, what the AI tools see in symlink versus copy mode, and why the mount path must stay stable.
Wave 2 made writes behind a followed first-level link land in the real
checkout, so the "current limits" paragraph written for the discovery-only
version was no longer true. Replace it with the actual write semantics, add
the walker decision flowchart the design discussion settled on, and record
the sourcefs/sourcewalk policy contract in the CLI development topic.
Refs #274
Explain follow_source_links in global and project configuration and distinguish linked source roots from first-level discovery. Document real-checkout update risks, cleanup guards, source write limits, Git staging warnings, and unverified Windows junction support.
The Syncing column described what a target gets as one line of text,
and the whole row led to the Skills tab, so reaching a target's MCP,
Hooks or instruction file took an extra click and a search for the
tab. Each part is now its own link into that tab, and the connected
shared AGENTS.md shows up by its file name, so the list says at a
glance which targets are not connected yet.
Release prep for 0.24.5 found three places where the docs no longer
matched what the pending range changed:
- The Codex portable-manifest rule (Codex installs from a root
plugin.json when a package has both manifests, so Skillshare expects
its version, or 1.0.0) was only in the English plugin reference.
- The .skillignore.local behavior (a pattern without / matches at any
depth, the dashboard shows the .local rules in Settings > Files and
reports a toggle they override as failed, and GET /api/skillignore
returns the .local file) was only in the English filtering and ui
references.
- The status reference did not say that the agents column counts only
the agents a target syncs, after .agentignore, the target's
include/exclude and each agent's targets frontmatter.
The ja, ko, zh-Hans and zh-Hant pages now carry the first two, and every
language carries the third. The Latest callout in README.md and its
translations now describes 0.24.5, which includes a feature.
Codex review on #400:
- A package added with a range such as npm:demo@^1.2.0 was compared with
npm's unrestricted latest. With latest at 2.0.0 and the newest matching
release at 1.9.0, check kept offering 2.0.0, which Pi never installs
because it keeps the configured range. Only a package added without a
version follows latest now; one with a range or a tag is left to Pi, as
a pinned one already was.
- The private-registry check read the user .npmrc path only from
NPM_CONFIG_USERCONFIG. npm reads its environment case-insensitively, so
a lowercase npm_config_userconfig pointing at an .npmrc with a private
registry was ignored, and the package name went to npmjs. Both
spellings are read now.
The plugin reference, its translations and the built-in skill say which
packages the check leaves to Pi.
The Plugins page listed every binding a run touched, one row each, so a
single failure sat among a dozen "unchanged" rows, and the preview did
the same. Failures now come first, Agents that ended the same way share
a row, and what stayed the same folds into one Unchanged line that opens
to one row per plugin, with Pi packages apart. Logos stay only on the
rows that need a look.
An npm package in Pi recorded no version and no source, so it showed no
version and Check updates could only say to check in Pi. The installed
package.json now gives its version, on the Plugins page and in a Pi
target's Extensions tab, and check compares that version with npm's
latest. A newer version gets an Update button on the row and in the
check's result; it updates that one package with pi update <source>,
not pi update --extensions, which would also update packages the
preview never listed. update leaves a package already at npm's latest
alone, and records no version, so the dashboard keeps reading what Pi
installed. The two check messages that were English in every locale now
have keys.
Release-As: 0.24.5
A portable root plugin.json without a version left the Codex binding's
version empty, which skips the post-update version check, so an update
could advance the snapshot while Codex still ran an older copy. Codex
reports 1.0.0 for such a manifest, so expect that instead.
Refs Codex review on #396.
Codex 0.159 installs from a portable root plugin.json (agent-plugins.org
schema) ahead of .codex-plugin/plugin.json, and reports 1.0.0 when that
manifest has no version. Skillshare preferred .codex-plugin/plugin.json,
so updating a package that ships both (ponytail 4.10.3) failed with
"native update returned version 1.0.0; expected 4.10.3" on every sync.
Disabling a skill only checked that its path was written to .skillignore.
A "!" rule in .skillignore.local is applied after that file, and an
unanchored one such as "!feature-radar" re-includes every path segment with
that name, so the skill stayed enabled while the dashboard reported success.
The dashboard also never showed the .local file, so nothing explained why.
Single and batch toggles now re-discover after writing and report an item
that did not reach the requested state as failed, naming the overriding
file; the batch toast shows the first failure's reason. GET /api/skillignore
and /api/agentignore return the .local file, and Settings > Files shows its
rules above the editor.
An agent that reads both a global and a project guidance block saw the
same body twice, with two "save it here", and had to guess whether a
user preference or a project decision went to the shared folder or the
project one. Each block now says what belongs in it: the global block
points project notes at a project memory when one exists, and the
project block keeps project notes and says that notes about the user,
their tools, or other projects do not belong in it. The project block's
examples follow suit, so it no longer names "a stated user preference".
The active rule's two overlapping sentences on when to save are merged
into one, and the plugins reference describes the older Codex.app path
without reference to current events.