skillshare v0.26.3 Release Notes

TL;DR

1. Separate OpenCode accounts. Add a second OpenCode config directory as a named target and run OpenCode with OPENCODE_CONFIG_DIR pointing at it.
2. Useful names for generic skill folders. New installs from skill or skills directories use a valid frontmatter name; existing install names stay unchanged on update.
3. Project conflicts open the right editor. Dashboard folder-conflict actions and links for project targets now lead to their project.
4. Dependency security fixes. The CLI includes updated Go dependencies.

New: OpenCode config directory accounts

OpenCode can now use the same named-account workflow as other supported Agents:

skillshare target add opencode-work --agent opencode --config-dir ~/.config/opencode-work -g
skillshare sync -g
OPENCODE_CONFIG_DIR="$HOME/.config/opencode-work" opencode

The account uses its own skills and agents directories, MCP configuration and plugins. Its target name can be used in MCP target lists. Choose an absolute config directory, or one beginning with ~, that is not OpenCode's default directory and is not already used by another target.

For account plugin operations, unset OPENCODE_CONFIG so an explicit shared config file cannot override the account directory. Inline OPENCODE_CONFIG_CONTENT overrides are not supported for plugin sync.

Thanks to @jskswamy (#593, #594).

Fixed: generic skill directory names

A skill stored in skills/SKILL.md used to install as skills, even when its frontmatter named it MinerU Document Extractor. New installs from generic skill or skills folders now use a valid frontmatter name, lowercased with whitespace normalized to hyphens: mineru-document-extractor in this example.

• Missing, invalid or conflicting frontmatter names fall back to the directory name.
• Descriptive directory names and explicit --name overrides keep their existing behavior.
• Updates preserve existing installation destinations; this release does not rename existing installs.
• Tracked repository paths and naming are unchanged.

Thanks to @chung1912 for reporting it (#616, #617).

Fixed: dashboard folder-conflict navigation

For a project target, both the folder-conflict action button and the target-name link now open the project editor. Previously they led to a target settings page that could not edit that project's target. Action buttons also have their own row instead of sharing the explanatory text's row.

Thanks to @heyAidy for reporting it (#612, #613).

Security: updated Go dependencies

The CLI now uses updated Go dependencies with security fixes, including Goldmark and the golang.org/x packages (#608).

Contributors

@jskswamy, @heyAidy, @chung1912, @salmonumbrella