Bundled Skill

The bundled compozy skill ships inside the CompozyOS binary. It is the lowest-precedence source in the skills hierarchy and is available whenever skills.enabled is true.

CompozyOS currently ships one bundled skill: compozy. The skill lives at skills/compozy/SKILL.md with resource files under skills/compozy/references/. This layout is a normal skill directory, so the same content can be installed outside CompozyOS by coding agents that want CompozyOS operating guidance without importing the runtime.

Catalog

The current runtime does not ship aliases for previous alpha compozy-* bundled skill names. A caller that needs CompozyOS guidance should load compozy and then read the reference file selected by its router.

Reference files

The compozy skill body is a router. It keeps startup prompts small and sends agents to focused reference files:

How bundled loading works

Bundled loading follows the same registry path as other skills:

1. The binary exposes an embedded filesystem from the root skills package.
2. The daemon registry scans that filesystem during boot.
3. skills/compozy/SKILL.md is parsed with the same loader used for local skills.
4. Verification runs on the Markdown body.
5. The skill enters the global registry as source bundled.

Bundled content is immutable for the running process. It refreshes only when the binary changes. User, marketplace, extension, additional-root, workspace, and agent-local skills can still override the bundled compozy name by precedence. That is an override, not an alias.

Prompt behavior

The normal prompt catalog lists the bundled skill by name and description:

<available-skills>
  <skill name="compozy">Agent guide for operating CompozyOS. Use when working with CompozyOS sessions, agents, native tools...</skill>
</available-skills>

Agents resolve canonical compozy__skill_view through the active harness, then load the full router with the returned tool reference and { "name": "compozy" }. Operators can read the same body with:

compozy skill view compozy

Each turn resolves the current skill catalog. When it matches the startup catalog delivered in that request, or the catalog confirmed in an earlier turn of the same ACP process, the live section uses a compact unchanged marker. Changed catalogs are sent in full. Failed or canceled deliveries do not establish a reusable catalog, and fresh ACP processes establish their own context.

Agents and operators read a focused resource file instead of the whole manual when the router names one:

{ "name": "compozy", "file": "references/network.md" }

compozy skill view compozy --file references/network.md

With tools and skills enabled, startup includes the compozy router. The complete references/tools-and-skills.md and references/native-tools.md manuals stay available through compozy__skill_view; they are loaded on demand before the matching operation. If a result is truncated, the router explains how to use compozy__tool_artifact_read in the same workspace and follow next_offset through eof to recover the complete retained result. Display redaction remains in effect; agents do not bypass a denied read through CLI or filesystem access.

When tools are enabled but skills are disabled, capable sessions keep both complete tool manuals inline. This preserves operational guidance without enabling the skill registry or changing tool authorization. The daemon omits all tool guidance for memory extractor children, automatic title generation, and checkpoint summarization, whose roles transform supplied input into output. This uses the persisted role, including an extractor created through Spawn, rather than excluding every system, dream, or spawned session. Task workers, coordinators, dream curators, interactive sessions, and unknown roles retain the appropriate guidance when tools are enabled. Older checkpoint sessions without an explicit role also retain it. The role is preserved across resume and custom background-agent routing. Input-only roles also omit startup and live skill catalogs and situation context; their runtime identity and supplied instructions remain present. These prompt choices do not change permissions or explicit skill reads.

These selections provide contextual prompt help only. Tool registration, discovery, authorization, MCP, and the tools.enabled gateway switch keep their existing behavior. No additional configuration key or user-state migration is required.

Native tools and authority

The bundled compozy skill teaches agents how to find and use CompozyOS-native tools, but it does not grant tool access. Tool visibility and invocation are enforced by the tool registry, session scope, toolsets, approval policy, and the owning runtime service. compozy__* names are canonical ToolIDs, not guaranteed harness invocation names. Agents should resolve canonical compozy__tool_search, inspect candidates through canonical compozy__tool_info, and then call the dedicated tool reference returned by the active harness when it is available in the active scope.

The review submit path is the clearest example. The reviewer-facing prompt tells the session to load compozy and read references/tasks-and-orchestration.md, but the submit_run_review model-facing tool is available only when task.Service.LookupReviewForSession(session_id) finds an active bound review. When available, the tool persists the verdict through task.Service.RecordRunReview. The skill is instructional; the binding is the authority.

Related pages

• SKILL.md Format documents skill frontmatter, body conventions, sidecars, and resources.
• Skills Overview documents the full source hierarchy and prompt catalog.
• Tools documents native tool discovery and policy.
• Review Gate documents reviewer-bound verdict authority.