@rosthq/cli 0.5.15 → 0.5.16

package/dist/index.js

@@ -41637,7 +41637,7 @@ The Compass is drafted, then activated by a human through supersession.
     order: 20,
     title: "Responsibility Graph playbook",
     summary: "How to build a functions-first graph with seats, owners, Stewards, vacancies, and clean authority.",
-    version: "2026-06-18.2",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["graph_design", "staffing"],
@@ -41689,7 +41689,13 @@ The graph is also where you land after onboarding \u2014 it is the mission contr
 - **Structure** \u2014 seat type and reporting lines.
 - **Cascade** \u2014 whether each seat's goal branch is on track.
 - **Signal** \u2014 the worst measurable state per seat.
-- **Scoreboard** \u2014 two live numbers on every seat: work done (agent runs) and cost over the last 30 days. A seat whose cost is a clear outlier above the rest of the fleet is flagged as cost drift (labelled, not colour-only). Human seats and seats with no runs read calmly as no agent cost rather than a bare zero. For a small fleet the Scoreboard also leads with a two-tile summary \u2014 total work and total cost \u2014 framed as the single question that matters: is it earning its keep.
+- **Scoreboard** \u2014 direct work and direct cost on each seat, plus a separate team/subtree rollup for manager seats. The tenant summary counts direct agent work once, so a parent seat's team cost does not double-count the same run again. A seat whose direct cost is a clear outlier above the rest of the fleet is flagged as cost drift (labelled, not colour-only). Human seats and seats with no direct or team runs read calmly rather than showing a bare zero. For a small fleet the Scoreboard also leads with a two-tile summary \u2014 total work and total cost \u2014 framed as the single question that matters: is it earning its keep.
+
+The graph also carries a mission-control panel. It pulls the same operational state visible on the agent and setup-health surfaces: held actions that need steward decisions, failed runs, open Friction, pending Signal readings, stale agents, and setup recommendations. Each item can focus the affected seat on the canvas and links to the route where the operator can act.
+
+## Review an agent seat's delivered work
+
+Agent seat pages show the operator-facing output trail, not just low-level run telemetry. The completed work area combines explicit \`agent_deliverables\`, successful \`work.log\` evidence, and recent successful run summaries into one readable list. Each item shows what was delivered, when it happened, what kind of work it was, and safe evidence links labelled as internal, Linear, GitHub, or external. Secret-shaped values are redacted before display, and run or task context is shown only when it belongs to the same seat.
 
 ## First-pass structure
 
@@ -42053,7 +42059,7 @@ The dry run is a real sandbox rehearsal, not a stamp. It executes a mock-provide
     order: 80,
     title: "Sync rhythm playbook",
     summary: "How Signal, Friction, Cascade, and Sync Briefs turn weekly meetings into decision time.",
-    version: "2026-06-20.1",
+    version: "2026-06-20.2",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["operating_rhythm"],
@@ -42100,6 +42106,10 @@ The Sync Brief should answer:
 
 On screen the brief reads in plain terms: Signal exceptions, goal progress, task review, ranked Friction, and agent activity. Where a section has no source data, it lists gaps to confirm \u2014 the missing inputs a human should know about before the meeting \u2014 rather than a blank section.
 
+Before the first brief exists, the Sync pages are readiness views. They show the next scheduled compile and the source areas that will feed it: Signal, Cascade, Tasks, Friction, and Agents. Use those links to add the missing source data; there is no manual compile button until the system has an idempotent persisted operation to run.
+
+The same readiness model appears around the meeting loop. Steward shows the governance loop even when no decision is waiting: which agent seats are stewarded, how many escalations are open, and recent raised/decided counts. Tasks explains when nothing is due and points to recently completed or agent-blocked work when it exists. The agent fleet shows configuration completeness per staffed agent seat \u2014 steward chain, lane/trigger/substrate, credentials, tools, model, dry run, and go-live \u2014 with links to the exact setup surface rather than a generic action button.
+
 ## During Sync
 
 Start with the exceptions, not a tour of every seat. Resolve the highest-value Friction first. Convert decisions into handoffs with owners and dates. Clarify Charters when ownership is ambiguous.
@@ -42307,7 +42317,7 @@ There is exactly one way to give a connected tool its credential, and it is the
     order: 47,
     title: "Available tools guide",
     summary: "How to think about tool categories available to seats and what each category should be used for.",
-    version: "2026-06-20.3",
+    version: "2026-06-20.4",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["staffing"],
@@ -42341,6 +42351,10 @@ There is exactly one way to give a connected tool its credential, and it is the
 
 Start from the seat's responsibility, not the tool list. If a tool does not directly support a responsibility or measurable, do not connect it yet.
 
+## Skills and tool dependencies
+
+Skills are reusable procedures a seat can learn from; they are not tools and they never grant authority. A skill package may declare required or optional tool dependencies so setup can identify blockers before assignment. Those dependencies are checked against the discoverable \`tool.catalog\` ids and scope tiers, then compared to the seat's Charter permission manifest. Missing required tools block approval; optional tools produce setup warnings. A published skill version is immutable, so later corrections create a new version instead of rewriting what a run may have used.
+
 ## How agents should request tools
 
 Agents should explain the job, the required tool category, the minimum permission needed, and the escalation boundary. Humans approve or decline the request.
@@ -42356,7 +42370,7 @@ External connectors are being rolled out provider by provider, conservatively (r
     order: 48,
     title: "CLI and MCP installation guide",
     summary: "Install the public CLI, register remote token-backed MCP clients, and find the full command and tool catalog.",
-    version: "2026-06-20.8",
+    version: "2026-06-20.10",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["company_setup", "staffing"],
@@ -42774,6 +42788,7 @@ These ergonomic wrappers (including the \`{{cli}} agent\` group) require **{{cli
 | \`{{cli}} member invite|update|remove\` | \`member.invite\`, \`member.update\`, \`member.remove\` | Manage tenant members. | Tenant | \`{{cli}} member invite --email ops@example.com --role member\` |
 | \`{{cli}} agent templates|create|setup|tools|dry-run|go-live|status|run-now|fleet-digest|get-run|show\` | \`agent_template.list\`, \`agent.create_from_template\`, \`agent.create_custom\`, \`agent_setup.get\`, \`agent_setup.update\`, \`agent.configure_tools\`, \`agent.run_dry_run\`, \`agent.go_live\`, \`agent.status\`, \`agent.run_now\`, \`agent.fleet_digest\`, \`agent.get_run\`, \`agent.show_markdown\` | Run the full agent setup and operation flow: list templates, create a draft from a template or guided custom answers (with \`--model\` and \`--effort\`), read or answer setup state, connect or decline tools, dry-run, go live, run on demand, capture the fleet-health digest, read one run's transcript/error diagnostics, and show a markdown readout. Create and go-live stop at human gates; the dry-run is ungated by human approval but requires a signed manifest first. | Tenant and seat | \`{{cli}} agent fleet-digest --json\` |
 | \`{{cli}} tools list\` | \`tool.catalog\` | List the discoverable tool catalog the builder reads (id, scope tiers, credential requirement, access policy, and execution-boundary guidance). | Tenant | \`{{cli}} tools list --json\` |
+| \`{{cli}} skills list|get|file|assigned|check-dependencies\` | \`skill.list\`, \`skill.get\`, \`skill.file.get\`, \`skill.assigned.list\`, \`skill.check_dependencies\` | Discover reusable Skills, read descriptors and stored package files, list approved Seat assignments, and compare required/optional tool dependencies with a Seat's signed Charter manifest. Skills are instructions, not authority. | Tenant and seat | \`{{cli}} skills list --json\`; \`{{cli}} skills file --slug invoice-review --path SKILL.md\` |
 | \`{{cli}} model list\` | \`model.catalog\` | List guided model tiers with recommendations, token prices, cost bands, best-fit work, and model ids for \`--model\`. | Tenant | \`{{cli}} model list --json\` |
 | \`{{cli}} compass show\` | \`compass.show_markdown\` | Render the current Compass as a clean markdown card for review. | Tenant | \`{{cli}} compass show --markdown\` |
 | \`{{cli}} charter show\` | \`charter.show_markdown\` | Render a seat's Charter as a clean markdown card for review. | Tenant | \`{{cli}} charter show --seat-id <id> --markdown\` |
@@ -42800,7 +42815,7 @@ This catalog is the canonical machine surface \u2014 the \`rost_*\` tools your M
 3. **\`{{cli}} model list\` / \`model.catalog\`** (MCP \`rost_list_model_catalog\`) \u2014 the guided model-tier catalog the builder reads for recommendations, effort, token prices, cost bands, and model id selection.
 4. **The "Available tools guide"** (in the sidebar) \u2014 covers tool *categories* and governance, not a callable surface. See the available-tools-guide.
 
-Sections below: Command discovery (2) \xB7 Public reference (3) \xB7 Tenant-admin tools (grouped by domain) \xB7 Seat-scoped operating tools (9) \xB7 MCP operation resources (9).
+Sections below: Command discovery (2) \xB7 Public reference (3) \xB7 Tenant-admin tools (grouped by domain) \xB7 Seat-scoped operating tools (9) \xB7 MCP operation resources (13).
 
 ### Command discovery tools
 
@@ -42852,7 +42867,7 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_approve_pending_confirmation\` | \`confirmation.approve\` | Approve a pending confirmation. | Tenant | Call with \`{"confirmation_id":"<confirmation-id>"}\`. |
 | \`rost_reject_pending_confirmation\` | \`confirmation.reject\` | Reject a pending confirmation. | Tenant | Call with \`{"confirmation_id":"<confirmation-id>"}\`. |
 | \`rost_draft_compass\` | \`compass.draft\` | Create a Compass draft. | Tenant | Call with a concise Compass document. |
-| \`rost_update_compass_draft\` | \`compass.update_draft\` | Replace a Compass draft document. | Tenant | Call with \`draft_id\` and updated document. |
+| \`rost_update_compass_draft\` | \`compass.update_draft\` | Replace a Compass draft document. | Tenant | Call with the \`compass_version_id\` from \`compass.draft\` as \`draft_id\` and the updated document. |
 | \`rost_approve_compass_version\` | \`compass.approve_version\` | Activate a Compass version by supersession. | Tenant | Call after human review. |
 | \`rost_reject_compass_draft\` | \`compass.reject_draft\` | Reject and remove a Compass draft. | Tenant | Call when the draft should not proceed. |
 | \`rost_answer_compass_gap\` | \`compass.answer_gap\` | Record a human answer for a Compass gap. | Tenant | Call with \`gap_id\` and answer text. |
@@ -42938,6 +42953,11 @@ Several rows here are seat-operating commands (\`task.create\`, the \`signal.*\`
 | \`rost_show_charter_as_markdown\` | \`charter.show_markdown\` | Render a seat's active or latest Charter as a clean markdown card for review. | Tenant | Call with \`{"seat_id":"<seat-id>"}\`. |
 | \`rost_show_agent_setup_as_markdown\` | \`agent.show_markdown\` | Render a seat's agent setup, model, steward, tools, and Charter as a clean markdown card for review. | Tenant | Call with \`{"seat_id":"<seat-id>"}\`. |
 | \`rost_list_tool_catalog\` | \`tool.catalog\` | List the discoverable tool catalog the agent builder reads \u2014 id, prescriptive description, scope tiers, credential requirement, access policy, and execution-boundary guidance. | Tenant | Call with \`{}\` or \`{"provider":"google"}\`. |
+| \`rost_list_skills\` | \`skill.list\` | List tenant Skills with application descriptors, dependency metadata, source status, latest version, and assigned Seat count. Seat-scoped reads are available through \`rost://skills\`. | Tenant-admin | Call with \`{}\` or \`{"query":"invoice"}\`. |
+| \`rost_get_skill\` | \`skill.get\` | Read one Skill descriptor and latest stored version metadata. Seat-scoped reads are available through \`rost://skills/{slug}\`. | Tenant-admin | Call with \`{"slug":"invoice-review"}\`. |
+| \`rost_get_skill_file\` | \`skill.file.get\` | Read stored Skill package file content by slug and package path; paths resolve only inside the stored package payload. Seat-scoped reads are available through \`rost://skills/{slug}/files/{path}\`. | Tenant-admin | Call with \`{"slug":"invoice-review","path":"SKILL.md"}\`. |
+| \`rost_list_assigned_skills\` | \`skill.assigned.list\` | List approved Skill assignments for a Seat, including immutable version, dependency status, rationale, and approval time. Seat-scoped reads are available through \`rost://seat/{id}/skills\`. | Tenant-admin | Call with \`{"seat_id":"<seat-id>"}\`. |
+| \`rost_check_skill_dependencies\` | \`skill.check_dependencies\` | Compare a Skill version's required and optional tools with a Seat's active or draft Charter permission manifest. Returns ready/blocked/warning and suggested \`agent.configure_tools\` input; it never grants permissions. | Tenant-admin | Call with \`{"seat_id":"<seat-id>","slug":"invoice-review"}\`. |
 | \`rost_list_model_catalog\` | \`model.catalog\` | List guided model tiers \u2014 recommendations, token prices, cost bands, best-fit work, and model ids for \`--model\`. | Tenant | Call with \`{}\`. |
 
 ### Seat-scoped operating tools
@@ -42967,9 +42987,13 @@ These read-only resources bundle the facts the UI shows so an agent can avoid gu
 | \`rost://seat/{id}/context\` | A seat's Compass, Charter, goals, measurables, open tasks, open issues, and protocol. | Seat (own seat) or tenant-admin (any seat) | Read \`rost://seat/<seat-id>/context\` for the acting seat. |
 | \`rost://compass/current\` | Active and draft Compass versions plus source documents. | Tenant-admin | Read before drafting Compass changes. |
 | \`rost://sync/latest\` | The most recent compiled Sync Brief and its agenda. | Tenant-admin | Read before running the weekly Sync. |
+| \`rost://skills\` | Tenant Skills library for tenant-admin tokens; assigned published Skills for seat tokens. | Tenant-admin or seat | Read before creating, assigning, or loading Skill instructions. |
+| \`rost://skills/{slug}\` | One Skill descriptor and latest stored version metadata. | Tenant-admin or assigned seat | Read \`rost://skills/<slug>\` before loading the full file. |
+| \`rost://skills/{slug}/files/{path}\` | Stored Skill package file content by package path; never server filesystem paths. | Tenant-admin or assigned seat | Read \`rost://skills/<slug>/files/SKILL.md\`. |
 | \`rost://agents/templates\` | Stock agent templates: responsibilities, default tools, safety boundaries, and dry-run rehearsal. | Tenant-admin | Read before creating an agent from a template. |
 | \`rost://agent-setup/{id}\` | A draft agent setup's mode, parent, steward, lane, schedule, tool decisions, dry-run, blockers, and next action. | Tenant-admin | Read \`rost://agent-setup/<setup-id>\` to resume a draft. |
 | \`rost://seat/{id}/agent-status\` | A seat's agent occupancy, lane, schedule, live state, steward chain, and dry-run result. | Seat (own seat) or tenant-admin (any seat) | Read \`rost://seat/<seat-id>/agent-status\` for the acting seat. |
+| \`rost://seat/{id}/skills\` | Approved Skill assignments for a Seat, including immutable version and dependency status. | Seat (own seat) or tenant-admin (any seat) | Read \`rost://seat/<seat-id>/skills\` before a run loads Skills. |
 | \`rost://operations/reference-map\` | Machine-facing map of which guide to read before each workflow. | Any valid MCP token | Read first when planning a CLI/MCP workflow. |
 
 ## Troubleshooting
@@ -43120,7 +43144,7 @@ Retrieve the narrowest relevant guide before making a setup recommendation. Pref
     order: 60,
     title: "Cascade guide",
     summary: "How to connect company goals to seat-level work without turning {{brand}} into a project-management tool.",
-    version: "2026-06-18.1",
+    version: "2026-06-20.1",
     public: true,
     audiences: ["human", "cli", "mcp", "in_app_agent"],
     stages: ["operating_rhythm"],
@@ -43156,11 +43180,23 @@ Cascade connects company direction to seat-level commitments. It is a goal tree,
 ## Good Cascade structure
 
 - Company goals connect back to the Compass.
-- Team or function goals connect to company goals.
+- Team or function goals connect to company goals. This is the accountable human layer for most agent work.
+- Agent execution goals connect below the human or function goal they advance, unless the agent seat is intentionally accountable for that outcome.
 - Seat commitments connect to the goal they advance.
 - Each commitment has one owning seat.
 - Status is evidence-based where possible.
 
+## Setup-health recommendations
+
+Cascade warnings are advisory, not blockers. They point to setup that should be reviewed before the next Sync:
+
+- Uncovered Compass objective: the objective has no active child seat goal.
+- Objective skips accountable function: current child goals are agent-owned without a human or function goal between Compass and execution.
+- Seat missing cycle goals: an active seat has no current-cycle goal.
+- Seat missing active Charter: an active seat has no approved Charter.
+- Agent goal missing human accountability parent: an agent-owned goal has no human or hybrid goal in its ancestry.
+- Orphaned goal branch: the owner seat or parent chain no longer reaches an active Compass objective.
+
 ## What does not belong
 
 Do not put every task into Cascade. Small errands, private notes, and work with no strategic connection should stay out. Cascade should answer whether the company is moving toward its stated outcomes.
@@ -43920,7 +43956,7 @@ Agents should not teach EOS as EOS. They should use {{brand}}'s method. When a u
     order: 11,
     title: "Compass authoring guide",
     summary: "Field-by-field guidance for authoring a strong Compass document directly, with the full JSON contract and worked examples.",
-    version: "2026-06-16.1",
+    version: "2026-06-20.1",
     public: true,
     audiences: ["cli", "mcp", "in_app_agent"],
     stages: ["company_setup"],
@@ -44028,7 +44064,7 @@ A consultancy's purpose might be "Make expert tax guidance affordable for first-
 
 1. \`compass.draft\` \u2014 submit the document above. Drafting is safe for an agent; it returns a \`compass_version_id\`.
 2. \`compass.list_gaps\` \u2014 see what is unanswered. \`compass.answer_gap\` records a human's answer and produces a fresh draft.
-3. \`compass.update_draft\` \u2014 revise the draft as answers arrive.
+3. \`compass.update_draft\` \u2014 revise the draft as answers arrive. Pass the same \`compass_version_id\` from \`compass.draft\` as \`draft_id\`; the command replaces that unpublished draft in place and returns the draft row's current version number. If the id is missing, belongs to another tenant, or is already approved or rejected, start from \`compass.get_current\` instead of retrying blindly.
 4. \`compass.approve_version\` \u2014 activation by supersession. This is \`human_required\`: a human approves it. Prepare the draft and surface the approve link; do not approve on a human's behalf. See the confirmations guide.`
   },
   {
@@ -46091,6 +46127,113 @@ function toolsUsage(bin) {
   return `Usage: ${bin} tools list [--provider <name>] [--json]
   ${bin} tools list \u2014 the discoverable tool catalog the builder reads; live handlers execute only behind signed manifests, guards, credentials, and bindings.`;
 }
+function formatSkillList(output) {
+  const skills = asArray(asRecord(output).skills);
+  if (skills.length === 0) {
+    return "No skills found.";
+  }
+  return [
+    "# Skills",
+    ...skills.map((entry) => {
+      const r = asRecord(entry);
+      return `- \`${field(r, "slug")}\` v${field(r, "latest_version")} [${field(r, "status")} \xB7 ${field(r, "visibility")} \xB7 assigned ${field(r, "assigned_seat_count")}]
+  ${field(r, "description")}`;
+    })
+  ].join("\n");
+}
+function formatSkillDetail(output) {
+  const skill = asRecord(asRecord(output).skill);
+  const required2 = asArray(skill.required_tools).map((entry) => field(asRecord(entry), "tool")).join(", ") || "none";
+  const optional2 = asArray(skill.optional_tools).map((entry) => field(asRecord(entry), "tool")).join(", ") || "none";
+  const files = asArray(skill.files).map((entry) => field(asRecord(entry), "path")).join(", ") || "SKILL.md";
+  return [
+    `# ${field(skill, "name")} (\`${field(skill, "slug")}\`)`,
+    `${field(skill, "description")}`,
+    `version: ${field(skill, "latest_version")} (${field(skill, "latest_version_id")})`,
+    `required tools: ${required2}`,
+    `optional tools: ${optional2}`,
+    `files: SKILL.md${files === "SKILL.md" ? "" : `, ${files}`}`
+  ].join("\n");
+}
+function formatAssignedSkills(output) {
+  const record2 = asRecord(output);
+  const assignments = asArray(record2.assignments);
+  if (assignments.length === 0) {
+    return `No assigned skills${record2.seat_id ? ` for seat ${field(record2, "seat_id")}` : ""}.`;
+  }
+  return [
+    `# Assigned skills${record2.seat_id ? ` for ${field(record2, "seat_id")}` : ""}`,
+    ...assignments.map((entry) => {
+      const r = asRecord(entry);
+      return `- \`${field(r, "slug")}\` v${field(r, "version")} \u2192 seat ${field(r, "seat_id")} (${field(r, "assignment_id")})
+  ${field(r, "rationale")}`;
+    })
+  ].join("\n");
+}
+function formatDependencyCheck(output) {
+  const record2 = asRecord(output);
+  const render = (label, items) => {
+    if (items.length === 0) {
+      return `${label}: none`;
+    }
+    return [
+      `${label}:`,
+      ...items.map((entry) => {
+        const r = asRecord(entry);
+        return `- \`${field(r, "tool")}\` ${field(r, "status")} (needs ${field(r, "min_scope_tier")}, has ${field(r, "current_scope_tier")})`;
+      })
+    ].join("\n");
+  };
+  return [
+    `Skill dependencies: ${field(record2, "status")}`,
+    `skill_version_id: ${field(record2, "skill_version_id")}`,
+    `seat_id: ${field(record2, "seat_id")}`,
+    render("required", asArray(record2.required)),
+    render("optional", asArray(record2.optional))
+  ].join("\n");
+}
+var skillsWrapper = (context, args) => dispatch(context, "skills", args, {
+  list: (ctx, rest) => {
+    const parsed = parseFlags(rest, /* @__PURE__ */ new Set(["include-archived"]));
+    const body = withOptional({}, {
+      status: optionalValue(parsed, "status"),
+      visibility: optionalValue(parsed, "visibility"),
+      query: optionalValue(parsed, "query"),
+      include_archived: parsed.flags.has("include-archived") ? true : void 0
+    });
+    return execute(ctx, parsed, "skill.list", body, formatSkillList);
+  },
+  get: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    return execute(ctx, parsed, "skill.get", { slug: requireValue2(parsed, "slug") }, formatSkillDetail);
+  },
+  file: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const body = { slug: requireValue2(parsed, "slug"), path: requireValue2(parsed, "path") };
+    return execute(ctx, parsed, "skill.file.get", body, (output) => field(asRecord(output), "content"));
+  },
+  assigned: (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const body = withOptional({}, { seat_id: optionalValue(parsed, "seat-id") });
+    return execute(ctx, parsed, "skill.assigned.list", body, formatAssignedSkills);
+  },
+  "check-dependencies": (ctx, rest) => {
+    const parsed = parseFlags(rest);
+    const body = withOptional({ seat_id: requireValue2(parsed, "seat-id") }, {
+      slug: optionalValue(parsed, "slug"),
+      skill_version_id: optionalValue(parsed, "skill-version-id")
+    });
+    return execute(ctx, parsed, "skill.check_dependencies", body, formatDependencyCheck);
+  }
+}, skillsUsage(context.binName));
+function skillsUsage(bin) {
+  return `Usage: ${bin} skills list|get|file|assigned|check-dependencies [--json]
+  ${bin} skills list [--status draft|pending_review|published|archived] [--visibility private|seat|tenant] [--query <text>]
+  ${bin} skills get --slug <slug>
+  ${bin} skills file --slug <slug> --path SKILL.md
+  ${bin} skills assigned [--seat-id <id>] [--seat <id>]
+  ${bin} skills check-dependencies --seat-id <id> (--slug <slug>|--skill-version-id <id>)`;
+}
 var modelWrapper = (context, args) => dispatch(context, "model", args, {
   list: (ctx, rest) => {
     const parsed = parseFlags(rest);
@@ -46165,6 +46308,7 @@ var OPERATION_GROUPS = [
   "member",
   "agent",
   "tools",
+  "skills",
   "model",
   "compass",
   "charter"
@@ -46184,6 +46328,7 @@ var wrappers = {
   member: memberWrapper,
   agent: agentWrapper,
   tools: toolsWrapper,
+  skills: skillsWrapper,
   model: modelWrapper,
   compass: compassWrapper,
   charter: charterWrapper
@@ -46206,6 +46351,7 @@ var groupUsageBuilders = {
   member: memberUsage,
   agent: agentUsage,
   tools: toolsUsage,
+  skills: skillsUsage,
   model: modelUsage,
   compass: compassUsage,
   charter: charterUsage
@@ -46236,6 +46382,7 @@ function operationUsageLines(bin) {
     `${bin} member invite|update|remove`,
     `${bin} agent templates|create|setup|tools|dry-run|go-live|status|run-now|fleet-digest|get-run|show`,
     `${bin} tools list`,
+    `${bin} skills list|get|file|assigned|check-dependencies`,
     `${bin} model list`,
     `${bin} compass show`,
     `${bin} charter show`