Docs/Context Studio/Skill Registry

Skill Registry

Browse the read-only catalog of every capability Orion can invoke — live compute skills and authored knowledge skills — with parameters, role gating, and source.

LuminaryWeaverTracerUpdated June 2026 · 6 min read

✦

In this section

Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.

💡

Tip

What it is — A read-only catalog of every capability Orion (and every other AI surface) can invoke, split into compute skills and knowledge skills.
When to use it — When you want to see exactly what Orion is able to do, inspect a skill's parameters or required role, or confirm a Domain Skill has been registered.
Where to find it — Context Studio → AI Context group → Skill Registry.
Who can use it — Tracer, Weaver, and Luminary. The list is role-filtered, so you only see skills your role is allowed to run.

The Skill Registry is the single, shared catalog of capabilities behind Orion. Anything Orion can do at runtime is enumerated here, so you can understand and audit Orion's reach without reading code. The same registry powers every AI surface — Orion chat, AI Analysts, MCP, Slack, Sheets, and Embedded all reach the same skills — which means what you see here is exactly what those surfaces use.

The page is a viewer, not an editor. You cannot create or delete skills here. Compute skills appear automatically from the platform's tool engine, and knowledge skills are authored on the Domain Skills page.

Overview

Open Skill Registry and you get a flat list of skill cards. Each card shows a type badge (compute or knowledge), the skill's title, its slug, and — when access is gated above the default — a role badge such as weaver+. A short description sits under the heading.

At the top right is a type filter with three pills: All, Compute, and Knowledge. Selecting a pill refetches the list filtered to that type. Click any card to expand it and reveal its execution reference, parameter list, status, and source.

The registry is consumer-agnostic by design: it wraps the existing execution engine rather than forking it. Compute skills are derived live from the tool engine every time the list loads, so the catalog can never drift from what Orion actually runs.

When to use it

You want a complete inventory of what Orion is capable of in this workspace.
You need to check which parameters a skill accepts before relying on it in a question or an automation.
You want to confirm that a Domain Skill you authored is now registered as a knowledge skill.
You are auditing access and need to see the minimum role required to run a given capability.
You are debugging why Orion did not use an expected capability, and want to verify the skill exists and is active.

Concepts

Term	What it means
Compute skill	A live tool from the platform's tool engine (for example, querying the warehouse). These are executable, derived automatically, and never authored by hand. Their source is `builtin`.
Knowledge skill	An authored Domain Skill — business context and instructions that teach Orion how to think about an area. These add knowledge rather than execution. Their source is `workspace`.
Execution ref	The underlying engine entry a compute skill maps to. Knowledge-only skills have no execution ref and cannot be invoked directly.
Parameters	The input fields a skill accepts, shown as `name : type` chips when a card is expanded.
Status	Whether the skill is `active`. The registry only lists active skills.
Source	Where the skill comes from: `builtin` (the tool engine) or `workspace` (authored in this workspace).
Min role	The minimum role allowed to run the skill — `tracer`, `weaver`, or `luminary`. The default is `tracer`; anything stricter shows a `role+` badge.

Getting started

You need a Tracer, Weaver, or Luminary role to open Context Studio. No setup is required for compute skills — they populate themselves. Knowledge skills appear here only after they have been authored and saved on the Domain Skills page.

To open the registry:

Open Context Studio

Navigate to Context Studio from the main app navigation.

Go to the AI Context group

In the left navigation, find the AI Context group.

Select Skill Registry

Click Skill Registry. The catalog loads with the All filter selected.

Step-by-step

Choose a type

Use the All / Compute / Knowledge pills at the top right to narrow the list. Compute shows live tools; Knowledge shows authored Domain Skills; All shows both.

Scan the cards

Each card shows the type badge, the title, the slug (in monospace), and an optional role badge. Read the one-line description to understand what the skill does.

Expand a skill

Click a card to expand it. The card border highlights and a detail panel opens below.

Read the details

In the expanded panel you can see the Execution ref, the number of Parameters, the Status, and the Source. Parameters are listed individually as name : type chips.

Collapse

Click the card again to collapse it. Only one card is expanded at a time.

Examples

Suppose you want to confirm Orion can query the warehouse and check what that capability requires.

Filter to compute

Click the Compute pill. The list narrows to live tools only — these have the source builtin.

Find the tool

Locate the SQL/query tool card. Its type badge reads compute and its slug is shown in monospace next to the title.

Expand and inspect

Click the card. You will see an Execution ref matching the tool, a Parameters count with chips such as sql : string, Status of active, and Source of builtin.

A compute skill is presented to the registry roughly like this — title is derived from the slug, and the parameters come straight from the tool's input schema:

json

{
  "slug": "run_sql",
  "type": "compute",
  "title": "Run Sql",
  "description": "Run a read-only SQL query against the connected warehouse.",
  "execution_ref": "run_sql",
  "parameters": { "properties": { "sql": { "type": "string" } } },
  "min_role": "tracer",
  "status": "active",
  "source": "builtin"
}

A knowledge skill authored as a Domain Skill appears with the knowledge type and a workspace source, and has no execution ref because it adds context rather than running anything.

Best practices

Use the Compute filter when you are reasoning about what Orion can do, and Knowledge when you are reasoning about what Orion knows.
Treat the registry as the source of truth for capability questions. Because compute skills are derived live, this list always reflects the real tool engine.
When a Domain Skill is not showing up here, fix it at the source on Domain Skills rather than expecting an edit control here.
Check the Min role badge before assuming a teammate can run a skill — the catalog you see is filtered to your own role, so a colleague with a lower role may see fewer cards.

Tips

💡

Tip

The role badge only appears when a skill is gated above the default Tracer level — for example weaver+. If a card shows no role badge, any role that can open the registry can run it. Even so, the registry's role filter is a coarse pre-filter; the real, fail-closed permission check happens at execution time.

Common mistakes

⚠️

Warning

Treating the registry as an editor. There are no create, edit, or delete controls here. Compute skills come from the tool engine automatically; knowledge skills are authored on Domain Skills.

Assuming every skill is runnable. Knowledge-only skills have no execution ref. They contribute context to Orion but cannot be invoked as a tool.

Expecting to see another role's view. The list is filtered to your role. A skill missing from your view may simply require a higher role than you hold.

Troubleshooting

Symptom	Cause	Fix
The page shows "Loading skill registry…" and never finishes	The registry request failed	Reload the page; if it persists, confirm you are signed in with a Tracer or higher role.
"No skills found." empty state	The current type filter matched nothing	Switch the filter back to All. Compute skills appear automatically from the tool engine; knowledge skills only appear after they are authored in Domain Skills.
A Domain Skill you wrote is not listed	It has not been saved as an active knowledge skill, or the Compute filter is active	Set the filter to Knowledge or All, then save the skill on the Domain Skills page if it is still missing.
A skill you expected is missing entirely	Its minimum role is higher than yours	The catalog is role-filtered; ask a Weaver or Luminary to confirm, or check your role under workspace settings.
An expanded card shows no Execution ref	It is a knowledge-only skill	This is expected — knowledge skills add context and are not directly invokable.

Domain Skills — author the knowledge skills that appear here.
Orion — the AI layer that invokes these skills.
AI Operations — monitor how skills and AI calls are actually used.
Context Studio overview — the full intelligence layer this page belongs to.