@controllerai/cli 0.2.20 → 0.2.22

package/skills-mcp/manifest.json

@@ -0,0 +1,200 @@
+{
+  "schemaVersion": 1,
+  "skillSetVersion": "2026.09.15.2",
+  "minCliVersion": "0.2.0",
+  "latestCliVersion": "0.2.22",
+  "skills": [
+    {
+      "name": "controllerai-start",
+      "files": [
+        {
+          "path": "controllerai-start/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-start/SKILL.md",
+          "sha256": "65b35ecd4c5a94bd991f85aaaa6c26f1d551f646da136757c5a8a853b1f7389c",
+          "size": 11172
+        },
+        {
+          "path": "controllerai-start/references/mcp-tool-map.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-start/references/mcp-tool-map.md",
+          "sha256": "8dc049be93070daa4ad66d09883f2887cb130cf3d54cc50056a202a2e118a925",
+          "size": 26761
+        }
+      ]
+    },
+    {
+      "name": "controllerai-workflows",
+      "files": [
+        {
+          "path": "controllerai-workflows/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-workflows/SKILL.md",
+          "sha256": "94f6f343c3cc2a469cdd2247f8bcc9cb8fa56290a35d988409155d22f5c5c1f9",
+          "size": 9549
+        },
+        {
+          "path": "controllerai-workflows/references/command-map.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-workflows/references/command-map.md",
+          "sha256": "3a1fe464d00c2ae734dab11db3b338436d91a9c32dd8a1b3f1843ac4200a739c",
+          "size": 89
+        }
+      ]
+    },
+    {
+      "name": "controllerai-node-config",
+      "files": [
+        {
+          "path": "controllerai-node-config/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-node-config/SKILL.md",
+          "sha256": "7fbc68a24ccc08c04be8b6c4184b74b238058b637e4203293e0c5eae332bac2d",
+          "size": 11678
+        },
+        {
+          "path": "controllerai-node-config/references/prop-and-readiness.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-node-config/references/prop-and-readiness.md",
+          "sha256": "87da8b25c8303818b1f0c677b2cc6f7121910e8fcd94371ed5bc2065f7b7b845",
+          "size": 5344
+        }
+      ]
+    },
+    {
+      "name": "controllerai-expressions",
+      "files": [
+        {
+          "path": "controllerai-expressions/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-expressions/SKILL.md",
+          "sha256": "c54f8c3176ffe48ca7aa78cd85151a1edf1f0083f7cd8b906b5d1d2ff5f5cc20",
+          "size": 10495
+        },
+        {
+          "path": "controllerai-expressions/references/dsl-and-recipes.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-expressions/references/dsl-and-recipes.md",
+          "sha256": "741b03033cb655dde95be99dcf6e00295b1b2d4f385ad42bbf4bb3c4001c9973",
+          "size": 4915
+        }
+      ]
+    },
+    {
+      "name": "controllerai-flow-control",
+      "files": [
+        {
+          "path": "controllerai-flow-control/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-flow-control/SKILL.md",
+          "sha256": "4bacfc3b7501565e0e5984b19d9223da1b5bf770875db804b5e6827d33efa967",
+          "size": 12367
+        },
+        {
+          "path": "controllerai-flow-control/references/patterns.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-flow-control/references/patterns.md",
+          "sha256": "a849179afb512e8fc0c3c833a1a2c737c5108e8ab8941c9fa261767671eceb01",
+          "size": 4704
+        }
+      ]
+    },
+    {
+      "name": "controllerai-runs",
+      "files": [
+        {
+          "path": "controllerai-runs/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-runs/SKILL.md",
+          "sha256": "ce8109606899a36dd298aa7fc41ff2288f62bfe9adeae0806b95fd22a317fe27",
+          "size": 9312
+        },
+        {
+          "path": "controllerai-runs/references/debugging.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-runs/references/debugging.md",
+          "sha256": "616d13ea43785e4d11bdb50b9e4098126fbc470ee2568b250e1af5f15cab3edf",
+          "size": 3162
+        }
+      ]
+    },
+    {
+      "name": "controllerai-triggers",
+      "files": [
+        {
+          "path": "controllerai-triggers/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-triggers/SKILL.md",
+          "sha256": "0797e2070acbd674deca6b659d467d1cc5a86cb26120e489c52d10cb58fc044b",
+          "size": 12374
+        },
+        {
+          "path": "controllerai-triggers/references/lifecycle.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-triggers/references/lifecycle.md",
+          "sha256": "519d9f858ee2ec8ab5f1c988e547f5a8c5478f4da3d454236354ade9800ed044",
+          "size": 3438
+        }
+      ]
+    },
+    {
+      "name": "controllerai-data",
+      "files": [
+        {
+          "path": "controllerai-data/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-data/SKILL.md",
+          "sha256": "d17cfcda2abbccf6463edc6331c091175f7c7d92f6a2ce69dccc6d0fa4188e34",
+          "size": 12477
+        },
+        {
+          "path": "controllerai-data/references/data-rails.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-data/references/data-rails.md",
+          "sha256": "6d22c72b3b2da83cfaf078683ef41ec2b6f3b9b249789ab2bd23d01d6710c261",
+          "size": 2843
+        }
+      ]
+    },
+    {
+      "name": "controllerai-ai-nodes",
+      "files": [
+        {
+          "path": "controllerai-ai-nodes/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-ai-nodes/SKILL.md",
+          "sha256": "e6071d906cf1df7665cb63274a579d7a0f46796440112a74f190338389b2db33",
+          "size": 9484
+        },
+        {
+          "path": "controllerai-ai-nodes/references/selection-and-testing.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-ai-nodes/references/selection-and-testing.md",
+          "sha256": "66b235b9e81645ab877b31443505c7b07ea3f2e5a357053f266c121415f8cf5c",
+          "size": 3111
+        }
+      ]
+    },
+    {
+      "name": "controllerai-integration-actions",
+      "files": [
+        {
+          "path": "controllerai-integration-actions/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-integration-actions/SKILL.md",
+          "sha256": "ceabf8fc8d964e94a0feabd95d1a452cdf5d8cfca83106f1d388f7de4f9a5567",
+          "size": 10076
+        }
+      ]
+    },
+    {
+      "name": "controllerai-agents",
+      "files": [
+        {
+          "path": "controllerai-agents/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-agents/SKILL.md",
+          "sha256": "20ac5f23a1579cbaf109c958a211e5d1ee9859db430479e3e00ed81136fbf682",
+          "size": 12715
+        },
+        {
+          "path": "controllerai-agents/references/instructions-and-versioning.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-agents/references/instructions-and-versioning.md",
+          "sha256": "88b059e74aef03ccb12a53815d1090e5449090ff6dfd863b6cef5a12b434cb65",
+          "size": 5644
+        }
+      ]
+    },
+    {
+      "name": "controllerai-template-setup",
+      "files": [
+        {
+          "path": "controllerai-template-setup/SKILL.md",
+          "url": "https://getcontroller.ai/skills-mcp/2026.09.15.2/controllerai-template-setup/SKILL.md",
+          "sha256": "a530a694257ccf7622c4f16579cad91bf96ac06dfc7cbd82a919914abe387e52",
+          "size": 609
+        }
+      ]
+    }
+  ]
+}

