Skip to content

for agencies running these per-client, how do you handle skill segregation? #70

Description

@latentloop07

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions