Currently, skill import only supports importing the SKILL.md file in isolation.
Request to extend import to support:
- .skill packages - the full skill folder format (containing SKILL.md + scripts/, references/, assets/, and other resources defined by the skill spec)
- .zip archives - zipped skills / zipped skill bundles
When a user imports a .skill file/folder or a .zip, the app should extract and register the entire skill structure, not just parse a single SKILL.md. All bundled resources (scripts, references, assets) should be preserved and made available to the agent at runtime, same as if the skill was installed via the built-in library.
This would bring import parity with the Claude Code / OpenCode .skill spec where a skill is a directory, not a single markdown file.
Usage Scenario
User downloads a skill from a marketplace, GitHub release, or a custom made skill and contains more than just SKILL.md.
- A skill with references/ or assets/ that the SKILL.md links to
- Any skill ported directly from Claude Code without stripping it down to a single file
- A skill with scripts/ for automation (e.g., pdf, docx, xlsx helpers)
Currently, skill import only supports importing the SKILL.md file in isolation.
Request to extend import to support:
When a user imports a .skill file/folder or a .zip, the app should extract and register the entire skill structure, not just parse a single SKILL.md. All bundled resources (scripts, references, assets) should be preserved and made available to the agent at runtime, same as if the skill was installed via the built-in library.
This would bring import parity with the Claude Code / OpenCode .skill spec where a skill is a directory, not a single markdown file.
Usage Scenario
User downloads a skill from a marketplace, GitHub release, or a custom made skill and contains more than just SKILL.md.