package/skills/controllerai-agents/references/command-reference.md

@@ -1,205 +0,0 @@
-# Controller AI agents
-
-An agent has one mutable draft and immutable published versions. Build instructions, tools, permissions, and files on the draft; verify in Test; publish last. Draft edits never update Live by themselves.
-
-
-
-- Attach one ready action directly instead of wrapping it; see Choose the capability architecture.
-- Choose confirmation before attaching a consequential tool; see Create and assemble the draft.
-- Use one conversation on an explicit rail for each verification task; see Verify the draft as an agent.
-- Resolve pending requests in that same conversation; see Verify the draft as an agent.
-- Enablement is runtime state, not publication; see Create and assemble the draft.
-- Publish authorized workflow dependencies, preflight, then publish the agent; see Publish in dependency order.
-- Draft-only means stop before publish; draft evidence never proves Live. See Publish in dependency order.
-
-## 1. Choose the capability architecture
-
-- Use `controllerai-integration-actions` when one existing app operation completes it.
-- Use a workflow tool for multiple steps, transformations, branching, looping, durable state, triggers, a custom typed contract, or reusable business logic.
-- Put judgment, tool-selection rules, tone, and escalation in instructions; put stable sources in knowledge files.
-
-Do not create a one-node workflow merely to expose a ready action, or replace orchestration with several independent direct actions when ordering or data handling must be deterministic.
-
-## 2. Build and verify capabilities
-
-For a ready action, follow `controllerai-integration-actions`: discover exact identities, select a connection, decide confirmation, then attach.
-
-For every workflow tool, load the relevant workflow skills and test the development state before attaching:
-
-```bash
-cai use <workflowId>
-cai flow get <flowId> --json
-cai run flow <flowId> --inputs values.json --json
-```
-
-MCP: there is no pin; pass `workflowId` to `flow_get` and `run_flow`, pass parsed `inputs`, and set `waitSeconds`.
-
-Capture the successful execution ID. Inputs become tool parameters and outputs its result. Require a nonempty output contract and verify the run returns it.
-
-## 3. Create and assemble the draft
-
-
-Read [instructions-and-versioning.md](instructions-and-versioning.md) before publishing or explaining Test versus Live behavior.
-
-```bash
-cai agent create --name "<agent name>" --instructions-file instructions.md --json
-```
-
-MCP: `agent_create` takes complete Markdown in `instructions`; it cannot read `instructions.md`.
-
-```bash
-cai agent add-action <agentId> \
-  --integration <integrationSlug> \
-  --action <actionKey> \
-  --connection <connectionId> \
-  --description "Use when ..." \
-  --json
-
-cai agent add-workflow <agentId> \
-  --workflow-id <workflowId> \
-  --flow <flowId> \
-  --description "Use when ...; accepts ...; returns ..." \
-  --json
-```
-
-MCP: use `agent_tool_action_add` or `agent_tool_workflow_add`; `requireConfirmation` is optional and defaults to `false`.
-
-```bash
-cai agent add-file <agentId> --file <path> --space <knowledge|shared> --json
-cai agent files <agentId> --space <knowledge|shared> [--live] --json
-cai agent tools <agentId> --json
-cai agent get <agentId> --json
-```
-
-MCP: use `agent_knowledge_file_add` or `agent_workspace_file_add` with inline `content`; `agent_file_list` uses `environment: dev|live`. Shared runtime files update live immediately.
-
-The default is no approval: attached actions and workflow tools run without a human approval step unless `requireConfirmation` is `true`, and omitting `--require-confirmation` has the same behavior. When attaching an action that sends, posts, spends, or deletes, choose `true` or explicitly tell the user that it will run unattended. Mention the confirmation choice in the report to the user; `cai agent update-tool` can change it later.
-
-Keep the two modes straight:
-
-| Context | Test / draft conversation | Live / shared conversation |
-| --- | --- | --- |
-| Agent configuration | Current mutable draft | Latest published immutable agent version |
-| Workflow tools | Current workflow development heads | Each workflow's latest live release; never pinned |
-| Reference files | Current draft knowledge files | Knowledge frozen into the published agent version |
-| Runtime files | Current live runtime files, overlaid by development/test runtime files at the same path | Current live runtime files only |
-| Access | Owner only | Owner, plus organization members when shared; non-owners never see the draft |
-
-Version pinning for workflow tools does not exist. Live tools track the latest release. If asked to freeze one, explain this, attach with policy `latest`, and never abandon the attachment.
-
-Publishing snapshots versioned fields, moves the live pointer, and restamps every existing live conversation. It does not snapshot the runtime model. This cutover interrupts in-flight answers and expires pending approvals; time it accordingly.
-
-Runtime lifecycle changes do not require publishing:
-
-```bash
-cai agent update <agentId> --disabled --json
-cai agent update <agentId> --enabled --json
-cai agent delete <agentId> --confirm --json
-```
-
-MCP: draft edits use `agent_update`; runtime uses `agent_set_enabled`; `agent_delete` has no `confirm`. Disable pauses runtime. Soft delete revokes access and requests session termination; there is no CLI restore.
-
-## Runtime usage boundary
-
-
-## 4. Verify the draft as an agent
-
-Saving the draft updates the agent's Test environment — there is no separate deploy step. Test conversations run each workflow tool's DEVELOPMENT version.
-
-```bash
-cai agent test <agentId> --draft --message "<representative request>" --json
-cai agent conversation history <conversationId> --json
-```
-
-MCP: `agent_test` requires `rail: draft` or `rail: live` and takes `waitSeconds`.
-
-`agent test` always creates a conversation. Use it for a one-shot check. When a task may need follow-up or approval, create one conversation on the requested rail, capture its ID, and reuse it:
-
-```bash
-cai agent conversation create <agentId> --draft --title "<test case>" --json
-cai agent conversation send <conversationId> --message "<request>" --wait --json
-```
-
-Do not resend the request or create a replacement after an approval pause. A required post-publish Live check is a separate rail task and gets one fresh Live conversation.
-
-Test positive and negative tool selection, exact arguments, results, errors, and knowledge. Offer the returned `appUrl`; on MCP, call `agent_present` and relay the returned card.
-
-- For a workflow tool, correlate a side-effectful call with its terminal workflow execution ID.
-- For a direct integration action, inspect persisted conversation action events/run result and the intended external effect. Direct actions do not create workflow execution IDs.
-
-For a pending approval, inspect the exact request first:
-
-```bash
-cai agent conversation approve <conversationId> --request <requestId> --json
-cai agent conversation deny <conversationId> --request <requestId> --message "<reason>" --json
-```
-
-The server resolves the tool from the request ID. Do not approve merely to continue. Resolve every pending request before publishing; approval or denial resumes this conversation, while publishing expires it.
-
-After `cai agent remove-tool`, test one request that must no longer use the removed capability and one retained capability.
-
-## 5. Publish in dependency order
-
-For attached workflows only:
-
-```bash
-cai use <workflowId>
-cai workflow status --json
-cai workflow publish --name "<release>" --json
-```
-
-MCP: there is no `use`; pass `workflowId` to `workflow_status` and `workflow_publish`.
-
-Publish a workflow only when its verified development state must go live and the user authorized it. A workflow publish already followed by a live agent changes that tool's live behavior immediately; do not republish the agent merely to pick it up.
-
-For a draft-only request, stop after Test evidence. Do not publish a workflow or agent merely because it is ready.
-
-Then publish the agent:
-
-```bash
-cai agent publish-preflight <agentId> --json
-cai agent publish <agentId> --name "<release>" --json
-cai agent versions <agentId> --json
-cai agent test <agentId> --live --message "<representative request>" --json
-```
-
-MCP: `agent_test` requires `rail: draft` or `rail: live` and takes `waitSeconds`.
-
-`publish-preflight` is the arbiter of structural readiness. Report blockers and stop. With none and an authorized release, publish, except an error you actually watched happen; that blocks even a green preflight.
-
-Email verification is not a publishing prerequisite. An unclaimed agent-created account may publish; email claiming only raises its monthly usage cap and enables account recovery.
-
-Use one loop: edit draft, read back, verify Test, publish, verify Live. Published versions have no rollback. Recover forward from `agent versions`; restore workflow definitions with history/restore, then republish. Workflow releases, action grants, and runtime files are live-bound; see [instructions-and-versioning.md](instructions-and-versioning.md). After detaching an action, publish to remove it from the published list.
-
-Draft evidence does not prove the live agent. Test is owner-only; shared users always run the latest published agent version and never see draft instructions, tools, or knowledge.
-
-## 6. Offer Slack and organization sharing
-
-After publish, offer product setup for Slack. Agents remain private unless the user requests organization access:
-
-```bash
-cai agent visibility <agentId> --value organization --json
-```
-
-Members use the published version. Direct actions use the owner's external account and organization usage pool. Grant changes affect Live immediately; private visibility revokes access.
-
-## Before you finish
-
-```bash
-cai agent tools <agentId> --json
-cai agent conversation list <agentId> --mode dev --json
-cai data query --type custom.<type> --env dev --json
-cai agent conversation history <conversationId> --json
-cai agent publish-preflight <agentId> --json
-cai agent versions <agentId> --json
-cai agent test <agentId> --live --message "<representative request>" --json
-```
-
-Run the last three commands only for an authorized release. For Live verification, use `--mode live` and `--env live` in the same pair.
-
-- Conversation list must show the captured ID on the requested rail, without retry-created duplicates.
-- History must show the intended tool arguments, terminal result, and no unresolved permission request.
-- For stateful behavior, the same-rail data query must show the expected record; an assistant reply is not proof.
-- A release requires clean preflight, agent version read-back, and one fresh Live conversation. Draft-only work must remain unpublished.
-
-Report the agent ID/version, tools and confirmation policies, execution or direct-action evidence, rail state, connections, access, and anything unverified.

