You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OR-247 feat: simplify the skills experience (#272)
* feat: simplify the skills experience
The Customize tab was five sections deep in choices that no longer earned
their place: a Global/This project scope picker on every card, a separate
"import from your agent" list, and two split skill lists.
- Skills installed in a coding agent are now mirrored automatically —
read live from its skills dir on every listing and every session write,
so a skill edited in Claude Code is the one the next session runs. The
import step and its two endpoints are gone. A session hosted by the
agent a skill came from is not handed a copy it already loads.
- Claude Code's installed plugins are mirrored too, discovered through
installed_plugins.json so only real installs count.
- Every skill and LaTeX template is global. Project scope is removed
from the store, the API, and the UI; anything already saved under it
is migrated into the single store on first access.
- Skill frontmatter is parsed the way skills are actually written:
folded and literal blocks, and values wrapped over indented lines. A
skill whose frontmatter we cannot read is a skill the user never sees.
- ~/.agents/skills is read whenever it exists, rather than only when
~/.codex does.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix: harden the skills mirror after review
Review of the mirroring change turned up defects worth fixing before it
ships:
- A plugin's skills are registered namespaced (`runpod:flash`), so the
bare `/name` only resolves from a copy. They are no longer treated as
natively loaded by the agent that installed them.
- Uploaded skills resolve through their folder name again, not the
frontmatter `name` a hand-edit can change out from under them.
- The hosting agent's own skills are dropped only after they have won
their `/name`, so a same-named skill from another agent can't take
their place in the worktree while the dashboard shows the first.
- Session skill dirs are replaced and pruned only when the manifest says
we wrote them, so a `.claude/skills` the project itself commits is
left alone; manifest names are re-validated before any removal.
- A folder whose source is unchanged is not re-copied, folders over the
upload budget are skipped, and neither the copy nor the size walk
follows symlinks.
- The retired per-project store is emptied, never deleted: anything that
can't move stays put as the user's only copy.
- A `#` comment no longer folds into the value above it, and a long
description truncates instead of dropping the skill.
- The Customize tab distinguishes a failed skills fetch from an empty
one, and ignores drops while an upload is in flight.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix: keep one answer for what a skill name resolves to
Second review round:
- `source_dirs` resolves uploads through the same listing the dashboard
reads, so a folder whose SKILL.md won't parse can't win a name in the
worktree while the tab shows the mirrored skill it shadowed.
- A folder tally now carries a digest over every (path, size) pair, so a
rename or a move inside a skill brings the session copy forward; each
source and destination is walked once per turn instead of three times.
- A destination whose content already matches its source is adopted as
ours, so a lost manifest heals instead of freezing that skill forever.
- A mirrored folder over the upload budget is left out of the listing
too, rather than offering a `/name` that never reaches the worktree.
- LaTeX templates get the same skip-if-unchanged treatment.
- Archive junk under the retired per-project store no longer keeps it
alive on every call.
The freshness test now watches the inode: `fs::copy` carries the mtime
across on macOS, so the timestamp it asserted on could never have failed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix: never let an adopted skill dir become prunable
Round three: adopting a destination whose content already matches its
source healed a lost manifest, but it also recorded a directory orx had
never written — so once the source went away, the prune deleted a skill
the project itself commits.
Adoption is now limited to the case it was for: no manifest at all. While
a manifest exists it stays the whole truth about what we own.
Also from that round: the upload budget moved into `source_dirs`, so the
menu, the hover preview and the session write agree on which `/name`
exists; a stray `.DS_Store` beside the retired per-project store no
longer keeps it alive; and the uncapped walks stopped pretending they can
fail.
The fingerprint test never reached the SKILL.md byte comparison it was
supposed to cover, and the migration test never asserted the retired tree
was gone — both fixed, and both verified by reverting the fix under them.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* refactor: one budget answer for uploads too
The listing kept sizing uploads with an uncapped walk while the resolver
had started budgeting them, so a hand-edited store could list a skill no
session would be given.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments