Individualized skill syncing?

[TyceHerrman]

Is it possible to do something like this?

assume skills a, b, and c all in skillshare and 3 ai clis, cc gemini and codex

skill a just for cc
skill b for gemini and codex
skill c for all 3.

Doesn't seem like it's possible from the docs, but can you let me know if I'm missing something?

[runkids]

Yes, this is supported! There are two ways to achieve per-skill target routing:

1. Skill-level targets field (set by skill author)

In each skill's SKILL.md frontmatter, add a targets field to restrict which CLIs it syncs to:

# skills/skill-a/SKILL.md
---
name: skill-a
targets: [claude]
---

# skills/skill-b/SKILL.md
---
name: skill-b
targets: [gemini, codex]
---

# skills/skill-c/SKILL.md
---
name: skill-c
# no targets field = syncs to ALL targets
---

2. Config-level include/exclude filters (set by consumer)

Alternatively, you can control routing from your config.yaml using per-target filters:

# ~/.config/skillshare/config.yaml
targets:
  claude:
    path: ~/.claude/skills
    include: [skill-a, skill-c]
  gemini-cli:
    path: ~/.gemini/skills
    include: [skill-b, skill-c]
  codex:
    path: ~/.codex/skills
    include: [skill-b, skill-c]

Both approaches can be combined — config filters are applied first, then the skill-level targets field.

This feature originated from #22.

Docs:

• Skill Format — targets field
• Configuration — include/exclude filters