Skip to content

v0.1.3

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Sep 15:40

What's Changed

  • Drawer coverage: walk drawers deep, catalogue plugin trees by @frontender-ua in #1

New Contributors

Full Changelog: v0.1.2...v0.1.3

v0.1.3 — the drawers it was missing

shelfware claimed to catalog every skill drawer on your machine. It wasn't: on the machine this was developed on it found 10 skills while 177 more sat in folders it walked straight past. This release makes the scanner deliver what the README already promised — the same catalog, looking in the right places.

npx shelfware@latest

Drawers are walked deep

A drawer is no longer assumed to be flat. Skills grouped into sub-folders are catalogued now, whether the grouping is by category (skills/engineering/<skill>/SKILL.md) or under a dot-named folder — ~/.codex/skills/.system/<skill> was invisible before and is a card today.

Plugin trees are catalogued

Every tool's ~/.<tool>/plugins tree is scanned. Where a tool keeps the installed plugins and the marketplace checkouts apart, each becomes its own drawer — …/plugins/cache and …/plugins/marketplaces — so the counts stay legible and you can filter either away. A tool that keeps one plugins folder gets one drawer, which is how Cursor's plugins still appear; they now come through the same general rule instead of a special case.

Inside a plugin tree only folders named skills/ (or skill/) are read, so a plugin's own README, its docs/ and its source never become cards.

Repository documents are no longer skills

A loose *.md file inside a drawer is still a skill — that hasn't changed. But the documents that ship beside skills in a checkout are now skipped: README (including translations), CHANGELOG, LICENCE, CONTRIBUTING, SECURITY, pull request templates and a few more.

Fixed: quarantine and delete could act outside the drawer

The deep walk used to descend through symlinked directories. A skill found under, say, ~/.claude/skills/shared -> ~/Develop/my-skills became an ordinary-looking card whose path read as if it were inside the drawer, and the containment check compared paths textually — so quarantining it renamed the real directory out of your repository, and deleting it removed that directory recursively.

Two changes close this. The walk no longer descends into a symlinked directory (one that holds its own SKILL.md is still catalogued, still as a reference). And quarantine, delete and save now verify containment against resolved real paths, checking the skill's parent folder — so a skill that is a symlink stays unlinkable exactly as before: the link goes, its target stays.

Nothing changed for existing setups

Same command-line flags, same local API, same quarantine manifest format, same card fields. Existing drawer names keep their identifiers, so bookmarked URLs and anything already on the quarantine shelf still resolve. The new drawers simply appear alongside them.

Worth knowing

  • A plugin installed as a symlink is read-only. It is still catalogued, but quarantine, delete and saving an edit all refuse it. Removing that refusal would mean acting on files outside the drawer, so the refusal is deliberate — it is on the list to make visible on the card rather than only at the moment you act.
  • "Copies wasting N MB" counts duplication your tools manage. With plugin trees in the catalog, most repeated skills are an installed plugin and its marketplace checkout, or the same plugin under two profiles. Deleting either side breaks a working plugin. Read that figure as information, not as a to-do.

Credits

Drawer coverage follows skill-cabinet issue #19 and its open pull requests #17, #20 and #21 (MIT), rewritten for this codebase.