--into grouped skills: SKILL.md name doesn't match synced folder name

[Curtion]

Hi! Love the project, thanks for building it!

When using --into to organize skills, the synced target folder uses a flat name (e.g. frontend__my-skill), but the name field in SKILL.md stays as
the bare name (my-skill). Some tools expect them to match:

• VS Code warns about the mismatch when editing SKILL.md
• pi-mono warns during skill loading

Thanks!

[runkids]

Hi, thanks for the report and the kind words!

The warning you're seeing from VS Code / pi-mono comes from the Agent Skills specification, which requires the name field to match the parent directory name. These are validation warnings only — they don't affect functionality.

Personally, I don't think requiring the skill name to match the directory name is a good rule — it creates unnecessary friction and limits how users can organize their skills. I'll be making some changes to give users more control over this.

[Curtion]

Hi, thanks for the report and the kind words!

The warning you're seeing from VS Code / pi-mono comes from the Agent Skills specification, which requires the name field to match the parent directory name. These are validation warnings only — they don't affect functionality.

Personally, I don't think requiring the skill name to match the directory name is a good rule — it creates unnecessary friction and limits how users can organize their skills. I'll be making some changes to give users more control over this.

Thanks for the explanation! That makes sense. Fully agree that the current spec is too restrictive — users should be able to organize skills however they want.

Happy to test any changes when you get around to them.

[runkids]

Addressed in v0.18.4 with the new target_naming config option:

• flat (default) — keeps frontend__my-skill naming
• standard — uses the SKILL.md name directly, matching the Agent Skills spec

Set globally or per-target via CLI, Web UI, or config.yaml. skillshare upgrade to get it. Thanks @Curtion!