Workspace default
Best for most hubs. Hubs that use the default get the same basic abilities.
Skills
A skill set is the group of skills a hub can use. You manage skill sets from Skills.
If a hub is the place to connect and a client is what connects, skills are what make the hub useful.
Each skill set also has a runtime. Runtime is the working setup behind those skills: language, location, speech defaults, blocked skills, live skill status, and updates.
Use Manage Updates when you need to decide whether an update belongs to a skill package, runtime container target, hub container target, or Billing check.
Start Here If
Section titled “Start Here If”- you need to choose between workspace default skills and a separate skill set;
- one hub needs different abilities or a slower update pace;
- paid Skill Store access, install state, update, or live skill status needs review;
- runtime config appears to affect more hubs than expected.
At a Glance
Section titled “At a Glance”| Question | Simple answer |
|---|---|
| What are skills? | Abilities a hub can use. |
| What is a skill set? | A group of skills assigned to one or more hubs. |
| What owns runtime config? | The skill set. |
| When should I use the default? | When most hubs should behave the same way. |
| When should I separate it? | When one hub needs different abilities, settings, or review. |
Shared vs Separate Skills
Section titled “Shared vs Separate Skills”Separate skill set
Best when one hub needs different abilities or a slower update pace.
Runtime config
Best when the skill set needs different language, location, speech, or blocked-skill defaults.
How Skill Sets Affect Hubs
Section titled “How Skill Sets Affect Hubs”Skill sets matter because permissions often refer to what a hub can do. When a skill is added, updated, removed, or changed, check whether permissions still make sense.
Use the workspace default when hubs should behave the same way. Create a separate skill set when one hub needs different abilities or a careful review before updates.
For a first setup, keep the workspace default unless you can clearly name what needs to be different.
Skill Set vs Runtime
Section titled “Skill Set vs Runtime”| Term | Plain meaning | Example question |
|---|---|---|
| Skill set | The group of skills a hub can use. | Should this hub have the same abilities as other hubs? |
| Runtime | The working setup behind the skill set. | Should these skills use a different language, location, or speech setup? |
| Runtime config | The guided settings for runtime defaults. | Do I need to change language, location, speech, or blocked skills? |
Skill Store
Section titled “Skill Store”The Skill Store lets you browse and add skills.
Skill cards can show:
- title and summary;
- category and tags;
- publisher;
- quality label;
- rating details when available;
- whether the skill is already installed;
- whether paid Skill Store access requires a plan that explicitly includes it.
Private memory is a Private or Team workspace skill path. Add thalovant-skill-memory only to the private skill set that should remember context, then store its scoped runtime token in the skill secret field. See Memory for the full setup and revoke test.
Installed Skills
Section titled “Installed Skills”The Installed view shows the skills already added to the selected skill set. Use it to:
- see installed state;
- review version labels;
- update skills when a newer release is available;
- remove skills when they are no longer needed;
- refresh live status.
Runtime View
Section titled “Runtime View”The Runtime view helps you answer:
- which skills are live right now;
- which skills need attention;
- whether the selected skill set is assigned to hubs;
- whether an update is available;
- whether runtime health looks normal after changes.
Runtime Config
Section titled “Runtime Config”Runtime config is where you adjust shared defaults for the selected skill set.
Set primary language, secondary languages, location, speech-to-text, and text-to-speech.
Block skills that should not load for this skill set.
Review the generated summary before saving so you know what will change.
Update Flow
Section titled “Update Flow”When a skill update is available:
- Review the skill title and quality label.
- Check which hubs use the affected skill set.
- Check runtime health so you know whether the skill set is ready for a restart.
- Apply the update when the workspace is ready.
- Return to Dashboard for the update summary and to Live Map for connection checks.
Skill updates change installed skill packages. Runtime updates change the core and messagebus images behind a runtime group. Hub updates change the listener and preview bridge images behind a hub. Use Manage Updates when Dashboard points to runtime or hub releases.
Skill Set Is Ready When
Section titled “Skill Set Is Ready When”A skill set is ready when:
- the assigned hubs are the hubs you meant to change;
- installed skills match the hub purpose;
- runtime defaults are still appropriate;
- skill updates have been applied or intentionally left for later;
- permissions have been reviewed after skill changes;
- Dashboard has no unexpected update or runtime warning.
Next Step
Section titled “Next Step”Read Runtime when you need the deeper model, or Configure Runtime when you are ready to change defaults.
Understand runtime
Configure runtime
Manage updates