Add Your Own Skill

You can run your own skills next to the ones from the Skill Store. Point Thalovant at the place your skill lives — a Git repository or a Python package — and it installs into the skill set you choose. No packaging pipeline, no support ticket.

At a Glance

Question	Simple answer
What is this about?	Running a skill you wrote on your own hubs.
Where do I start?	Skills → Skill Store → Add custom skill.
What is done?	Your skill shows as installed and the skill set is healthy.

Before You Start

Confirm:

• your skill is a standard OVOS skill (it installs with pip);
• you know where it lives: a Git repository URL or a package name;
• the skill set (and hub) you want it on already exists;
• private skills need a workspace plan that includes private skill sets.

Add the Skill

1. Open Skills and select the skill set that should run your skill.
2. Open the Skill Store tab and choose Add custom skill.
3. Give the skill a name people will recognize.
4. Paste the source: your Git repository URL (a specific commit or tag keeps installs predictable) or the package name.
5. For a private repository, add a read-only access token in the Git access fields — it is stored securely, used only to install, and never shown again.
6. Save. The skill set restarts and installs your skill; the row shows live install status until it settles.

Custom skills stay private to your workspace. They install into the one skill set you chose and use your existing plan limits — there is no separate subscription.

Update Your Skill

When you push improvements:

1. Open your skill’s card in the store view and choose Publish release (owners see this on their own custom skills).
2. Name the version and pick the branch or the exact commit to release.
3. Publish. Skill sets running your skill show Update available; apply it with one click, or roll your own skill sets in the same step.

Tip

Releases are just catalog entries. Nothing rebuilds and nothing redeploys — the runtime installs the version you published and reports back when it is live.

If Something Fails

• The skill row shows the install error and the rest of the skill set keeps running — one bad skill never takes a hub down.
• Fix the code, publish a new release, and apply it.
• A private-repository install that cannot authenticate reports it plainly: check the Git access token on the skill set.

Your Skill Is Ready When

• the skill shows installed in the skill set;
• the skill set reports healthy;
• your hub answers to the skill’s intents;
• publishing a release moves the version shown on the skill row.

Next Step

See Skills for how skill sets share skills across hubs, and Manage Updates for the wider update story.