v0.21.5

skillshare v0.21.5 Release Notes

TL;DR

1. A second account of Claude Code, Codex or Pi can be its own target. Skills, agents, MCP servers and plugins go to that account's folder.
2. Sync one part from its own page. Skills, Agents, MCP and each project have a sync button that writes only that part.
3. Stop managing an MCP server without touching Agent files. The Agent keeps the server; Skillshare lets go of it.
4. Servers added to an Agent directly are pointed out, and Import opens on the file that holds them.
5. Fixes for importing a project's MCP conflict, Pi adapter settings, sync previews and confusing global setup errors.

A second account as its own target

Many people run a second copy of an Agent with its own config folder, such as a work account of Claude Code started with CLAUDE_CONFIG_DIR=~/.claude-work. Until now that meant a custom target with hand-written paths, and MCP servers could not reach it at all.

Add the folder as an account instead, and Skillshare works out where that account keeps its skills and agents:

skillshare target add claude-work --agent claude --config-dir ~/.claude-work

In the dashboard, choose Add target → Another account, pick the Agent and the folder. The config only records the folder:

targets:
  claude-work:
    agent: claude
    config_dir: ~/.claude-work

Codex (CODEX_HOME) and Pi (PI_CODING_AGENT_DIR) accounts work the same way. Their skills go to skills inside the account's folder.

The account's name works wherever an Agent's name does for MCP and plugins:

mcp:
  targets: [claude, claude-work]      # both accounts get every server
  servers:
    jira:
      command: jira-mcp
      targets: [claude-work]          # the work account only

Servers are written into the account's own file, and plugins are installed with the Agent's CLI pointed at the account's folder. skillshare mcp import --from claude-work reads that account's servers. A Pi account needs piExtension: pi-mcp-adapter, since pi-mcp-extension always reads ~/.pi/agent/mcp.json.

Removing an account target warns you when MCP config still names it, so the next MCP sync does not fail by surprise.

Sync one part from its own page

Syncing used to mean going to the Sync page and reviewing everything at once. Skills, Agents and MCP now each have a sync button that previews and writes only that part. A project page has Sync project, which writes that project's skills, agents and MCP and leaves global targets and other projects alone. The sync prompts after an update, uninstall or collect open the same dialog.

Stop managing an MCP server

Removing a server always cleared its entries from the Agents on the next sync, so there was no way to hand a server back to the Agent. Stop managing drops it from Skillshare and leaves the Agent files as they are:

skillshare mcp remove context7 --keep-files

It is also the third choice in the dashboard's remove dialog and in the remove wizard.

The MCP page and each project's MCP tab now say which Agent files hold servers Skillshare does not manage, and Import opens on that file.

Pi adapter settings moved from a hover icon to a line under the server's endpoint, so you can see which tools each server exposes to Pi at a glance.

Fixes

• Importing a project's MCP conflict now reads that project's files and imports into the project. It used to read the Agent's global file.
• Pi adapter settings survive unticking Pi. Ticking Pi again no longer resets Direct tools and piOptions.
• The MCP page no longer crashes on a cold load.
• Skill and agent pages list their projects, matching the counts on the Skills and Agents lists.
• Skills and Agents sync previews no longer show changes on targets that are already in sync.
• Global setup errors say they are about the global config. A missing global source folder now says so, names the config, and tells you how to fix it instead of suggesting skillshare init.