question for the agency-shaped use case. these SEO + ads skills look great as a public baseline, but in an agency context most teams customize per-client — different proprietary playbooks per account. ~/.claude/skills/ flat directory becomes a mess pretty quickly.

how are people handling that? a couple of patterns we've seen:

• per-client subdirectories (claude doesn't really support this natively)
• per-client claude profiles with separate skill sets loaded
• a self-hosted registry with per-collection scoping (we built skillnote for this, mit: github.com/luna-prompts/skillnote)

curious what's working. might warrant a docs note for agency adopters.