FAQ

Do I need an account to install skills?: No. Search, install, and inspect are fully anonymous — you only sign in to publish your own skills.
Where do skills get installed?: Into your project's .claude/skills/ folder — Claude Code's skill-discovery directory — each as a flat <name>/ folder. The manifest (skillgraph.json) and lockfile (skillgraph.lock.json) live at the project root.
What is a coordinate and a scope?: A published skill is addressed as @scope/name, where the scope is your username. You never type your scope when publishing — the registry stamps it from your identity, so you can only ever publish under your own.
Owned vs installed — what is the difference?: Installed skills are ones you consume (read-only). Owned skills are ones you manage and can publish. fork turns an installed skill into an owned copy under your scope, recording its origin as lineage.
How does publishing a dependency graph work?: publish resolves the managed skills you point it at, orders them leaves-first, and publishes each. A co-published sibling dependency is stamped with your scope; a cross-author dependency is referenced by its full coordinate.
Is it Claude-only?: The on-disk target is Claude Code's .claude/skills/ for now, but the manifest and lock live at the project root (agent-agnostic) so the same resolved graph can materialize into other agents' directories later.