skillshare v0.27.0 Release Notes

TL;DR

1. Manage project folders from the terminal. skillshare project brings global project registrations to the CLI, with previews, JSON output, filters, and per-project sync.
2. Tracked updates are scanned before becoming active. A rejected update no longer exposes its candidate files through existing target links.
3. Dashboard fixes. Mobile navigation, responsive update controls, and description editing that retains nested YAML values.

skillshare upgrade

Added: project registrations in the CLI

List and inspect the projects registered in your global config, or add a folder and choose which tools receive its skills and agents:

skillshare project list --json
skillshare project add ~/work/app --target claude,codex --skills-mode copy --dry-run
skillshare project add ~/work/app --target claude,codex --skills-mode copy --sync
skillshare project show app --json
skillshare project edit app --skills-include 'frontend-*'
skillshare project sync app --json

The command always uses the global config, even inside a project; it does not accept -p. It does not edit the project's own config or manage its MCP settings. Filters replace their saved lists, rather than appending.

A failed sync after add or edit leaves the registration saved. Fix the target and retry project sync; inspect the JSON result before retrying a partially completed change.

skillshare project remove app --dry-run --json previews removal. Removal detaches skills and keeps agent files. JSON removal requires --yes unless previewing. These filesystem changes are not transactional.

Reference: #603. Thanks to @salmonumbrella.

Fixed: tracked updates became visible before their security scan

Tracked skill and agent repositories can already be linked into tools. Previously, pulling into their active checkout could expose candidate content through those links before the audit decision.

CLI and dashboard updates now pull and scan an isolated candidate. Rejecting findings, or a scan error, leaves the active checkout and metadata unchanged. Approval publishes the exact scanned commit without fetching again. Existing accepted findings remain honored.

--force can accept blocking findings, but does not bypass a scan error. Publication is not an atomic multi-file switch.

References: #645, #646, #647. Thanks to @suainam for the proposal.

Changed: failed update checks return a failure exit code

skillshare check now exits with code 1 if any checked item has status error, such as an unreachable remote or a missing local source. Available updates, stale items, and local modifications alone still exit successfully.

With --json, stdout still contains the complete results. Scripts should inspect each item's status and message even when the command fails.

References: #643, runkids/skillshare-app#85. Thanks to @dev-seahouse for the related report.

Fixed: dashboard editing and update controls

• Editing a skill's description retains nested YAML values, such as metadata and lists, preserves a leading UTF-8 BOM, and keeps descriptions containing colons valid YAML.
• Update controls no longer visually overlap local-changes statuses, and long skill names no longer break the detail layout.
• On narrow screens, a menu opens navigation and shows the current mode inside the menu.

References: #637, #638, #642, #644. Thanks to @chung1912 for the reports.

Fixed: selected global config logs and Antigravity CLI plugins

• With SKILLSHARE_CONFIG, global logs remain in the state directory ($XDG_STATE_HOME/skillshare/logs/, default ~/.local/state/skillshare/logs/), rather than a project-style folder. CLI and dashboard log viewing and clearing use the same files.
• Antigravity CLI plugin checks, updates, and removal recognize the native JSON-array inventory instead of failing with an unrecognized-inventory error.

References: #609, #639, #640. Thanks to @salmonumbrella and @jskswamy.

Compatibility

No configuration migration is required. Automation that previously ignored failed check results may now observe exit code 1; update those scripts to handle errors explicitly.

Contributors

Thanks to @salmonumbrella, @suainam, @jskswamy, @chung1912, and @dev-seahouse.