Repository navigation
Conversation
0libote
force-pushed
the
feat/hide-bundled-skills
branch
from
October 19, 2026 10:54
90f272d to
b4f817b
Compare
0libote
changed the title
…tions Borrow the registry shape from skills-hub (MIT): each inventory now reports its adapter (global/project skill dirs, install detection). Detection never gates management; undetected tools show a note.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Skills tab can hide provider-bundled skills, and repository-installed skills can report when their source changes.
Hide bundled skills filters entries marked as system skills, remembers the choice in this browser, and shows how many skills are hidden. It only affects the list; the provider can still use those skills.
New installs from Git repositories record their source and a fingerprint of the skill's files. Check for updates checks these sources on demand and reports whether each skill is up to date, has changed, or could not be checked. Normal inventory refreshes do not contact repositories. Checks compare the selected skill's complete files, including supporting files and executable flags, so unrelated repository commits do not trigger an update.
Review update opens a fresh source preview with the installed skill selected. Replacing it requires the existing explicit confirmation. The check never changes local files. Earlier installs and sources without a repository origin need to be re-imported to enable tracking. There are no scheduled checks or automatic replacements.
Provider adapters (
docker/setup/skills/adapters.mjs): each inventory now reports its adapter — the global skill folder, the verified project folder (Codex, Cursor, OpenCode and Antigravity share.agents/skillsinside a project; Grok and Muse project scope stays unverified rather than guessed), and whether the tool itself is detected. Detection never gates management: an undetected tool shows a note and stays fully editable, unlike registries that refuse unknown tools. Adapter globals are cross-checked against the scanned primary roots intests/skill-adapters.test.mjsso they cannot drift. Motivation and the skills-hub spike behind this are recorded indocs/experiments/skills-hub.md.Screenshots
Bundled skill filter on a phone:
Update check and review flow:
Undetected-tool adapter note on a phone: