Library
Library is the catalogue inside the Operations pane. It shows every operator the platform knows about, every skill and workflow each operator hosts, and the pack each came from. Use it to discover what is installed, inspect a skill before invoking it, and trace a skill back to the pack that provides it.
Layout
Section titled “Layout”The Library opens as a three-column browser inside the Operations pane:
| Column | What It Shows |
|---|---|
| Operators | The full operator list (e.g. pkm-operator, comms-operator, scheduling-operator, fleet-operator, secops-operator). Each row shows how many skills + workflows the operator currently hosts. |
| Operator detail | Selected operator’s identity, the pack(s) it ships from, the skills and workflows under it. |
| Skill / workflow inspector | Selected skill or workflow’s manifest — input contract, tool surface, scope requirements, model tier, last invocation. |
A pack filter row above the three columns scopes the catalogue to a single pack at a time, or shows all installed packs together. Manage in Settings jumps to the pack management surface.
A status row sits above the filter row, showing daemon state, inbox depth, and the active host.
What An Operator Is
Section titled “What An Operator Is”An operator is a long-running role a pack can declare. Operators host skills and workflows and accumulate domain-specific judgement over time (preferences, recipient picks, classifier corrections). The platform ships first-party operators for personal knowledge management, communications, scheduling, fleet health, security operations, and others; community packs can extend the operator set under the same shape.
See Operator and Pack for the substrate definitions.
What The Inspector Tells You
Section titled “What The Inspector Tells You”Selecting a skill or workflow opens the inspector. Useful for:
- Verifying what the skill will do before dispatching it (its tool surface).
- Confirming which scopes the skill requires and whether your current context can satisfy them.
- Looking up which pack the skill came from — including whether the pack is Sealed, Certified, Community, User-authored, or Imported.
- Checking when the skill last ran and what the outcome was.
If the skill belongs to a sealed pack, the inspector shows the redacted view the pack publisher allows — sealed packs do not expose their internal prompts or workflow graphs.
How Library Differs From Marketplace
Section titled “How Library Differs From Marketplace”| Surface | Purpose |
|---|---|
| Library | What is installed and reachable right now. Inspection of installed capability. |
| Marketplace | What is available to install. Discovery + trust evaluation before installation. |
The two complement each other: Marketplace decides what enters your platform, Library inspects what is already there.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Where To Check |
|---|---|
| Operator appears empty | The pack filter row — operator skills may be filtered out by the active pack scope. |
| Skill missing that you expected | Settings → Packs to confirm the pack is installed and enabled on this host. |
| Inspector shows redacted fields | The skill belongs to a sealed pack; redaction is by publisher policy. |
Related concepts
Section titled “Related concepts”- Packs and trust — the trust chain behind every operator and skill listed here
- Agency model — how the substrate composes operators + skills into authorised work