Skills, Tools, and Capability Discovery
Capability discovery decides what exists, what layer owns it, and whether to promote it into a skill, tool page, ecosystem page, workflow, graph object, or source ledger. Source: User request, 2026-06-27; Capability Routing Map
When To Use This
Use this page when adding a tool, installing a skill, auditing MCP/CLI coverage, or deciding whether a repeated workflow needs codification. Source: Ecosystem Capability Coverage, 2026-06-27
Decision Matrix
| Signal | Promote to | Verification |
|---|---|---|
| Repeatable procedure | Skill page and executable SKILL.md |
skills:check |
| Product/capability facts | Tool or ecosystem page | Routing summary and source evidence |
| Cross-tool principle | Concept page | Links from owning tools/skills |
| Registry/source snapshot | Source/ingest page or raw file | Raw artifact path |
| Reusable operating context | Workflow manifest plus durable object bindings | brain runtime and routing checks |
Core Model
A capability is not automatically a skill. Skills tell agents how to execute. Tool pages explain products and tradeoffs. Concept pages generalize across tools. Ecosystem pages route vendor families. Workflows bind reusable procedures to graph objects, sources, tools, and proof. Source: Wiki Brain Operating Model, 2026-08-10
Tool And Skill Routing
Use skills.sh and Agent Operations Skills to discover installable procedures, MCP Registry for MCP surfaces, service CLI seeds for first-party CLIs, and Ecosystem Capability Coverage to decide whether coverage is real enough to promote. Source: Ecosystem Capability Coverage, 2026-06-27
Failure Modes
- Installing a skill because it exists, not because it owns a repeated workflow.
- Creating a tool page that is just a skill mirror.
- Treating MCP availability as permission to mutate live services.
- Letting a generated projection become the source of truth.
Evidence And Timeline
Promotion proof is a source registry signal, a canonical page or skill, a routing entry, relevant workflow/object bindings, and a verification path. Source: Ecosystem Capability Coverage, 2026-06-27
Concept Position
| Field | Value |
|---|---|
| Concept family | Agent harness and runtime primitives |
| Concept owned | Capability discovery decides what exists, what layer owns it, and whether to promote it into a skill, tool page, ecosystem page, pack, or s... |
| Category map | Concept System Map |
Timeline
- 2026-07-01 | Concepts category refresh added this page to the Agent harness and runtime primitives family, linked it to Concept System Map, and kept it standalone because it owns this reusable mental model: Capability discovery decides what exists, what layer owns it, and whether to promote it into a skill, tool page, ecosystem page, pack, or s... Source: User request, 2026-07-01
- 2026-06-27 | Canonical cluster page created to make skill/tool/capability discovery a first-class synthesis instead of a pile of registry snapshots. Source: User request, 2026-06-27