Manage skills and folders

[druellan]

When I create/import a new skill, I can import it in a custom folder, for example coding/react.
But, or I'm missing something or there is no way to move skills between folders, is that correct?
If I install a skill in the root and then I want to move it into coding I need to pretty much remove/install it again?
Can I move it in the Skillshare local folder (I bet this maybe can mess the Skilldatabase).

Thanks!

[runkids]

Yes, you can move it manually — skillshare doesn't have a dedicated move command, but a plain mv works safely:

cd ~/.config/skillshare/skills
mv my-skill coding/react/
skillshare sync

sync will clean up the old flat symlink in your targets and create the new flattened one (coding__react__my-skill) automatically.

To answer your worry directly: this won't mess up the skill database. skillshare doesn't keep a central registry keyed by path — each skill's metadata lives in a .skillshare-meta.json file inside its own folder, so it just travels along with the mv.

Full guide (including suggested folder layouts): Organizing Skills with Folders

[druellan]

Thanks @runkids but if I do that I need to re-build all the filters, since filters are tied to the skill folder structure, correct?

[runkids]

Good catch — it depends on which kind of filter you mean, since skillshare has three separate layers and only one of them is path-sensitive:

• Target include/exclude (skillshare target <name> --add-include/--add-exclude) — these glob-match against the flattened resource name (e.g. my-skill → coding__react__my-skill after the move). Since the flat name encodes the full folder path, moving a skill does change it, so any include/exclude pattern that referenced the old flat name (or a prefix of it) needs to be updated to the new one.
• .skillignore — this uses plain gitignore syntax. An unanchored, single-segment pattern like my-skill (no slash) still matches at any depth, so it keeps working after the move. Only patterns anchored to the old location (e.g. old-folder/my-skill/) would need updating.
• SKILL.md'''s metadata.targets field — not path-based at all, since it'''s declared inside the skill'''s own frontmatter. It just travels with the mv, no changes needed.

So: if you'''re only using .skillignore with basename patterns or per-skill metadata.targets, you'''re fine. If you have target-level include/exclude rules keyed to the old flat names, those specific ones need a quick update to match the new path.

[druellan]

Thanks @runkids I'm endeed using target import for the process, is not that I'm going to change and move the skills all the time, but I'm going to experiment with the .skillignore file. Thanks again.