github runkids/skillshare v0.30.10

one hour ago

skillshare v0.30.10 Release Notes

TL;DR

  1. Trust the Codex hooks skillshare writes. skillshare hooks sync --trust -g lists the new or changed hooks with their commands and records Codex's trust once you confirm. The dashboard's Hooks page has the same action.
  2. sync and init leave alone what skillshare did not create: look-alike folders, another tool's links and identical folders are no longer deleted or re-pointed.
  3. diff lists what sync removes, for agents and for merge-mode skills.
  4. init names the agent files it kept, and sync agents --force takes over a file that already matches.
  5. Updating skills from the dashboard fetches each repository once, with one progress indicator while it runs.
  6. The hooks dialog for targets opens with nothing selected.

Hooks: Codex trust

Codex runs a user-level hook only after it is trusted, and only /hooks in its TUI recorded that. Every hook skillshare added or moved started untrusted, and codex exec skipped it without a word. (#828, #829)

skillshare hooks sync --trust -g          # lists the commands, asks once
skillshare hooks sync --trust --yes -g    # no question, for scripts
  • After the sync writes, skillshare asks Codex which of its hooks are new or changed, in every Codex home it manages, account homes such as codex-2 included.
  • Those hooks are listed with their full commands and confirmed once. --yes (-y) skips the question. Without a terminal and without --yes, nothing is trusted and the command fails.
  • --json never asks. It reports each hook in a codexTrust list as trusted, unchanged or needed, and exits non-zero when hooks still need trust.
  • Only trusted_hash in config.toml changes. A hook that is disabled in Codex is reported, not switched on, and hooks skillshare does not own are never touched.
  • A home Codex cannot list, or whose write fails, is named in the error. The other homes are still trusted.
  • In the dashboard, the Hooks page has a Trust Codex hooks button in global scope once nothing is waiting to be synced. Its dialog shows each command and records trust only after you confirm.

Global mode only, and codex must be on PATH. Project-level hooks and plugin hooks are not covered. See Codex trust.

Sync: entries skillshare did not create

On Windows, init followed by sync deleted entries in a tool's skills folder that skillshare never made, with no backup, and re-pointed another tool's junction. The manifest of what skillshare created now decides. (#914)

  • Orphan cleanup keeps a folder whose name only looks like skillshare's flat naming (team__shared, _drafts), and a broken link that the manifest does not record. It warns about them.
  • Merge sync re-points a same-name link only when skillshare made it or it already points into the source. Otherwise the entry is reported as kept local.
  • sync --force still removes or replaces these.
  • During init, a folder identical to the source is moved to the trash under replaced-by-init/ instead of being deleted.
  • doctor reports such entries as kept, and a broken link that sync will remove as broken.

Diff

  • The agent diff, in the CLI and the dashboard, listed every link no agent maps to as a removal. Agent sync prunes a link only in merge mode, and only when it is broken or points into the source, so a live link to another location was listed forever. (#939, #942)
  • The CLI diff listed no orphan links for merge-mode skills, so a skill removed from the source showed nothing until sync pruned its link. (#940)

Both now list exactly the links sync removes.

Agents

  • When a tool already had a file under an agent's name, the first sync kept it and init still said "Synced". init now prints a line per tool that names the kept files and the command that replaces them, skillshare sync agents --force. In symlink mode it says the whole agents folder was kept. (#938, #943)
  • Where agents are copied instead of linked (Windows without Developer Mode), a file a tool already had with the same content as the source was kept and never tracked, even with --force. With --force it is now recorded as skillshare's, so later syncs update it. Without --force nothing changes. (#944)

Dashboard

  • The Updates tab cloned the repository once per skill and reinstalled every one: 31 skills from 8 repositories took over a minute where skillshare update --all takes 16 seconds, and unchanged skills were reported as updated. Skills are now grouped by repository and branch, and a skill that already matches upstream is shown and counted as up to date. (#931)
  • An update showed two spinners, a progress bar and a moving line at once, and the bar disappeared before it reached the end. There is now one bar that completes before it fades. Backup, install from config, the plugin update dialog and pending Doctor checks follow the same rule. (#932)
  • The dialog where a hook is edited or removed in its target file opened with every hook ticked, so removing one could import the rest by accident. It now opens with nothing selected, and its entry points are named Hooks in targets and Not managed yet. The review step lists each hook once and opens a diff on request. (#935)
  • When the OpenCode CLI is missing, the dashboard says the command was not found and what to do, instead of showing the raw error. (#935)

Contributors

@salmonumbrella @endgame302

Don't miss a new skillshare release

NewReleases is sending notifications on new releases.