Canopy
Canopy is arbora's front door: the live architecture website, which grows
into a richer front door over time. This skill is the entry point that tells a
harness how to use the ecosystem through arbora and canopy. The arbora MCP
server is the one door to the ecosystem. It exposes six intent
tools. Each takes op="<operation id>" with params={...}, or a
natural-language intent="..." with op empty.
| Tool |
Use it to |
find |
Discover operations, connector tools, skills and agents, with their params |
ask |
Read: graph questions, records, workstreams, run status |
why |
Explain a result, a decision or a lineage |
write |
Record facts, checkpoints and other caller-owned writes |
act |
Run things: fleet tool calls, registered agents, workflows |
manage |
Configure the platform |
Rules, in order
- Discover before concluding. Call
find(intent="...") before you decide
that a capability is absent. find(op="<id>") returns one operation's spec
and params schema.
- Preview a write, then resubmit.
write, act and manage answer a
first call with a preview and a plan_ref. Read it, then resubmit the same
call with that plan_ref and execute=true. Operations that declare no
confirmation, such as the workstream operations, run on the first call.
- Reach a fleet tool through
act with fleet.call. Pass
params={"server": ..., "tool": ..., "arguments": {...}}. find returns
the server and tool names.
- Run a registered agent through
act with agents.run. Pass the agent
profile and the task as input; report the run result as it is.
The shared workstream
Every coding harness that carries this plugin joins one workstream per
workspace. The plugin attaches the session on the first prompt and records a
checkpoint before compaction. To hand off on purpose, follow the
session-handoff skill: write with op="workstream.checkpoint". To pick up
what an earlier session left, ask with op="workstream.get" and the current
working directory as workspace_root.
The status line
A plugin cannot set the main status line of every harness. To show the
workstream and the sign-in state, select the command
arbora plugin statusline --harness <profile> as the harness status line
command in its settings.
Sign-in
The harness signs in to the door itself through the native client, with an
authorization code flow in the browser. A harness whose hooks run commands also
needs arbora plugin login --harness <profile> once; until then each hook
prints a one-line AUTH_REQUIRED note and never blocks the session.
1---2name: canopy3description: >-4 Canopy is arbora's front door: the live architecture website and the entry5 point to the ecosystem through arbora's MCP door. Use it to reach every6 operation, connector tool, skill and agent from this coding harness with the7 six intent tools find, ask, why, write, act and manage. Use when a task needs8 platform knowledge, a connector, a registered agent or the shared workstream;9 before concluding that a capability is missing; or when a write needs a preview.10license: MIT11metadata:12 source: https://skillmd.com/skills/knuckles-team/canopy13 domain: core14 skill_type: skill15 tags: [arbora, door, mcp, intent-tools, workstream]16 version: '1.6.0'17---1819# Canopy2021Canopy is arbora's front door: the live architecture website, which grows22into a richer front door over time. This skill is the entry point that tells a23harness how to use the ecosystem through arbora and canopy. The arbora MCP24server is the one door to the ecosystem. It exposes six intent25tools. Each takes `op="<operation id>"` with `params={...}`, or a26natural-language `intent="..."` with `op` empty.2728| Tool | Use it to |29|---|---|30| `find` | Discover operations, connector tools, skills and agents, with their params |31| `ask` | Read: graph questions, records, workstreams, run status |32| `why` | Explain a result, a decision or a lineage |33| `write` | Record facts, checkpoints and other caller-owned writes |34| `act` | Run things: fleet tool calls, registered agents, workflows |35| `manage` | Configure the platform |3637## Rules, in order38391. **Discover before concluding.** Call `find(intent="...")` before you decide40 that a capability is absent. `find(op="<id>")` returns one operation's spec41 and params schema.422. **Preview a write, then resubmit.** `write`, `act` and `manage` answer a43 first call with a preview and a `plan_ref`. Read it, then resubmit the same44 call with that `plan_ref` and `execute=true`. Operations that declare no45 confirmation, such as the workstream operations, run on the first call.463. **Reach a fleet tool through `act` with `fleet.call`.** Pass47 `params={"server": ..., "tool": ..., "arguments": {...}}`. `find` returns48 the server and tool names.494. **Run a registered agent through `act` with `agents.run`.** Pass the agent50 profile and the task as `input`; report the run result as it is.5152## The shared workstream5354Every coding harness that carries this plugin joins one workstream per55workspace. The plugin attaches the session on the first prompt and records a56checkpoint before compaction. To hand off on purpose, follow the57`session-handoff` skill: `write` with `op="workstream.checkpoint"`. To pick up58what an earlier session left, `ask` with `op="workstream.get"` and the current59working directory as `workspace_root`.6061## The status line6263A plugin cannot set the main status line of every harness. To show the64workstream and the sign-in state, select the command65`arbora plugin statusline --harness <profile>` as the harness status line66command in its settings.6768## Sign-in6970The harness signs in to the door itself through the native client, with an71authorization code flow in the browser. A harness whose hooks run commands also72needs `arbora plugin login --harness <profile>` once; until then each hook73prints a one-line `AUTH_REQUIRED` note and never blocks the session.