1Join your organization

You join by invitation. An admin sends one to your skills-hub username or your email address:

Existing account: the email links straight to an accept page. Sign in and accept.
New to skills-hub: the link walks you through creating an account first (email and password, GitHub, or Google), then accepts the invite for you.

Invites expire after 7 days; ask for a fresh one if yours has lapsed. If the invite was targeted at a department or team, you are placed there on acceptance.

2Complete onboarding

After accepting you land on a short onboarding flow: pick your departments and teams from your organization's structure and enter your job role. It takes about a minute, and it is how the registry knows which department and team skills to show you.

3Find skills

From your organization page you can:

Search every org skill you are allowed to see, by name or description.
Filter by category (Build, Review, Docs, Marketing, and so on).
Browse by structure on the Departments page: each department and team lists its skills.

Visibility is scoped automatically:

A skill marked	Is visible to
Organization	Every member
Department	Members of that department (or everyone, when cross-department sharing is on)
Team	Members of that team (or everyone, when cross-team sharing is on)

If a teammate mentions a skill you cannot find, that is scoping at work: you are not in the unit it belongs to. Ask to be added, or ask an admin whether it should be shared wider.

4Install and use a skill

Org skills install exactly like public ones. From a skill page, copy the install command:

bash

npx @skills-hub-ai/cli login                 # once
npx @skills-hub-ai/cli install <skill-slug>  # private org skills need the login

Then use it in Claude Code, Cursor, or any MCP-connected tool. Update everything later with npx @skills-hub-ai/cli update.

If an install of a public catalogskill is refused with a policy message, your organization's install policy blocked it; the message names the policy and an admin can adjust it. Your organization's own skills are never blocked.

5Create and publish

The intended pattern, and why governance stays out of your way:

Personal variants are frictionless. Take a base skill from the registry, extend it with your own tone and workflow, keep it private. No review, no approval, ever.
Review applies at the moment of sharing. When your skill should become something colleagues rely on, publish it to the organization. That is when ownership and (if your org requires it) approval attach.

Publish from the New org skill button on your organization page. Org skills offer three visibility levels: Organization (the default), Department, or Team. If your organization requires approval for new skills, your submission enters the governance queue and a reviewer publishes it; you can watch its status on the Governance page.

6Own what you publish

Every published skill lists a named owner: the person accountable for keeping it current. When the underlying process changes, ship a new version with a changelog line. Skills are plain markdown and exportable at any time; there is no lock-in.

Your team's private skill registry