skillshare v0.21.10 Release Notes

TL;DR

One AGENTS.md for every tool. The dashboard's Extras page has an AGENTS.md tab: write a shared file once and pick which tools read it. Restore puts back exactly what each tool had before.
Each tool's instruction file, in one place. Every target page has a tab named after the file that tool reads (CLAUDE.md, GEMINI.md, AGENTS.md…), with its read order, an editor and warnings.
Single-file extras. An extra can sync one file instead of a folder, rename it per target, or add an @ import line instead of replacing the file.
See which projects a skill reaches. The Skills page tells global tools and project folders apart, and the Target filter groups them.
Fixes: Pi servers load again with pi-mcp-adapter 3.0, a failed git pull no longer leaves stale files behind, and upgrading with sudo no longer leaves root-owned files in your home.

Share one AGENTS.md across your tools

Open the dashboard, go to Extras, and pick the AGENTS.md tab.

skillshare ui

Create a shared AGENTS.md and choose which targets read it. Codex, Gemini and other tools get a link in place of their file, which is backed up first. Claude has no user-level AGENTS.md, so it gets an @ import in ~/.claude/CLAUDE.md and keeps its own content.

You can keep several shared files side by side, for example one for personal work and one for your job. Tools that follow @ imports can use more than one. Restore asks first, then puts back exactly what the tool had before it was attached.

Edit each tool's instruction file

Every target page now has a tab named after the file that tool reads. It shows the order the tool reads its files in, an editor, and warnings such as Windsurf reading only the first 6,000 characters. Convert… moves the content of CLAUDE.md into AGENTS.md by import, rename or copy, and backs up the file first.

In project mode, the tab shows whether each tool reads ./AGENTS.md, and offers a small fix for tools that only read their own file, such as adding @AGENTS.md to CLAUDE.md.

A custom target can say which instruction file it reads, either in the Custom target dialog or later from the same tab:

targets:
  myagent:
    path: ~/.myagent/skills
    instructions:
      path: ~/.myagent/AGENTS.md
      import: true        # the tool follows @path lines

Single-file extras

An extra with file syncs one file instead of a whole folder. as renames it for a target, and mode: import writes an @ line into the target's own file instead of replacing it.

extras:
  - name: personal
    file: AGENTS.md
    targets:
      - path: ~/.codex
      - path: ~/.claude
        as: CLAUDE.md
        mode: import

extras list shows modified when a linked file was replaced by a different one, and extras remove puts back what each target had before the first sync.

See which projects a skill reaches

If you manage project folders from the global config, the Skills page used to draw a project's tools with the same icons as your global tools, so claude plus two projects looked like three Claude icons. The Targets column now shows your global tools as icons, followed by a folder badge with the number of projects the skill reaches. Hover it to see each project's tools, and the projects the skill skips.

The Target filter groups global tools and projects, with one entry per project, so "which skills are in this project" is one click. In the tree view, the Targets row shows where the selected skill actually goes.

Without projects, the page looks the same as before.

Bug fixes

Pi servers load again with pi-mcp-adapter 3.0. The adapter now reads mcp-adapter.json instead of mcp.json, so the servers skillshare synced were ignored. Skillshare now writes them to ~/.pi/agent/mcp-adapter.json, .pi/mcp-adapter.json in a project, or mcp-adapter.json in a Pi account's folder. The next sync removes the entries it had written to mcp.json and leaves yours alone. pi-mcp-extension still uses mcp.json.

skillshare sync mcp

A pull that fails midway no longer leaves the remote's files behind. When git could not finish a pull, for example because a file in the source folder was owned by root, the files it had already written showed up as local changes, and the dashboard suggested committing them. A failed pull now restores those files and leaves your own edits alone, and a permission failure shows the chown command that fixes it.

Upgrading with sudo no longer leaves root-owned files in your home. When the binary lived in a root-owned folder, the whole upgrade ran under sudo, so the built-in skill, dashboard assets and logs were written as root. Only the binary replacement uses sudo now.

skillshare upgrade

runkids/skillshare v0.21.10 on GitHub