@cleocode/skills 2026.9.19 → 2026.9.21

package/skills/manifest.json

@@ -1,14 +1,5 @@
 {
   "$schema": "https://cleo-dev.com/schemas/v1/skills-manifest.schema.json",
-  "_meta": {
-    "schemaVersion": "2.7.0",
-    "lastUpdated": "2026-05-19",
-    "totalSkills": 22,
-    "generatedFrom": "T260 — lifecycle pipeline rework: dedicated skills for ADR, IVT loop, consensus, release, artifact-publish, provenance. T9664/T9665/T9672 (epic T9568) — adds loomStage + adrRefs fields on every LOOM-stage skill entry (underscored canonical form matching `cleo lifecycle` stage names; ADR refs point at .cleo/adrs/). T9672 reconciled dispatch_matrix.by_protocol key 'architecture-decision' → 'architecture_decision' matching the lifecycle CLI source of truth; the dashed form is retained as a keyword alias.",
-    "architectureNote": "Universal Subagent Architecture: All spawns use provider-neutral delegation with skill/protocol injection. Pipeline stages and cross-cutting protocols each have a dedicated skill — no overloading.",
-    "loomStageContract": "Each of the 10 LOOM lifecycle stages (research, consensus, architecture_decision, specification, decomposition, implementation, validation, testing, release, contribution) MUST have a bound skill whose manifest entry declares loomStage matching the lifecycle CLI stage name. The legacy `protocol` field is retained as an alias; dispatch_matrix.by_protocol is the authoritative routing table. See docs/skills/loom-coverage-matrix.md.",
-    "adrRefsContract": "Each LOOM-stage skill MUST declare an adrRefs[] array naming the ADR file(s) that govern the stage. Every referenced ADR-NNN MUST resolve to a file under .cleo/adrs/. The Vitest gate at packages/skills/skills/_shared/__tests__/loom-adr-links.test.ts enforces both conditions."
-  },
   "dispatch_matrix": {
     "_comment": "Maps task types/keywords to skill NAMES. Provider adapter decides HOW to execute.",
     "by_task_type": {
@@ -56,27 +47,82 @@
       "agent-protocol": "ct-orchestrator"
     }
   },
+  "_meta": {
+    "schemaVersion": "2.7.0",
+    "lastUpdated": "2026-05-19",
+    "totalSkills": 29,
+    "generatedFrom": "T260 — lifecycle pipeline rework: dedicated skills for ADR, IVT loop, consensus, release, artifact-publish, provenance. T9664/T9665/T9672 (epic T9568) — adds loomStage + adrRefs fields on every LOOM-stage skill entry (underscored canonical form matching `cleo lifecycle` stage names; ADR refs point at .cleo/adrs/). T9672 reconciled dispatch_matrix.by_protocol key 'architecture-decision' → 'architecture_decision' matching the lifecycle CLI source of truth; the dashed form is retained as a keyword alias.",
+    "architectureNote": "Universal Subagent Architecture: All spawns use provider-neutral delegation with skill/protocol injection. Pipeline stages and cross-cutting protocols each have a dedicated skill — no overloading.",
+    "loomStageContract": "Each of the 10 LOOM lifecycle stages (research, consensus, architecture_decision, specification, decomposition, implementation, validation, testing, release, contribution) MUST have a bound skill whose manifest entry declares loomStage matching the lifecycle CLI stage name. The legacy `protocol` field is retained as an alias; dispatch_matrix.by_protocol is the authoritative routing table. See docs/skills/loom-coverage-matrix.md.",
+    "adrRefsContract": "Each LOOM-stage skill MUST declare an adrRefs[] array naming the ADR file(s) that govern the stage. Every referenced ADR-NNN MUST resolve to a file under .cleo/adrs/. The Vitest gate at packages/skills/skills/_shared/__tests__/loom-adr-links.test.ts enforces both conditions.",
+    "generator": "scripts/skills/generate-manifest.mjs — derived from SKILL.md frontmatter; do not hand-edit identity fields (T12648)"
+  },
   "skills": [
     {
-      "name": "ct-cleo",
-      "version": "2.0.0",
-      "description": "CLEO task management protocol — core guidance for session, task, and workflow operations.",
-      "path": "skills/ct-cleo",
-      "tags": ["cleo", "protocol", "cli", "session", "task-management"],
+      "name": "ct-adr-recorder",
+      "version": "1.0.0",
+      "description": "Records Architecture Decision Records from accepted consensus verdicts. Use when promoting a consensus outcome to a formal ADR: drafts the document in the proposed-then-accepted HITL lifecycle, links to the originating consensus manifest, persists the decision to the canonical SQLite decisions table, and triggers downstream invalidation when an accepted ADR is later superseded. Triggers on phrases like 'write ADR', 'record architecture decision', 'formalize this decision', 'lock in the choice', 'create ADR-XXX', or when a consensus task reaches completed status and needs formalization.",
+      "path": "skills/ct-adr-recorder",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 0,
-      "token_budget": 6000,
-      "references": ["skills/ct-cleo/references/session-protocol.md", "skills/ct-cleo/references/loom-lifecycle.md", "skills/ct-cleo/references/anti-patterns.md"],
+      "loomStage": "architecture_decision",
+      "tags": [
+        "adr",
+        "architecture-decision",
+        "hitl",
+        "decision-record"
+      ],
+      "token_budget": 8000,
+      "protocol": "architecture_decision",
+      "adrRefs": [
+        "ADR-053",
+        "ADR-070"
+      ],
+      "references": [
+        "skills/ct-adr-recorder/references/cascade.md",
+        "skills/ct-adr-recorder/references/examples.md"
+      ],
       "capabilities": {
-        "inputs": ["TASK_ID", "SESSION_ID"],
-        "outputs": ["session-state", "task-state"],
+        "inputs": [
+          "consensus-manifest-id",
+          "task-id",
+          "decision-context"
+        ],
+        "outputs": [
+          "adr-markdown",
+          "decisions-table-row",
+          "manifest-entry"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["cleo", "session", "task", "start"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": [],
+        "dispatch_triggers": [
+          "write ADR",
+          "record architecture decision",
+          "formalize this decision",
+          "create ADR",
+          "lock in the choice"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-consensus-voter",
+          "ct-spec-writer"
+        ],
         "dispatch_keywords": {
-          "primary": ["cleo", "session", "task", "protocol"],
-          "secondary": ["start", "end", "status", "discovery"]
+          "primary": [
+            "adr",
+            "decision",
+            "architecture",
+            "formalize"
+          ],
+          "secondary": [
+            "proposed",
+            "accepted",
+            "superseded",
+            "hitl"
+          ]
         }
       },
       "constraints": {
@@ -86,229 +132,410 @@
       }
     },
     {
-      "name": "ct-orchestrator",
-      "version": "4.0.0",
-      "description": "Pipeline-aware orchestration for multi-agent workflows. Manages RCASD-IVTR+C pipeline progression, provider-neutral subagent delegation, and manifest-mediated handoffs.",
-      "path": "skills/ct-orchestrator",
-      "tags": ["workflow", "multi-agent", "coordination", "pipeline"],
+      "name": "ct-artifact-publisher",
+      "version": "1.0.0",
+      "description": "Builds and publishes artifacts to registries (npm, PyPI, cargo, docker, GitHub releases, generic tarballs) following the validate, then dry-run, then build, then publish, then record-provenance pipeline. Invoked by ct-release-orchestrator as a sub-skill when a release has artifact config. Never stores credentials in output or manifest (ARTP-008), always dry-runs first (ARTP-002), halts and attempts rollback on failure (ARTP-009). Triggers when a release config has at least one enabled artifact handler.",
+      "path": "skills/ct-artifact-publisher",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 0,
+      "tags": [
+        "artifact",
+        "publish",
+        "registry",
+        "release",
+        "distribution"
+      ],
       "token_budget": 8000,
-      "references": ["skills/ct-orchestrator/references/autonomous-operation.md", "skills/ct-orchestrator/references/lifecycle-gates.md", "skills/ct-orchestrator/references/orchestrator-compliance.md", "skills/ct-orchestrator/references/orchestrator-handoffs.md", "skills/ct-orchestrator/references/orchestrator-patterns.md", "skills/ct-orchestrator/references/orchestrator-recovery.md", "skills/ct-orchestrator/references/orchestrator-spawning.md", "skills/ct-orchestrator/references/orchestrator-tokens.md", "skills/ct-orchestrator/references/SUBAGENT-PROTOCOL-BLOCK.md"],
+      "protocol": "artifact-publish",
+      "references": [
+        "skills/ct-artifact-publisher/references/artifact-types.md",
+        "skills/ct-artifact-publisher/references/handler-interface.md"
+      ],
       "capabilities": {
-        "inputs": ["TASK_ID", "SESSION_ID", "EPIC_ID"],
-        "outputs": ["workflow-coordination", "subagent-spawns"],
+        "inputs": [
+          "release-config",
+          "version",
+          "commit-sha"
+        ],
+        "outputs": [
+          "built-artifacts",
+          "checksums",
+          "publish-results",
+          "manifest-entry"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["orchestrate", "orchestrator mode", "delegate to subagents", "coordinate agents", "spawn subagents", "multi-agent workflow"],
-        "compatible_subagent_types": ["orchestrator"],
-        "chains_to": ["ct-epic-architect", "ct-research-agent", "ct-task-executor", "ct-spec-writer", "ct-validator", "ct-documentor"],
+        "dispatch_triggers": [
+          "publish artifacts",
+          "build and publish",
+          "run artifact publish",
+          "ship packages",
+          "push to registry"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-provenance-keeper"
+        ],
         "dispatch_keywords": {
-          "primary": ["orchestrate", "coordinate", "delegate", "multi-agent"],
-          "secondary": ["spawn", "pipeline", "HITL", "workflow"]
+          "primary": [
+            "artifact",
+            "publish",
+            "registry",
+            "package"
+          ],
+          "secondary": [
+            "npm",
+            "docker",
+            "cargo",
+            "tarball"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 150000,
-        "requires_session": true,
-        "requires_epic": true
+        "max_context_tokens": 60000,
+        "requires_session": false,
+        "requires_epic": false
       }
     },
     {
-      "name": "ct-task-executor",
-      "version": "2.0.0",
-      "description": "General implementation task execution for completing assigned CLEO tasks.",
-      "path": "skills/ct-task-executor",
-      "tags": ["execution", "implementation", "task-management"],
-      "status": "active",
+      "name": "ct-cleo",
+      "version": "2.21.0",
+      "description": "CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.",
+      "path": "skills/ct-cleo",
       "tier": 0,
-      "token_budget": 8000,
-      "protocol": "implementation",
-      "loomStage": "implementation",
-      "adrRefs": ["ADR-070", "ADR-062"],
+      "deliveryTier": "core",
+      "install": "harness",
+      "status": "active",
+      "tags": [
+        "cleo",
+        "protocol",
+        "cli",
+        "session",
+        "task-management"
+      ],
+      "token_budget": 6000,
       "references": [
-        "skills/ct-task-executor/references/implementation-patterns.md",
-        "skills/ct-task-executor/references/acceptance-criteria-mapping.md",
-        "skills/ct-task-executor/references/evidence-and-gates.md",
-        "skills/ct-task-executor/references/common-failures.md",
-        "skills/ct-task-executor/references/anti-patterns.md"
+        "skills/ct-cleo/references/session-protocol.md",
+        "skills/ct-cleo/references/loom-lifecycle.md",
+        "skills/ct-cleo/references/anti-patterns.md"
       ],
       "capabilities": {
-        "inputs": ["TASK_ID", "TASK_NAME", "TASK_INSTRUCTIONS", "DELIVERABLES_LIST", "ACCEPTANCE_CRITERIA"],
-        "outputs": ["deliverables", "manifest-entry"],
+        "inputs": [
+          "TASK_ID",
+          "SESSION_ID"
+        ],
+        "outputs": [
+          "session-state",
+          "task-state"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["execute task", "implement", "complete this task", "build component"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-documentor"],
+        "dispatch_triggers": [
+          "cleo",
+          "session",
+          "task",
+          "start"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["implement", "build", "execute", "create"],
-          "secondary": ["complete", "finish", "work on", "carry out"]
+          "primary": [
+            "cleo",
+            "session",
+            "task",
+            "protocol"
+          ],
+          "secondary": [
+            "start",
+            "end",
+            "status",
+            "discovery"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 80000,
-        "requires_session": true,
+        "max_context_tokens": 60000,
+        "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-epic-architect",
-      "version": "3.0.0",
-      "description": "Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks.",
-      "path": "skills/ct-epic-architect",
-      "tags": ["planning", "architecture", "task-management"],
-      "status": "active",
+      "name": "ct-codebase-mapper",
+      "version": "1.0.0",
+      "description": "Codebase analysis and mapping for autonomous agent understanding. Builds structured maps of project stack, architecture, conventions, testing, integrations, and concerns.",
+      "path": "skills/ct-codebase-mapper",
       "tier": 1,
-      "token_budget": 8000,
-      "protocol": "decomposition",
-      "loomStage": "decomposition",
-      "adrRefs": ["ADR-066", "ADR-073"],
-      "references": ["skills/ct-epic-architect/references/bug-epic-example.md", "skills/ct-epic-architect/references/commands.md", "skills/ct-epic-architect/references/feature-epic-example.md"],
-      "capabilities": {
-        "inputs": ["TASK_ID", "FEATURE_NAME", "EPIC_ID", "SESSION_ID"],
-        "outputs": ["epic", "tasks", "manifest-entry"],
-        "dependencies": [],
-        "dispatch_triggers": ["create epic", "plan epic", "decompose into tasks", "task breakdown"],
-        "compatible_subagent_types": ["general-purpose", "planning"],
-        "chains_to": ["ct-task-executor", "ct-research-agent", "ct-spec-writer"],
-        "dispatch_keywords": {
-          "primary": ["epic", "plan", "decompose", "architect"],
-          "secondary": ["breakdown", "wave", "sprint", "dependency"]
-        }
-      },
-      "constraints": {
-        "max_context_tokens": 100000,
-        "requires_session": true,
-        "requires_epic": false
-      }
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "active"
     },
     {
-      "name": "ct-research-agent",
-      "version": "2.0.0",
-      "description": "Multi-source research and investigation combining web search, documentation lookup, and codebase analysis.",
-      "path": "skills/ct-research-agent",
-      "tags": ["research", "investigation", "discovery"],
-      "status": "active",
+      "name": "ct-consensus-voter",
+      "version": "1.0.0",
+      "description": "Runs structured multi-agent voting for decision tasks with confidence scores, conflict detection, and HITL escalation when the threshold is not met. Use when two or more agents must vote on options: architecture choices, tool selection, policy decisions, when a task carries agent_type:analysis, or on phrases like 'reach consensus', 'vote on options', 'resolve the debate', 'pick the best approach'. Produces a voting matrix JSON, enforces the 0.5 threshold, flags ties within 0.1 confidence as contested and escalates to human tiebreak.",
+      "path": "skills/ct-consensus-voter",
       "tier": 1,
-      "token_budget": 8000,
-      "protocol": "research",
-      "loomStage": "research",
-      "adrRefs": ["ADR-023", "ADR-070"],
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "active",
+      "loomStage": "consensus",
+      "tags": [
+        "consensus",
+        "voting",
+        "decision",
+        "multi-agent",
+        "hitl"
+      ],
+      "token_budget": 6000,
+      "protocol": "consensus",
+      "adrRefs": [
+        "ADR-015",
+        "ADR-023"
+      ],
       "references": [
-        "skills/ct-research-agent/references/triggers-and-routing.md",
-        "skills/ct-research-agent/references/source-strategy.md",
-        "skills/ct-research-agent/references/citation-and-evidence.md",
-        "skills/ct-research-agent/references/anti-patterns.md"
+        "skills/ct-consensus-voter/references/matrix-examples.md"
       ],
       "capabilities": {
-        "inputs": ["TASK_ID", "TOPIC", "RESEARCH_QUESTIONS"],
-        "outputs": ["research-file", "manifest-entry"],
+        "inputs": [
+          "task-id",
+          "question",
+          "candidate-options"
+        ],
+        "outputs": [
+          "voting-matrix",
+          "manifest-entry"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["research", "investigate", "gather information", "explore options"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-spec-writer", "ct-epic-architect"],
+        "dispatch_triggers": [
+          "reach consensus",
+          "vote on options",
+          "resolve the debate",
+          "pick the best approach",
+          "run consensus"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-adr-recorder",
+          "ct-research-agent"
+        ],
         "dispatch_keywords": {
-          "primary": ["research", "investigate", "explore", "discover"],
-          "secondary": ["gather", "survey", "analyze", "fact-finding"]
+          "primary": [
+            "consensus",
+            "vote",
+            "decide",
+            "verdict"
+          ],
+          "secondary": [
+            "confidence",
+            "rationale",
+            "evidence",
+            "contested"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 80000,
+        "max_context_tokens": 60000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-spec-writer",
-      "version": "2.0.0",
-      "description": "Technical specification writing using RFC 2119 language for clear, unambiguous requirements.",
-      "path": "skills/ct-spec-writer",
-      "tags": ["specification", "documentation", "rfc"],
-      "status": "active",
+      "name": "ct-contribution",
+      "version": "1.0.0",
+      "description": "Guided workflow for multi-agent consensus contributions. Use when user says \"/contribution\", \"contribution protocol\", \"submit contribution\", \"consensus workflow\", \"multi-agent decision\", \"create contribution\", \"contribution start\", \"contribution submit\", \"detect conflicts\", \"weighted consensus\", \"decision tracking\", \"conflict resolution\".",
+      "path": "skills/ct-contribution",
       "tier": 1,
-      "token_budget": 8000,
-      "protocol": "specification",
-      "loomStage": "specification",
-      "adrRefs": ["ADR-014", "ADR-023"],
-      "references": [
-        "skills/ct-spec-writer/references/rfc2119-language.md",
-        "skills/ct-spec-writer/references/spec-templates.md",
-        "skills/ct-spec-writer/references/traceability-matrix.md",
-        "skills/ct-spec-writer/references/anti-patterns.md"
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "active",
+      "loomStage": "contribution",
+      "tags": [
+        "contribution",
+        "consensus",
+        "workflow"
+      ],
+      "token_budget": 6000,
+      "protocol": "contribution",
+      "adrRefs": [
+        "ADR-015",
+        "ADR-053"
       ],
+      "references": [],
       "capabilities": {
-        "inputs": ["TASK_ID", "SPEC_NAME", "spec_topic"],
-        "outputs": ["specification-file", "manifest-entry"],
+        "inputs": [
+          "TASK_ID",
+          "contribution_type",
+          "context"
+        ],
+        "outputs": [
+          "contribution-record",
+          "consensus-report"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["write a spec", "create specification", "define protocol"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-task-executor", "ct-documentor"],
+        "dispatch_triggers": [
+          "contribution",
+          "submit contribution",
+          "consensus workflow"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["spec", "rfc", "protocol", "contract"],
-          "secondary": ["specification", "requirements", "interface", "architecture"]
+          "primary": [
+            "contribution",
+            "consensus",
+            "submit",
+            "decision"
+          ],
+          "secondary": [
+            "conflict",
+            "weighted",
+            "tracking",
+            "resolution"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 80000,
+        "max_context_tokens": 60000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-validator",
-      "version": "2.0.0",
-      "description": "Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards.",
-      "path": "skills/ct-validator",
-      "tags": ["validation", "compliance", "audit"],
-      "status": "active",
+      "name": "ct-council",
+      "version": "1.0.0",
+      "description": "Convene \"The Council\" — a 5-advisor, shuffled gate-based peer-review, chairman-synthesis workflow for reviewing a plan, decision, architecture, or piece of work inside the current project. Use when the user says \"convene the council\" (or \"counsel\"), \"get the council on this\", \"council review\", \"run the five advisors\", \"stress-test this\", \"get multiple perspectives\", or asks for a rigorous multi-angle challenge of a proposal (Contrarian, First Principles, Expansionist, Outsider, Executor → shuffled peer review with pass/fail gates → convergence detector → Chairman verdict). Operates on the current codebase — each advisor grounds their analysis in actual files/commits before opining. Output is validated by scripts/validate.py.",
+      "path": "skills/ct-council",
       "tier": 1,
-      "token_budget": 6000,
-      "protocol": "validation",
-      "loomStage": "validation",
-      "adrRefs": ["ADR-051", "ADR-023"],
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "active",
+      "tags": [
+        "council",
+        "review",
+        "peer-review",
+        "multi-perspective",
+        "stress-test"
+      ],
+      "token_budget": 8000,
       "references": [
-        "skills/ct-validator/references/validation-modes.md",
-        "skills/ct-validator/references/schema-checking.md",
-        "skills/ct-validator/references/compliance-reports.md",
-        "skills/ct-validator/references/anti-patterns.md"
+        "skills/ct-council/references/chairman.md",
+        "skills/ct-council/references/contrarian.md",
+        "skills/ct-council/references/evidence-pack.md",
+        "skills/ct-council/references/examples.md",
+        "skills/ct-council/references/executor.md",
+        "skills/ct-council/references/expansionist.md",
+        "skills/ct-council/references/first-principles.md",
+        "skills/ct-council/references/outsider.md",
+        "skills/ct-council/references/peer-review.md"
       ],
       "capabilities": {
-        "inputs": ["TASK_ID", "VALIDATION_TARGET", "VALIDATION_CRITERIA"],
-        "outputs": ["validation-report", "manifest-entry"],
+        "inputs": [
+          "proposal",
+          "plan",
+          "architecture-decision",
+          "task-id"
+        ],
+        "outputs": [
+          "council-verdict",
+          "advisor-reports",
+          "convergence-report"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["validate", "verify", "check compliance", "audit"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-ivt-looper"],
+        "dispatch_triggers": [
+          "convene the council",
+          "council review",
+          "run the five advisors",
+          "stress-test this",
+          "get multiple perspectives"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["validate", "verify", "audit", "compliance"],
-          "secondary": ["check", "conformance", "standards", "requirements"]
+          "primary": [
+            "council",
+            "advisors",
+            "stress-test",
+            "peer-review"
+          ],
+          "secondary": [
+            "contrarian",
+            "first-principles",
+            "expansionist",
+            "outsider",
+            "executor",
+            "chairman"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
+        "max_context_tokens": 80000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
       "name": "ct-dev-workflow",
-      "version": "3.0.0",
-      "description": "Development workflow orchestration for task-driven development with atomic commits and release processes.",
+      "version": "3.1.0",
+      "description": "Development workflow orchestration for task-driven development with atomic commits, conventional commit messages, and systematic release processes. Enforces task traceability, branch discipline, smart test scope selection, and GitHub Actions integration. Use when committing code, creating releases, managing branches, or following contribution protocols. Triggers on commit operations, release preparation, or workflow compliance needs.",
       "path": "skills/ct-dev-workflow",
-      "tags": ["workflow", "git", "commits", "release", "testing"],
+      "tier": 0,
+      "deliveryTier": "core",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
+      "tags": [
+        "workflow",
+        "git",
+        "commits",
+        "release",
+        "testing"
+      ],
       "token_budget": 6000,
       "references": [],
       "capabilities": {
-        "inputs": ["TASK_ID", "CHANGE_TYPE", "SCOPE"],
-        "outputs": ["commit", "tag", "push"],
+        "inputs": [
+          "TASK_ID",
+          "CHANGE_TYPE",
+          "SCOPE"
+        ],
+        "outputs": [
+          "commit",
+          "tag",
+          "push"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["commit", "release", "run the workflow", "test"],
-        "compatible_subagent_types": ["general-purpose"],
+        "dispatch_triggers": [
+          "commit",
+          "release",
+          "run the workflow",
+          "test"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
         "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["commit", "release", "push", "test"],
-          "secondary": ["atomic", "conventional", "ship", "vitest"]
+          "primary": [
+            "commit",
+            "release",
+            "push",
+            "test"
+          ],
+          "secondary": [
+            "atomic",
+            "conventional",
+            "ship",
+            "vitest"
+          ]
         }
       },
       "constraints": {
@@ -318,62 +545,117 @@
       }
     },
     {
-      "name": "ct-documentor",
-      "version": "3.0.0",
-      "description": "Documentation coordination — chains lookup, writing, and review skills.",
-      "path": "skills/ct-documentor",
-      "tags": ["documentation", "orchestration", "workflow"],
-      "status": "active",
-      "tier": 2,
-      "token_budget": 8000,
+      "name": "ct-docs-lookup",
+      "version": "1.0.0",
+      "description": "This skill should be used when the user asks \"how do I configure [library]\", \"write code using [framework]\", \"what are the [library] methods\", \"show me [framework] examples\", or mentions libraries like React, Vue, Next.js, Prisma, Supabase, Express, Tailwind, Drizzle, Svelte. Triggers for library setup, configuration, API references, framework code examples, or version-specific docs (\"React 19\", \"Next.js 15\").",
+      "path": "skills/ct-docs-lookup",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "deprecated",
+      "tags": [
+        "documentation",
+        "libraries",
+        "context7"
+      ],
+      "token_budget": 6000,
       "references": [
-        "skills/ct-documentor/references/chain-orchestration.md",
-        "skills/ct-documentor/references/doc-types-and-templates.md",
-        "skills/ct-documentor/references/style-coordination.md",
-        "skills/ct-documentor/references/anti-patterns.md"
+        "skills/ct-docs-lookup/references/ctx7-workflow.md",
+        "skills/ct-docs-lookup/references/library-id-resolution.md",
+        "skills/ct-docs-lookup/references/version-specific-docs.md"
       ],
       "capabilities": {
-        "inputs": ["TASK_ID", "documentation_topic"],
-        "outputs": ["documentation-file", "manifest-entry", "review-report"],
-        "dependencies": ["ct-docs-lookup", "ct-docs-write", "ct-docs-review"],
-        "dispatch_triggers": ["write documentation", "create docs", "review docs"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-docs-lookup", "ct-docs-write", "ct-docs-review"],
+        "inputs": [
+          "library_name",
+          "query",
+          "version"
+        ],
+        "outputs": [
+          "documentation-content",
+          "code-examples"
+        ],
+        "dependencies": [],
+        "dispatch_triggers": [
+          "how do I configure",
+          "write code using",
+          "show me examples"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["doc", "document", "readme", "guide"],
-          "secondary": ["documentation", "docs", "markdown", "mdx"]
+          "primary": [
+            "library",
+            "framework",
+            "api",
+            "reference"
+          ],
+          "secondary": [
+            "configure",
+            "methods",
+            "examples",
+            "docs"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 80000,
+        "max_context_tokens": 60000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-docs-lookup",
+      "name": "ct-docs-review",
       "version": "1.0.0",
-      "description": "Context7 library documentation lookup for framework and library references.",
-      "path": "skills/ct-docs-lookup",
-      "tags": ["documentation", "libraries", "context7"],
-      "status": "active",
-      "tier": 2,
+      "description": "This skill should be used when the user asks to \"review documentation\", \"check docs style\", \"review this markdown file\", \"check style guide compliance\", \"review PR documentation\", or needs documentation reviewed against the CLEO writing style guide. Supports both local file review and GitHub PR review modes with inline comments.",
+      "path": "skills/ct-docs-review",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "deprecated",
+      "tags": [
+        "documentation",
+        "review",
+        "style-guide"
+      ],
       "token_budget": 6000,
       "references": [
-        "skills/ct-docs-lookup/references/ctx7-workflow.md",
-        "skills/ct-docs-lookup/references/library-id-resolution.md",
-        "skills/ct-docs-lookup/references/version-specific-docs.md"
+        "skills/ct-docs-review/references/style-violations.md",
+        "skills/ct-docs-review/references/pr-review-mode.md",
+        "skills/ct-docs-review/references/inline-comment-patterns.md"
       ],
       "capabilities": {
-        "inputs": ["library_name", "query", "version"],
-        "outputs": ["documentation-content", "code-examples"],
+        "inputs": [
+          "file_path",
+          "pr_url",
+          "diff_content"
+        ],
+        "outputs": [
+          "review-comments",
+          "style-violations"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["how do I configure", "write code using", "show me examples"],
-        "compatible_subagent_types": ["general-purpose"],
+        "dispatch_triggers": [
+          "review documentation",
+          "check docs style"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
         "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["library", "framework", "api", "reference"],
-          "secondary": ["configure", "methods", "examples", "docs"]
+          "primary": [
+            "review",
+            "check",
+            "style",
+            "compliance"
+          ],
+          "secondary": [
+            "violations",
+            "improvements",
+            "pr review"
+          ]
         }
       },
       "constraints": {
@@ -384,12 +666,18 @@
     },
     {
       "name": "ct-docs-write",
-      "version": "1.0.0",
-      "description": "Documentation writing with CLEO style guide compliance.",
+      "version": "1.2.0",
+      "description": "This skill should be used when creating, editing, or reviewing documentation files (markdown, MDX, README, guides). Use when the user asks to \"write docs\", \"create documentation\", \"edit the README\", \"improve doc clarity\", \"make docs more readable\", \"follow the style guide\", or \"write user-facing content\". Applies CLEO's conversational, clear, and user-focused writing style.",
       "path": "skills/ct-docs-write",
-      "tags": ["documentation", "writing", "style-guide"],
-      "status": "active",
-      "tier": 2,
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "deprecated",
+      "tags": [
+        "documentation",
+        "writing",
+        "style-guide"
+      ],
       "token_budget": 6000,
       "references": [
         "skills/ct-docs-write/references/cleo-style-guide.md",
@@ -397,15 +685,38 @@
         "skills/ct-docs-write/references/audience-targeting.md"
       ],
       "capabilities": {
-        "inputs": ["file_path", "content_topic", "audience"],
-        "outputs": ["documentation-file", "markdown-content"],
+        "inputs": [
+          "file_path",
+          "content_topic",
+          "audience"
+        ],
+        "outputs": [
+          "documentation-file",
+          "markdown-content"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["write docs", "create documentation", "edit the README"],
-        "compatible_subagent_types": ["general-purpose"],
+        "dispatch_triggers": [
+          "write docs",
+          "create documentation",
+          "edit the README"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
         "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["write", "create", "edit", "style"],
-          "secondary": ["clarity", "readable", "user-facing", "content"]
+          "primary": [
+            "write",
+            "create",
+            "edit",
+            "style"
+          ],
+          "secondary": [
+            "clarity",
+            "readable",
+            "user-facing",
+            "content"
+          ]
         }
       },
       "constraints": {
@@ -415,88 +726,198 @@
       }
     },
     {
-      "name": "ct-docs-review",
-      "version": "1.0.0",
-      "description": "Documentation style guide review and compliance checking.",
-      "path": "skills/ct-docs-review",
-      "tags": ["documentation", "review", "style-guide"],
+      "name": "ct-documentor",
+      "version": "3.16.1",
+      "description": "Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Coordinates ct-docs-lookup, ct-docs-write, ct-docs-review, ct-spec-writer, and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.",
+      "path": "skills/ct-documentor",
+      "tier": 0,
+      "deliveryTier": "core",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
-      "token_budget": 6000,
+      "tags": [
+        "documentation",
+        "orchestration",
+        "workflow"
+      ],
+      "token_budget": 8000,
       "references": [
-        "skills/ct-docs-review/references/style-violations.md",
-        "skills/ct-docs-review/references/pr-review-mode.md",
-        "skills/ct-docs-review/references/inline-comment-patterns.md"
+        "skills/ct-documentor/references/chain-orchestration.md",
+        "skills/ct-documentor/references/doc-types-and-templates.md",
+        "skills/ct-documentor/references/style-coordination.md",
+        "skills/ct-documentor/references/anti-patterns.md"
       ],
       "capabilities": {
-        "inputs": ["file_path", "pr_url", "diff_content"],
-        "outputs": ["review-comments", "style-violations"],
-        "dependencies": [],
-        "dispatch_triggers": ["review documentation", "check docs style"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": [],
+        "inputs": [
+          "TASK_ID",
+          "documentation_topic"
+        ],
+        "outputs": [
+          "documentation-file",
+          "manifest-entry",
+          "review-report"
+        ],
+        "dependencies": [
+          "ct-docs-lookup",
+          "ct-docs-write",
+          "ct-docs-review"
+        ],
+        "dispatch_triggers": [
+          "write documentation",
+          "create docs",
+          "review docs"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-docs-lookup",
+          "ct-docs-write",
+          "ct-docs-review"
+        ],
         "dispatch_keywords": {
-          "primary": ["review", "check", "style", "compliance"],
-          "secondary": ["violations", "improvements", "pr review"]
+          "primary": [
+            "doc",
+            "document",
+            "readme",
+            "guide"
+          ],
+          "secondary": [
+            "documentation",
+            "docs",
+            "markdown",
+            "mdx"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
+        "max_context_tokens": 80000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-contribution",
-      "version": "1.0.0",
-      "description": "Multi-agent consensus contributions with conflict detection and decision tracking.",
-      "path": "skills/ct-contribution",
-      "tags": ["contribution", "consensus", "workflow"],
+      "name": "ct-epic-architect",
+      "version": "3.0.0",
+      "description": "Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. Provides dependency analysis, wave-based parallel execution planning, hierarchy management, and research linking. Use when creating epics, decomposing initiatives into task trees, planning parallel workflows, or analyzing task dependencies. Triggers on epic creation, task decomposition requests, or planning phase work.",
+      "path": "skills/ct-epic-architect",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
-      "token_budget": 6000,
-      "protocol": "contribution",
-      "loomStage": "contribution",
-      "adrRefs": ["ADR-015", "ADR-053"],
-      "references": [],
+      "loomStage": "decomposition",
+      "tags": [
+        "planning",
+        "architecture",
+        "task-management"
+      ],
+      "token_budget": 8000,
+      "protocol": "decomposition",
+      "adrRefs": [
+        "ADR-066",
+        "ADR-073"
+      ],
+      "references": [
+        "skills/ct-epic-architect/references/bug-epic-example.md",
+        "skills/ct-epic-architect/references/commands.md",
+        "skills/ct-epic-architect/references/feature-epic-example.md"
+      ],
       "capabilities": {
-        "inputs": ["TASK_ID", "contribution_type", "context"],
-        "outputs": ["contribution-record", "consensus-report"],
+        "inputs": [
+          "TASK_ID",
+          "FEATURE_NAME",
+          "EPIC_ID",
+          "SESSION_ID"
+        ],
+        "outputs": [
+          "epic",
+          "tasks",
+          "manifest-entry"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["contribution", "submit contribution", "consensus workflow"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": [],
+        "dispatch_triggers": [
+          "create epic",
+          "plan epic",
+          "decompose into tasks",
+          "task breakdown"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose",
+          "planning"
+        ],
+        "chains_to": [
+          "ct-task-executor",
+          "ct-research-agent",
+          "ct-spec-writer"
+        ],
         "dispatch_keywords": {
-          "primary": ["contribution", "consensus", "submit", "decision"],
-          "secondary": ["conflict", "weighted", "tracking", "resolution"]
+          "primary": [
+            "epic",
+            "plan",
+            "decompose",
+            "architect"
+          ],
+          "secondary": [
+            "breakdown",
+            "wave",
+            "sprint",
+            "dependency"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
-        "requires_session": false,
+        "max_context_tokens": 100000,
+        "requires_session": true,
         "requires_epic": false
       }
     },
     {
       "name": "ct-grade",
-      "version": "1.0.0",
-      "description": "Session grading for agent behavioral analysis and protocol compliance scoring.",
+      "version": "2.1.0",
+      "description": "CLEO session grading and A/B behavioral analysis with token tracking. Evaluates agent session quality via a 5-dimension rubric (S1 session discipline, S2 discovery efficiency, S3 task hygiene, S4 error protocol, S5 progressive disclosure). Supports three modes: (1) scenario — run playbook scenarios S1-S5 via CLI; (2) ab — blind A/B comparison of different CLI configurations for same domain operations with token cost measurement; (3) blind — spawn two agents with different configurations, blind-comparator picks winner, analyzer produces recommendation. Use when grading agent sessions, running grade playbook scenarios, comparing behavioral differences, measuring token usage across configurations, or performing multi-run blind A/B evaluation with statistical analysis and comparative report. Triggers on: grade session, evaluate agent behavior, A/B test CLEO configurations, run grade scenario, token usage analysis, behavioral rubric, protocol compliance scoring.",
       "path": "skills/ct-grade",
-      "tags": ["grading", "quality", "analysis"],
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
       "status": "active",
-      "tier": 2,
+      "tags": [
+        "grading",
+        "quality",
+        "analysis"
+      ],
       "token_budget": 6000,
       "references": [],
       "capabilities": {
-        "inputs": ["SESSION_ID", "grading_criteria"],
-        "outputs": ["grade-report", "diagnostic-flags"],
+        "inputs": [
+          "SESSION_ID",
+          "grading_criteria"
+        ],
+        "outputs": [
+          "grade-report",
+          "diagnostic-flags"
+        ],
         "dependencies": [],
-        "dispatch_triggers": ["grade session", "evaluate session", "session quality"],
-        "compatible_subagent_types": ["general-purpose"],
+        "dispatch_triggers": [
+          "grade session",
+          "evaluate session",
+          "session quality"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
         "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["grade", "evaluate", "score", "quality"],
-          "secondary": ["session", "behavioral", "rubric", "analysis"]
+          "primary": [
+            "grade",
+            "evaluate",
+            "score",
+            "quality"
+          ],
+          "secondary": [
+            "session",
+            "behavioral",
+            "rubric",
+            "analysis"
+          ]
         }
       },
       "constraints": {
@@ -506,143 +927,247 @@
       }
     },
     {
-      "name": "ct-skill-creator",
-      "version": "1.0.0",
-      "description": "Guide for creating effective skills with proper structure and progressive disclosure.",
-      "path": "skills/ct-skill-creator",
-      "tags": ["skills", "creation", "meta"],
-      "status": "active",
-      "tier": 3,
-      "token_budget": 8000,
-      "references": ["skills/ct-skill-creator/references/output-patterns.md", "skills/ct-skill-creator/references/workflows.md"],
-      "capabilities": {
-        "inputs": ["skill_name", "skill_purpose"],
-        "outputs": ["skill-directory", "SKILL.md"],
-        "dependencies": [],
-        "dispatch_triggers": ["create a new skill", "update an existing skill"],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": [],
-        "dispatch_keywords": {
-          "primary": ["skill", "create", "build", "extend"],
-          "secondary": ["capabilities", "workflow", "integration"]
-        }
-      },
-      "constraints": {
-        "max_context_tokens": 80000,
-        "requires_session": false,
-        "requires_epic": false
-      }
-    },
-    {
-      "name": "ct-adr-recorder",
+      "name": "ct-ivt-looper",
       "version": "1.0.0",
-      "description": "Records Architecture Decision Records from accepted consensus verdicts. Drafts the document in the proposed-then-accepted HITL lifecycle, links to the originating consensus manifest, persists to the canonical SQLite decisions table, and triggers downstream invalidation when an accepted ADR is later superseded.",
-      "path": "skills/ct-adr-recorder",
-      "tags": ["adr", "architecture-decision", "hitl", "decision-record"],
+      "description": "Runs a project-agnostic autonomous Implement-then-Validate-then-Test compliance loop on any git worktree. Detects the project's test framework (vitest, jest, mocha, pytest, unittest, go-test, cargo-test, rspec, phpunit, bats, or other) and iterates until the implementation satisfies its specification, recording convergence metrics to the manifest. Use when given an implementation task that must ship verified: the IVT loop is the autonomous compliance layer enforced before any release or PR. Triggers on phrases like 'implement and verify', 'run the IVT loop', 'ship this task', 'complete implementation with tests', 'verify against spec', or any implementation task with acceptance criteria. Works in any git worktree regardless of language or framework, never hardcoded to one project's tooling.",
+      "path": "skills/ct-ivt-looper",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
-      "token_budget": 8000,
-      "protocol": "architecture_decision",
-      "loomStage": "architecture_decision",
-      "adrRefs": ["ADR-053", "ADR-070"],
+      "loomStage": "testing",
+      "tags": [
+        "testing",
+        "ivt-loop",
+        "autonomous",
+        "framework-agnostic",
+        "compliance"
+      ],
+      "token_budget": 10000,
+      "protocol": "testing",
+      "adrRefs": [
+        "ADR-051",
+        "ADR-061"
+      ],
       "references": [
-        "skills/ct-adr-recorder/references/cascade.md",
-        "skills/ct-adr-recorder/references/examples.md"
+        "skills/ct-ivt-looper/references/escalation.md",
+        "skills/ct-ivt-looper/references/frameworks.md",
+        "skills/ct-ivt-looper/references/loop-anatomy.md"
       ],
       "capabilities": {
-        "inputs": ["consensus-manifest-id", "task-id", "decision-context"],
-        "outputs": ["adr-markdown", "decisions-table-row", "manifest-entry"],
+        "inputs": [
+          "task-id",
+          "spec-reference",
+          "worktree-path"
+        ],
+        "outputs": [
+          "manifest-entry",
+          "ivt-convergence-report"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "write ADR",
-          "record architecture decision",
-          "formalize this decision",
-          "create ADR",
-          "lock in the choice"
+          "run the IVT loop",
+          "implement and verify",
+          "ship this task",
+          "verify against spec",
+          "complete implementation with tests"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-validator",
+          "ct-release-orchestrator"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-consensus-voter", "ct-spec-writer"],
         "dispatch_keywords": {
-          "primary": ["adr", "decision", "architecture", "formalize"],
-          "secondary": ["proposed", "accepted", "superseded", "hitl"]
+          "primary": [
+            "ivt",
+            "implement",
+            "validate",
+            "test"
+          ],
+          "secondary": [
+            "converge",
+            "framework",
+            "spec",
+            "iterate"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
+        "max_context_tokens": 80000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-ivt-looper",
+      "name": "ct-lead",
       "version": "1.0.0",
-      "description": "Runs a project-agnostic autonomous Implement→Validate→Test compliance loop on any git worktree. Detects the project's test framework and iterates until the implementation satisfies its specification. Works in any git worktree regardless of language or framework — the autonomous compliance layer enforced before any release or PR.",
-      "path": "skills/ct-ivt-looper",
-      "tags": ["testing", "ivt-loop", "autonomous", "framework-agnostic", "compliance"],
+      "description": "Phase Lead orchestration playbook for spawning and supervising a parallel worker swarm in one wave. Use when spawned by ct-orchestrator with role=orchestrator to fan out N leaf workers via delegate_task, drain the epic-<TID>.wave-<n> conduit topic plus pipeline_manifest, await rollupWaveStatus convergence, and return ONE rolled-up contract string to the parent Orchestrator. Triggers: 'phase lead', 'wave lead', 'supervise wave', 'fan out workers', 'aggregate worker results', 'rollup wave', any task with role=orchestrator that is itself a child of another orchestrator. Implements ADR-070 hierarchical orchestration.",
+      "path": "skills/ct-lead",
+      "tier": 0,
+      "deliveryTier": "core",
+      "install": "harness",
+      "status": "active"
+    },
+    {
+      "name": "ct-master-tac",
+      "version": "1.0.0",
+      "description": "Master Tactical Bundle for CleoOS autonomous execution. Installs the complete primitive library needed to run the full agentic execution layer on a fresh CleoOS install: 12 CANT protocol files (research, consensus, architecture-decision, specification, decomposition, implementation, validation, testing, contribution, release, artifact-publish, provenance), the canonical platform team definition, and the skills manifest entry. Use when bootstrapping a new CleoOS project, verifying that all protocol primitives are present, or recovering a broken protocol tree. Triggers on: \"install master tac\", \"bootstrap protocols\", \"tools.skill.install ct-master-tac\", \"verify protocol bundle\", \"repair protocol files\", \"fresh CleoOS install\".",
+      "path": "skills/ct-master-tac",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated"
+    },
+    {
+      "name": "ct-memory",
+      "version": "1.0.0",
+      "description": "Brain memory protocol with progressive disclosure for anti-hallucination and context recall",
+      "path": "skills/ct-memory",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated"
+    },
+    {
+      "name": "ct-orchestrator",
+      "version": "4.0.0",
+      "description": "Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to \\\"orchestrate\\\", \\\"orchestrator mode\\\", \\\"run as orchestrator\\\", \\\"delegate to subagents\\\", \\\"coordinate agents\\\", \\\"spawn subagents\\\", \\\"multi-agent workflow\\\", \\\"context-protected workflow\\\", \\\"agent farm\\\", \\\"HITL orchestration\\\", \\\"pipeline management\\\", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.",
+      "path": "skills/ct-orchestrator",
+      "tier": 0,
+      "deliveryTier": "core",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
-      "token_budget": 10000,
-      "protocol": "testing",
-      "loomStage": "testing",
-      "adrRefs": ["ADR-051", "ADR-061"],
+      "tags": [
+        "workflow",
+        "multi-agent",
+        "coordination",
+        "pipeline"
+      ],
+      "token_budget": 8000,
       "references": [
-        "skills/ct-ivt-looper/references/escalation.md",
-        "skills/ct-ivt-looper/references/frameworks.md",
-        "skills/ct-ivt-looper/references/loop-anatomy.md"
+        "skills/ct-orchestrator/references/autonomous-operation.md",
+        "skills/ct-orchestrator/references/lifecycle-gates.md",
+        "skills/ct-orchestrator/references/orchestrator-compliance.md",
+        "skills/ct-orchestrator/references/orchestrator-handoffs.md",
+        "skills/ct-orchestrator/references/orchestrator-patterns.md",
+        "skills/ct-orchestrator/references/orchestrator-recovery.md",
+        "skills/ct-orchestrator/references/orchestrator-spawning.md",
+        "skills/ct-orchestrator/references/orchestrator-tokens.md",
+        "skills/ct-orchestrator/references/SUBAGENT-PROTOCOL-BLOCK.md"
       ],
       "capabilities": {
-        "inputs": ["task-id", "spec-reference", "worktree-path"],
-        "outputs": ["manifest-entry", "ivt-convergence-report"],
+        "inputs": [
+          "TASK_ID",
+          "SESSION_ID",
+          "EPIC_ID"
+        ],
+        "outputs": [
+          "workflow-coordination",
+          "subagent-spawns"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "run the IVT loop",
-          "implement and verify",
-          "ship this task",
-          "verify against spec",
-          "complete implementation with tests"
+          "orchestrate",
+          "orchestrator mode",
+          "delegate to subagents",
+          "coordinate agents",
+          "spawn subagents",
+          "multi-agent workflow"
+        ],
+        "compatible_subagent_types": [
+          "orchestrator"
+        ],
+        "chains_to": [
+          "ct-epic-architect",
+          "ct-research-agent",
+          "ct-task-executor",
+          "ct-spec-writer",
+          "ct-validator",
+          "ct-documentor"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-validator", "ct-release-orchestrator"],
         "dispatch_keywords": {
-          "primary": ["ivt", "implement", "validate", "test"],
-          "secondary": ["converge", "framework", "spec", "iterate"]
+          "primary": [
+            "orchestrate",
+            "coordinate",
+            "delegate",
+            "multi-agent"
+          ],
+          "secondary": [
+            "spawn",
+            "pipeline",
+            "HITL",
+            "workflow"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 80000,
-        "requires_session": false,
-        "requires_epic": false
+        "max_context_tokens": 150000,
+        "requires_session": true,
+        "requires_epic": true
       }
     },
     {
-      "name": "ct-consensus-voter",
+      "name": "ct-provenance-keeper",
       "version": "1.0.0",
-      "description": "Runs structured multi-agent voting for decision tasks with confidence scores, conflict detection, and HITL escalation when the threshold is not met. Produces a voting matrix JSON, enforces the 0.5 threshold, and flags ties within 0.1 confidence as contested for human tiebreak. Split from the overloaded ct-validator skill.",
-      "path": "skills/ct-consensus-voter",
-      "tags": ["consensus", "voting", "decision", "multi-agent", "hitl"],
+      "description": "Generates in-toto v1 attestations, SLSA-level provenance records, SBOMs (CycloneDX or SPDX), and sigstore/cosign signatures for published artifacts. Invoked by ct-artifact-publisher as a delegation for signing and attestation. Records the full commit, then build, then artifact, then attestation, then registry chain in .cleo/releases.json and rejects publishes whose digest does not match the attestation. Triggers when artifact-publish reaches the provenance step or when a release needs SLSA L2+ attestation.",
+      "path": "skills/ct-provenance-keeper",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
+      "tags": [
+        "provenance",
+        "slsa",
+        "attestation",
+        "sbom",
+        "sigstore",
+        "supply-chain"
+      ],
       "token_budget": 6000,
-      "protocol": "consensus",
-      "loomStage": "consensus",
-      "adrRefs": ["ADR-015", "ADR-023"],
-      "references": ["skills/ct-consensus-voter/references/matrix-examples.md"],
+      "protocol": "provenance",
+      "references": [
+        "skills/ct-provenance-keeper/references/signing.md",
+        "skills/ct-provenance-keeper/references/slsa.md"
+      ],
       "capabilities": {
-        "inputs": ["task-id", "question", "candidate-options"],
-        "outputs": ["voting-matrix", "manifest-entry"],
+        "inputs": [
+          "built-artifacts",
+          "commit-sha",
+          "builder-identity"
+        ],
+        "outputs": [
+          "in-toto-attestation",
+          "sbom",
+          "signature",
+          "releases-json-entry"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "reach consensus",
-          "vote on options",
-          "resolve the debate",
-          "pick the best approach",
-          "run consensus"
+          "generate provenance",
+          "sign artifacts",
+          "create attestation",
+          "record supply chain",
+          "run slsa attestation"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-adr-recorder", "ct-research-agent"],
+        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["consensus", "vote", "decide", "verdict"],
-          "secondary": ["confidence", "rationale", "evidence", "contested"]
+          "primary": [
+            "provenance",
+            "attestation",
+            "sbom",
+            "slsa"
+          ],
+          "secondary": [
+            "sigstore",
+            "cosign",
+            "in-toto",
+            "sign"
+          ]
         }
       },
       "constraints": {
@@ -653,23 +1178,44 @@
     },
     {
       "name": "ct-release-orchestrator",
-      "version": "1.0.0",
-      "description": "Orchestrates the full release pipeline: version bump → changelog → commit → tag, then conditionally forks to artifact-publish and provenance based on release config. Parent protocol that composes ct-artifact-publisher and ct-provenance-keeper as sub-protocols. Source-only releases skip both sub-protocols entirely.",
+      "version": "3.0.0",
+      "description": "Orchestrates the canonical 4-verb release pipeline introduced by SPEC-T9345: cleo release plan, then cleo release open, then PR + GHA tag workflow, then cleo release reconcile. The deprecated cleo release ship monolith was deleted in T10103 — do not invoke it. Use ship-e2e-smoke to validate the full pipeline end-to-end (dry-run by default). The full verb-to-state map is in docs/release/verb-matrix.md. Use when shipping a new version, validating the release pipeline end-to-end, or promoting a completed epic to released status.",
       "path": "skills/ct-release-orchestrator",
-      "tags": ["release", "orchestration", "composition", "ship", "version"],
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
+      "loomStage": "release",
+      "tags": [
+        "release",
+        "orchestration",
+        "composition",
+        "ship",
+        "version"
+      ],
       "token_budget": 8000,
       "protocol": "release",
-      "loomStage": "release",
-      "adrRefs": ["ADR-053", "ADR-063", "ADR-065"],
+      "adrRefs": [
+        "ADR-053",
+        "ADR-063",
+        "ADR-065"
+      ],
       "references": [
         "skills/ct-release-orchestrator/references/composition.md",
         "skills/ct-release-orchestrator/references/release-types.md"
       ],
       "capabilities": {
-        "inputs": ["version", "epic-id", "release-config"],
-        "outputs": ["release-commit", "git-tag", "changelog-entry", "manifest-entry"],
+        "inputs": [
+          "version",
+          "epic-id",
+          "release-config"
+        ],
+        "outputs": [
+          "release-commit",
+          "git-tag",
+          "changelog-entry",
+          "manifest-entry"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
           "ship release",
@@ -678,11 +1224,26 @@
           "cleo release ship",
           "promote epic to released"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-artifact-publisher", "ct-provenance-keeper"],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-artifact-publisher",
+          "ct-provenance-keeper"
+        ],
         "dispatch_keywords": {
-          "primary": ["release", "ship", "version", "tag"],
-          "secondary": ["changelog", "semver", "bump", "publish"]
+          "primary": [
+            "release",
+            "ship",
+            "version",
+            "tag"
+          ],
+          "secondary": [
+            "changelog",
+            "semver",
+            "bump",
+            "publish"
+          ]
         }
       },
       "constraints": {
@@ -692,124 +1253,379 @@
       }
     },
     {
-      "name": "ct-artifact-publisher",
-      "version": "1.0.0",
-      "description": "Builds and publishes artifacts to registries (npm, PyPI, cargo, docker, GitHub releases, generic tarballs) following the validate → dry-run → build → publish → record-provenance pipeline. Invoked by ct-release-orchestrator as a sub-skill when a release has artifact config. Never stores credentials in output or manifest.",
-      "path": "skills/ct-artifact-publisher",
-      "tags": ["artifact", "publish", "registry", "release", "distribution"],
+      "name": "ct-research-agent",
+      "version": "2.0.0",
+      "description": "Multi-source research and investigation combining web search, documentation lookup via Context7, and codebase analysis. Synthesizes findings into actionable recommendations with proper citation and task traceability. Use when conducting research, investigating best practices, gathering technical information, or analyzing existing implementations. Triggers on research tasks, investigation needs, or information discovery requests.",
+      "path": "skills/ct-research-agent",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
+      "loomStage": "research",
+      "tags": [
+        "research",
+        "investigation",
+        "discovery"
+      ],
       "token_budget": 8000,
-      "protocol": "artifact-publish",
+      "protocol": "research",
+      "adrRefs": [
+        "ADR-023",
+        "ADR-070"
+      ],
       "references": [
-        "skills/ct-artifact-publisher/references/artifact-types.md",
-        "skills/ct-artifact-publisher/references/handler-interface.md"
+        "skills/ct-research-agent/references/triggers-and-routing.md",
+        "skills/ct-research-agent/references/source-strategy.md",
+        "skills/ct-research-agent/references/citation-and-evidence.md",
+        "skills/ct-research-agent/references/anti-patterns.md"
       ],
       "capabilities": {
-        "inputs": ["release-config", "version", "commit-sha"],
-        "outputs": ["built-artifacts", "checksums", "publish-results", "manifest-entry"],
+        "inputs": [
+          "TASK_ID",
+          "TOPIC",
+          "RESEARCH_QUESTIONS"
+        ],
+        "outputs": [
+          "research-file",
+          "manifest-entry"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "publish artifacts",
-          "build and publish",
-          "run artifact publish",
-          "ship packages",
-          "push to registry"
+          "research",
+          "investigate",
+          "gather information",
+          "explore options"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-spec-writer",
+          "ct-epic-architect"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": ["ct-provenance-keeper"],
         "dispatch_keywords": {
-          "primary": ["artifact", "publish", "registry", "package"],
-          "secondary": ["npm", "docker", "cargo", "tarball"]
+          "primary": [
+            "research",
+            "investigate",
+            "explore",
+            "discover"
+          ],
+          "secondary": [
+            "gather",
+            "survey",
+            "analyze",
+            "fact-finding"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
+        "max_context_tokens": 80000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-provenance-keeper",
+      "name": "ct-skill-creator",
       "version": "1.0.0",
-      "description": "Generates in-toto v1 attestations, SLSA-level provenance records, SBOMs (CycloneDX or SPDX), and sigstore/cosign signatures for published artifacts. Invoked by ct-artifact-publisher as a delegation for signing and attestation. Records the full commit→build→artifact→attestation→registry chain in .cleo/releases.json.",
-      "path": "skills/ct-provenance-keeper",
-      "tags": ["provenance", "slsa", "attestation", "sbom", "sigstore", "supply-chain"],
-      "status": "active",
-      "tier": 2,
-      "token_budget": 6000,
-      "protocol": "provenance",
+      "description": "Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.",
+      "path": "skills/ct-skill-creator",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated",
+      "tags": [
+        "skills",
+        "creation",
+        "meta"
+      ],
+      "token_budget": 8000,
       "references": [
-        "skills/ct-provenance-keeper/references/signing.md",
-        "skills/ct-provenance-keeper/references/slsa.md"
+        "skills/ct-skill-creator/references/output-patterns.md",
+        "skills/ct-skill-creator/references/workflows.md"
       ],
       "capabilities": {
-        "inputs": ["built-artifacts", "commit-sha", "builder-identity"],
-        "outputs": ["in-toto-attestation", "sbom", "signature", "releases-json-entry"],
+        "inputs": [
+          "skill_name",
+          "skill_purpose"
+        ],
+        "outputs": [
+          "skill-directory",
+          "SKILL.md"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "generate provenance",
-          "sign artifacts",
-          "create attestation",
-          "record supply chain",
-          "run slsa attestation"
+          "create a new skill",
+          "update an existing skill"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
         ],
-        "compatible_subagent_types": ["general-purpose"],
         "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["provenance", "attestation", "sbom", "slsa"],
-          "secondary": ["sigstore", "cosign", "in-toto", "sign"]
+          "primary": [
+            "skill",
+            "create",
+            "build",
+            "extend"
+          ],
+          "secondary": [
+            "capabilities",
+            "workflow",
+            "integration"
+          ]
         }
       },
       "constraints": {
-        "max_context_tokens": 60000,
+        "max_context_tokens": 80000,
         "requires_session": false,
         "requires_epic": false
       }
     },
     {
-      "name": "ct-council",
+      "name": "ct-skill-validator",
       "version": "1.0.0",
-      "description": "Convene \"The Council\" — a 5-advisor, shuffled gate-based peer-review, chairman-synthesis workflow for reviewing a plan, decision, architecture, or piece of work inside the current project. Operates on the current codebase — each advisor grounds their analysis in actual files/commits before opining. Output is validated by scripts/validate.py.",
-      "path": "skills/ct-council",
-      "tags": ["council", "review", "peer-review", "multi-perspective", "stress-test"],
+      "description": "Validates an existing skill folder against the full CLEO standard and ecosystem. Use when auditing skills for structural compliance, verifying a skill fits into the CLEO ecosystem and constitution, running quality A/B evals, or preparing a skill for distribution. Runs a 3-phase validation loop — structural, ecosystem fit, and quality eval — then presents all findings as an HTML report opened in the user's browser. Iterates until all required phases pass.",
+      "path": "skills/ct-skill-validator",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated"
+    },
+    {
+      "name": "ct-spec-writer",
+      "version": "2.1.0",
+      "description": "Technical specification writing using RFC 2119 language for clear, unambiguous requirements. Creates protocol specifications, technical requirements, API specifications, and architecture documents with testable requirements and compliance criteria. Use when writing specifications, defining protocols, documenting requirements, or creating API contracts. Triggers on specification tasks, protocol definition needs, or requirement documentation.",
+      "path": "skills/ct-spec-writer",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
       "status": "active",
-      "tier": 2,
+      "loomStage": "specification",
+      "tags": [
+        "specification",
+        "documentation",
+        "rfc"
+      ],
       "token_budget": 8000,
+      "protocol": "specification",
+      "adrRefs": [
+        "ADR-014",
+        "ADR-023"
+      ],
       "references": [
-        "skills/ct-council/references/chairman.md",
-        "skills/ct-council/references/contrarian.md",
-        "skills/ct-council/references/evidence-pack.md",
-        "skills/ct-council/references/examples.md",
-        "skills/ct-council/references/executor.md",
-        "skills/ct-council/references/expansionist.md",
-        "skills/ct-council/references/first-principles.md",
-        "skills/ct-council/references/outsider.md",
-        "skills/ct-council/references/peer-review.md"
+        "skills/ct-spec-writer/references/rfc2119-language.md",
+        "skills/ct-spec-writer/references/spec-templates.md",
+        "skills/ct-spec-writer/references/traceability-matrix.md",
+        "skills/ct-spec-writer/references/anti-patterns.md"
       ],
       "capabilities": {
-        "inputs": ["proposal", "plan", "architecture-decision", "task-id"],
-        "outputs": ["council-verdict", "advisor-reports", "convergence-report"],
+        "inputs": [
+          "TASK_ID",
+          "SPEC_NAME",
+          "spec_topic"
+        ],
+        "outputs": [
+          "specification-file",
+          "manifest-entry"
+        ],
         "dependencies": [],
         "dispatch_triggers": [
-          "convene the council",
-          "council review",
-          "run the five advisors",
-          "stress-test this",
-          "get multiple perspectives"
+          "write a spec",
+          "create specification",
+          "define protocol"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-task-executor",
+          "ct-documentor"
+        ],
+        "dispatch_keywords": {
+          "primary": [
+            "spec",
+            "rfc",
+            "protocol",
+            "contract"
+          ],
+          "secondary": [
+            "specification",
+            "requirements",
+            "interface",
+            "architecture"
+          ]
+        }
+      },
+      "constraints": {
+        "max_context_tokens": 80000,
+        "requires_session": false,
+        "requires_epic": false
+      }
+    },
+    {
+      "name": "ct-stickynote",
+      "version": "1.0.0",
+      "description": "Quick ephemeral sticky notes for project-wide capture before formal classification",
+      "path": "skills/ct-stickynote",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated"
+    },
+    {
+      "name": "ct-task-executor",
+      "version": "2.7.0",
+      "description": "General implementation task execution for completing assigned CLEO tasks by following instructions and producing concrete deliverables. Handles coding, configuration, documentation work with quality verification against acceptance criteria and progress reporting. Use when executing implementation tasks, completing assigned work, or producing task deliverables. Triggers on implementation tasks, general execution needs, or task completion work.",
+      "path": "skills/ct-task-executor",
+      "tier": 0,
+      "deliveryTier": "core",
+      "install": "harness",
+      "status": "active",
+      "loomStage": "implementation",
+      "tags": [
+        "execution",
+        "implementation",
+        "task-management"
+      ],
+      "token_budget": 8000,
+      "protocol": "implementation",
+      "adrRefs": [
+        "ADR-070",
+        "ADR-062"
+      ],
+      "references": [
+        "skills/ct-task-executor/references/implementation-patterns.md",
+        "skills/ct-task-executor/references/acceptance-criteria-mapping.md",
+        "skills/ct-task-executor/references/evidence-and-gates.md",
+        "skills/ct-task-executor/references/common-failures.md",
+        "skills/ct-task-executor/references/anti-patterns.md"
+      ],
+      "capabilities": {
+        "inputs": [
+          "TASK_ID",
+          "TASK_NAME",
+          "TASK_INSTRUCTIONS",
+          "DELIVERABLES_LIST",
+          "ACCEPTANCE_CRITERIA"
+        ],
+        "outputs": [
+          "deliverables",
+          "manifest-entry"
+        ],
+        "dependencies": [],
+        "dispatch_triggers": [
+          "execute task",
+          "implement",
+          "complete this task",
+          "build component"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-documentor"
         ],
-        "compatible_subagent_types": ["general-purpose"],
-        "chains_to": [],
         "dispatch_keywords": {
-          "primary": ["council", "advisors", "stress-test", "peer-review"],
-          "secondary": ["contrarian", "first-principles", "expansionist", "outsider", "executor", "chairman"]
+          "primary": [
+            "implement",
+            "build",
+            "execute",
+            "create"
+          ],
+          "secondary": [
+            "complete",
+            "finish",
+            "work on",
+            "carry out"
+          ]
         }
       },
       "constraints": {
         "max_context_tokens": 80000,
+        "requires_session": true,
+        "requires_epic": false
+      }
+    },
+    {
+      "name": "ct-validator",
+      "version": "2.0.0",
+      "description": "Compliance validation for verifying systems, documents, or code against requirements, schemas, or standards. Performs schema validation, code compliance checks, document validation, and protocol compliance verification with detailed pass/fail reporting. Use when validating compliance, checking schemas, verifying code standards, or auditing protocol implementations. Triggers on validation tasks, compliance checks, or quality verification needs.",
+      "path": "skills/ct-validator",
+      "tier": 1,
+      "deliveryTier": "on-demand",
+      "install": "harness",
+      "status": "active",
+      "loomStage": "validation",
+      "tags": [
+        "validation",
+        "compliance",
+        "audit"
+      ],
+      "token_budget": 6000,
+      "protocol": "validation",
+      "adrRefs": [
+        "ADR-051",
+        "ADR-023"
+      ],
+      "references": [
+        "skills/ct-validator/references/validation-modes.md",
+        "skills/ct-validator/references/schema-checking.md",
+        "skills/ct-validator/references/compliance-reports.md",
+        "skills/ct-validator/references/anti-patterns.md"
+      ],
+      "capabilities": {
+        "inputs": [
+          "TASK_ID",
+          "VALIDATION_TARGET",
+          "VALIDATION_CRITERIA"
+        ],
+        "outputs": [
+          "validation-report",
+          "manifest-entry"
+        ],
+        "dependencies": [],
+        "dispatch_triggers": [
+          "validate",
+          "verify",
+          "check compliance",
+          "audit"
+        ],
+        "compatible_subagent_types": [
+          "general-purpose"
+        ],
+        "chains_to": [
+          "ct-ivt-looper"
+        ],
+        "dispatch_keywords": {
+          "primary": [
+            "validate",
+            "verify",
+            "audit",
+            "compliance"
+          ],
+          "secondary": [
+            "check",
+            "conformance",
+            "standards",
+            "requirements"
+          ]
+        }
+      },
+      "constraints": {
+        "max_context_tokens": 60000,
         "requires_session": false,
         "requires_epic": false
       }
+    },
+    {
+      "name": "signaldock-connect",
+      "version": "1.0.0",
+      "description": "Connect any AI agent to SignalDock for agent-to-agent messaging. Use when an agent needs to: (1) register on api.signaldock.io, (2) install the signaldock runtime CLI, (3) send/receive messages to other agents, (4) set up SSE real-time streaming, (5) poll for messages, (6) check inbox, or (7) connect to the SignalDock platform. Triggers on: \"connect to signaldock\", \"register agent\", \"send message to agent\", \"agent messaging\", \"signaldock setup\", \"install signaldock\", \"agent-to-agent\".",
+      "path": "skills/signaldock-connect",
+      "tier": 3,
+      "deliveryTier": "internal",
+      "install": "internal",
+      "status": "deprecated"
     }
   ]
 }