package/skills/controllerai-ai-nodes/references/command-reference.md

@@ -1,98 +0,0 @@
-# Controller AI AI nodes
-
-
-
-- Use native Ask AI for a bounded AI step; see Configure Ask AI in dependency order.
-- Keep an existing Ask AI node unless the requested component changes; see Configure Ask AI in dependency order.
-- Set reload selectors before fetching live model options; see Configure Ask AI in dependency order.
-- Never invent or hardcode a model ID; see Configure Ask AI in dependency order.
-
-## Choose the AI surface
-
-- Use Ask AI for one bounded transformation with explicit inputs and output contract.
-- Use a Controller AI agent for conversational judgment, multiple tools, durable instructions, and knowledge files. Load `controllerai-agents`.
-- Use `registry_agent` workflow actions only when a workflow must create/message a platform agent conversation or manage its files; discover the exact action and props rather than treating the whole agent as one node.
-
-## Configure Ask AI in dependency order
-
-For a bounded workflow transformation, use the native Ask AI component. Do not replace it with a provider integration action or delete an existing Ask AI node to bypass configuration.
-
-Discover the current component instead of hardcoding a key:
-
-```bash
-cai integration actions "ask AI" --json
-cai integration action --integration <nodeSlug> --key <nodeKey> --json
-cai node init --flow <flowId> --node <nodeSlug> --key <nodeKey> --name "<result produced>" --json
-cai node status <nodeId> --json
-```
-
-Typical selectors are provider, model, prompt/user message, and response data type. Trust current prop metadata over these names.
-
-1. Set the provider or other `reloadProps` selector.
-2. Re-read props.
-3. Fetch live model options; never invent a model identifier.
-4. Set the returned model value.
-5. Set the response type.
-6. Author the prompt with expression context.
-
-```bash
-cai node set <nodeId> --prop <providerProp> --value '<provider>' --json
-cai node props <nodeId> --json
-cai node options <nodeId> --prop <modelProp> --query '<model family>' --json
-cai node set <nodeId> --prop <modelProp> --value '<returned value>' --label '<returned label>' --json
-cai expr set <nodeId> --prop <promptProp> --js '<prompt expression>' --json
-```
-
-MCP: `node set` and `expr set` both use `node_prop_set`; pass exactly one of `value` or `js` here.
-
-Model catalogs, availability, and prices change. Use current options and the user's cost/quality preference. If the requested model is absent, leave it unset, report it, and ask; never substitute.
-
-## Prefer typed output for downstream logic
-
-If downstream nodes need fields, create a small `custom.*` shape first:
-
-```bash
-cai schema create custom.classification \
-  --field category:text:"Category" \
-  --field confidence:number:"Confidence" \
-  --field rationale:text:"Rationale" \
-  --json
-cai node set <nodeId> --prop <responseTypeProp> --value 'custom.classification' --json
-```
-
-Tell the model exactly what each field means, allowed values, and how to represent uncertainty. Never parse free-form prose downstream when a structured response contract is available.
-
-## Prompt contract
-
-A useful workflow prompt contains only behavior-changing material:
-
-- Task and audience
-- Actual input data through exact bindings
-- Decision rules and constraints
-- Required output fields/format
-- Explicit uncertainty or no-data behavior
-
-Avoid filler personas, repeated instructions, and claims about data not present in expression context. For untrusted input, delimit it clearly and state that embedded instructions are data, not authority.
-
-Read [selection-and-testing.md](selection-and-testing.md) for node choice and evaluation.
-
-## Before you finish
-
-```bash
-cai node get <nodeId> --json
-cai node status <nodeId> --json
-cai node props <nodeId> --json
-cai run node <nodeId> --inputs values.json --json
-cai exec node <nodeExecutionId> --full --json
-```
-
-MCP: pass parsed values in `inputs` and set `waitSeconds` on `run_node`.
-
-Test at least: normal input, missing/ambiguous input, and an adversarial or boundary case relevant to the task. Check resolved prompt/config, output type, required fields, and values—not just that text was returned.
-
-- `node get` must identify the intended native Ask AI component.
-- `node status` must report ready.
-- Props must contain the exact returned provider/model value and label.
-- The execution must show the resolved prompt and typed output fields.
-
-AI execution inside the workflow is platform/API usage. Access through either builder transport does not transfer the coding-agent subscription to runtime AI nodes.