skillshare v0.21.1 Release Notes

TL;DR

1. Turn off a global MCP server in one project — mark an entry disabled in project mode and the server stops loading there, while every other project keeps it. Claude Code, OpenCode, Kilo Code and Pi.
2. Kilo Code is an MCP client — global and project scope.
3. Claude Code local scope servers are reported — when a server you added with claude mcp add hides the one Skillshare writes, the plan says so and gives the command that removes it.
4. The dashboard shows which skills are manual only, explains each frontmatter field in the editor's Add field menu, and shows Agent logos in the MCP import picker.
5. MCP fixes — Agents with no MCP file yet are detected, Cline's new settings location is found, and an entry owned by a deleted config can be taken over.
6. Breaking: the kilocode skills target moved from .kilocode/skills to .kilo/skills.

Turn off a global MCP server in one project

A server in an Agent's global config loads in every project. Until now the only way to keep it out of one project was to edit the Agent's files by hand on every machine.

In project mode, add an entry with the same name and mark it disabled:

cd my-project
skillshare mcp add company-docs --disabled --target claude --target opencode
skillshare sync mcp

# .skillshare/config.yaml
mcp:
  servers:
    company-docs:
      disabled: true
      targets: [claude, opencode]

The entry holds no command or URL. The Agent keeps those from its global entry, so the project file only carries the switch, and it can be committed for the whole team.

How it lands depends on the Agent:

• OpenCode, Kilo Code and Pi with pi-mcp-adapter merge project settings over global ones, so they get a lone switch in their project file.
• Claude Code takes a whole entry from one scope and does not merge. Skillshare adds the name to that project's off list in ~/.claude.json, the same list the /mcp panel edits. A name you turned off yourself is never claimed or removed.
• Other clients are refused. In their format a lone switch would replace the server instead of turning it off. Codex gets its own message: on a machine whose global config lacks the server, a lone switch in a project file stops Codex loading its whole config, so set enabled = false in ~/.codex/config.toml instead.

In the dashboard, open it from the project folder, choose Add server and pick Off in this project. Refs: #286.

Kilo Code is an MCP client

kilocode joins the supported MCP clients in global and project scope. It uses OpenCode's format. Skillshare writes to whichever kilo.jsonc or kilo.json already exists and creates kilo.jsonc when there is none.

Kilo ignores a project config that holds an environment reference, so fromEnv and bearerToken are refused for Kilo in project mode before anything is written. Refs: #287.

Claude Code local scope servers are reported

A server added with claude mcp add and no --scope goes to Claude Code's local scope, and it wins, whole, over a server of the same name in .mcp.json or the user scope. Skillshare could write an entry, report success, and Claude Code would still run the other one.

In project mode the plan and the dashboard now point out such a server next to the entry it hides:

claude mcp remove company-docs -s local

The sync is not blocked. Global mode cannot report this, because the project is not known there.

Client limits are caught before the write

Claude Code skips the reserved names workspace, claude-in-chrome and computer-use, and reads its own credentials such as ANTHROPIC_API_KEY as empty in a remote server's url and headers. Both are now refused for Claude with a message that says what to do. The dashboard's config preview refuses the same things saving would.

Dashboard

• Manual only skills are visible. A skill with disable-model-invocation: true carries a manual only tag in the skills list, on its tile and on its detail page, matching the badge the list TUI shows after M. Refs: #283.
• Add field explains each frontmatter field. The skill editor's Add field menu shows what each field does under its name, instead of bare keys such as context and shell.
• Agent icons in the MCP import picker. The Agent dropdown in Import from a target shows each Agent's logo. Factory, LM Studio, Kilo Code and Claude Desktop now have their own icons.

Bug fixes

• The MCP page detects Agents that have no MCP file yet. A fresh Claude Code install showed as not detected. An Agent's own settings folder now counts. In project mode the page listed every Agent as detected; it now lists those with a project MCP file or a global install.
• Cline's MCP settings are found again. Cline moved its settings to ~/.cline/data/settings/. Skillshare writes there and honors CLINE_MCP_SETTINGS_PATH, CLINE_DATA_DIR and CLINE_DIR. The old VS Code extension path is still used while it is the only one that exists.
• An MCP entry owned by a deleted config can be taken over. It used to stay blocked forever as "managed by another Skillshare config". An explicit import or replace now takes it over, and the conflict names the owning file.
• --disabled is refused where it does nothing. Only mcp add uses the flag; the other mcp commands and sync mcp accepted it and ignored it.
• A relative XDG_CONFIG_HOME is ignored for MCP paths, as the XDG specification requires.
• Skill detail and new skill pages. The file viewer no longer leaves a gap above it when it sticks while scrolling, and the info column beside a long SKILL.md stays in view.

Migration: kilocode skills target

The kilocode skills target moved from .kilocode/skills to .kilo/skills, in both global and project scope, because that is the only location Kilo Code's documentation lists now.

skillshare sync

Run it once to write skills to the new location.