Problem
File-based skills are discoverable through the composer, but there is no dedicated place to inspect their descriptions, sources and paths or manage which files MonoCode includes in its catalog.
Proposed scope
Add Settings → Skills using the existing discovery and starter-SKILL.md APIs: filter by name/description/source/path, rescan folders, create a project or personal starter skill, copy/reveal paths, and hide/show individual files in MonoCode's catalog without deleting them. Provider-owned native command catalogs remain provider-managed; the UI will explain that limitation.
This is extracted from a working implementation in my fork and will be submitted as a focused PR against main. It excludes provider additions, command runners, marketplace/import flows, icon replacements, and unrelated settings work.
Opening this issue first per CONTRIBUTING.md's requirement for a new surface. There is an existing command-picker PR (#98), but this proposal concerns a dedicated Settings panel rather than chat command actions. Feedback on scope and placement is welcome.

Problem
File-based skills are discoverable through the composer, but there is no dedicated place to inspect their descriptions, sources and paths or manage which files MonoCode includes in its catalog.
Proposed scope
Add Settings → Skills using the existing discovery and starter-SKILL.md APIs: filter by name/description/source/path, rescan folders, create a project or personal starter skill, copy/reveal paths, and hide/show individual files in MonoCode's catalog without deleting them. Provider-owned native command catalogs remain provider-managed; the UI will explain that limitation.
This is extracted from a working implementation in my fork and will be submitted as a focused PR against main. It excludes provider additions, command runners, marketplace/import flows, icon replacements, and unrelated settings work.
Opening this issue first per CONTRIBUTING.md's requirement for a new surface. There is an existing command-picker PR (#98), but this proposal concerns a dedicated Settings panel rather than chat command actions. Feedback on scope and placement is welcome.