[Question] How to manage two different skill from one same repo？

[leeeezx]

Hi! I'm using skillshare to manage my AI skills. I've noticed this repo provides two different versions of the planning-with-files skill:

• .codex/skills/planning-with-files
• .gemini/skills/planning-with-files

I want my codex target to track only the Codex version, and my gemini cli target to track only the Gemini version. I want them to stay updated separately when I run skillshare update or sync.

What is the best way to use skillshare for this? Thanks for your help!

[runkids]

Thanks for the question — and for the continued feedback! 🙏

Right now, skillshare syncs all installed skills to all configured targets — there's no per-target routing yet.

What works today

You can install each version separately using subdir paths:

skillshare install github.com/user/repo/.codex/skills/planning-with-files --name codex-planning
skillshare install github.com/user/repo/.gemini/skills/planning-with-files --name gemini-planning

Both will sync to all targets, but in practice this is harmless — each tool simply ignores skills it doesn't recognize. The only downside is a bit of extra clutter in each target directory.

If you want strict isolation, project mode can help:

# .skillshare/config.yaml in your project
targets:
  - codex

skillshare install github.com/user/repo/.codex/skills/planning-with-files -p
skillshare sync -p

This way only the codex target gets synced in that project context.

On per-target filtering

A targets.include / targets.exclude config would solve this cleanly, but honestly it's a fairly niche use case so I'm not sure when I'd get to it. Keeping this open to track interest — if more people run into this, it'll move up the priority list.

Thanks again for taking the time to report!

[leeeezx]

thank you for your answer！

[runkids]

@leeeezx Update: I actually ran into a similar situation myself now 😂, so I've decided to go ahead and implement per-target include/exclude filtering. Will ship it in an upcoming release — stay tuned! 🚀

[leeeezx]

@leeeezx Update: I actually ran into a similar situation myself now 😂, so I've decided to go ahead and implement per-target include/exclude filtering. Will ship it in an upcoming release — stay tuned! 🚀

haha, a late but good news for me, thanks for your work.

[runkids]

Update — your question actually gave me the inspiration, and I ran into the exact same need myself recently, so I went ahead and built per-target include/exclude filtering. It ships in v0.12.6.

For your use case, there are two steps:

Step 1 — Install with distinct names (you may already have this from the earlier workaround):

skillshare install github.com/user/repo/.codex/skills/planning-with-files --name codex-planning
skillshare install github.com/user/repo/.gemini/skills/planning-with-files --name gemini-planning

Since both subdirectories share the same folder name (planning-with-files), --name gives each a unique identity in the source.

Step 2 — Exclude the other target's skill:

targets:
  codex:
    path: ~/.codex/skills
    exclude: [gemini-*]
  gemini:
    path: ~/.config/gemini/skills
    exclude: [codex-*]

All shared skills sync to both targets as before — each target just skips the skills meant for the other. Patterns use glob syntax (*, ?, [...]).

• Works in both global and project mode
• include (whitelist) is also supported if you prefer an explicit allow-list
• Full docs: https://skillshare.runkids.cc/docs/targets/configuration#include--exclude-target-filters

Thanks again for raising this — it ended up being a really useful feature! Marking as answered — feel free to follow up if you hit any issues.

[leeeezx]

excellent work！i will try now

[leeeezx]

Am I successful now? The warn can be ignored？

[runkids]

That's fine, it just means there's a duplicate name in SKILL.👍 But I might make some detection improvements for exclude and include.