@cleocode/skills 2026.9.21 → 2026.9.22

package/skills/ct-master-tac/bundled/protocols/release.cant

@@ -1,107 +0,0 @@
----
-kind: protocol
-version: 1.0.0
-id: REL
-title: "Release Protocol"
-status: active
-type: conditional
-audience: "llm-agent, orchestrator"
-tags: "release, semver, changelog"
-skillRef: ct-release-orchestrator
-lastUpdated: 2026-04-08
-enforcement: strict
-stage: "release"
-consult-when: "Shipping a new version; running 'cleo release ship'; promoting a completed epic to released status; any task with 'release', 'version bump', 'changelog', 'tag', 'publish'"
-input:
-  version: "string — CalVer YYYY.MM.patch target version"
-  changelog_entries: "string[] — summarized changes since last release"
-  artifact_config: "object | null — artifact publish config; null for source-only releases"
-output:
-  release_tag: "string — git tag created (e.g. v2026.4.5)"
-  changelog_path: "string — path to updated CHANGELOG file"
-  artifacts_published: "boolean — true when artifact phase ran"
-  release_manifest: "object — release summary for pipeline_manifest via cleo manifest append"
----
-
-# Release Protocol
-#
-# Provenance: @task T3155, @epic T3147
-# Type: Conditional Protocol
-# Max Active: 3 protocols (including base)
-#
-# Trigger Conditions
-#
-# This protocol activates when the task involves:
-#   Version: "release", "version", "v1.x.x"
-#   Publish: "publish", "deploy", "ship"
-#   Changelog: "changelog", "release notes"
-#   Tag: "tag", "milestone", "GA"
-#
-# Explicit Override: --protocol release flag on task creation.
-#
-# Requirements (RFC 2119)
-#
-# MUST:
-#   RLSE-001: MUST follow semantic versioning (semver)
-#   RLSE-002: MUST update changelog with all changes
-#   RLSE-003: MUST pass all validation gates before release
-#   RLSE-004: MUST tag release in version control
-#   RLSE-005: MUST document breaking changes with migration path
-#   RLSE-006: MUST verify version consistency across files
-#   RLSE-007: MUST set agent_type: "documentation" in manifest
-#
-# SHOULD:
-#   RLSE-010: SHOULD include upgrade instructions
-#   RLSE-011: SHOULD verify documentation is current
-#   RLSE-012: SHOULD test installation process
-#   RLSE-013: SHOULD create backup before release
-#   RLSE-014: SHOULD run test suite for major/minor releases
-#   RLSE-015: SHOULD verify tests pass before tagging
-#
-# MAY:
-#   RLSE-020: MAY include performance benchmarks
-#   RLSE-021: MAY announce on communication channels
-#   RLSE-022: MAY batch minor fixes into single release
-#
-# State Machine:
-#   create -> planned -> active -> released (immutable)
-#
-# Ship Workflow (10 steps):
-#   1. Auto-populate release tasks
-#   1.5. Run release guards
-#   2. Bump version (if --bump-version)
-#   3. Ensure [Unreleased] section in CHANGELOG.md
-#   4. Generate changelog from task metadata
-#   5. Validate changelog content
-#   6. Append to CHANGELOG.md + platform outputs
-#   7. Run validation gates
-#   8. Create release commit
-#   9. Create annotated tag (if --create-tag)
-#   10. Push to remote (if --push)
-#   11. Update release status to released
-#
-# Composition with Sub-Protocols:
-#   artifact-publish: Conditional, triggered when release config has artifact handlers
-#   provenance: Conditional, invoked transitively via artifact-publish for signing
-#
-# Error Codes (50-59):
-#   50: E_RELEASE_NOT_FOUND
-#   51: E_RELEASE_EXISTS
-#   52: E_RELEASE_LOCKED
-#   53: E_INVALID_VERSION
-#   54: E_VALIDATION_FAILED
-#   55: E_VERSION_BUMP_FAILED
-#   56: E_TAG_CREATION_FAILED
-#   57: E_CHANGELOG_GENERATION_FAILED
-#   58: E_TAG_EXISTS
-#   59: E_TASKS_INCOMPLETE
-#
-# Anti-Patterns:
-#   - Skipping version bump (version confusion)
-#   - Missing changelog entry (lost history)
-#   - Undocumented breaking changes (user frustration)
-#   - No release tag (cannot reference version)
-#   - Incomplete checklist (missed steps)
-#   - Major releases without --run-tests (quality risk)
-#   - Ignoring epic completeness warnings
-#   - Overusing --force (bypasses guards)

package/skills/ct-master-tac/bundled/protocols/research.cant

@@ -1,77 +0,0 @@
----
-kind: protocol
-version: 1.0.0
-id: RSCH
-title: "Research Protocol"
-status: active
-type: base
-audience: "llm-agent, orchestrator"
-tags: "research, investigation, evidence"
-skillRef: ct-research-agent
-lastUpdated: 2026-04-08
-enforcement: strict
-stage: "research"
-consult-when: "Investigating unknown territory; gathering evidence before a consensus or specification; any task with 'research', 'investigate', 'explore', 'study', 'discover', 'analyze'; tasks that explicitly must NOT modify code"
-input:
-  topic: "string — subject of investigation"
-  scope: "string — boundaries of the research (what to include/exclude)"
-  output_dir: "string — directory for findings (default: .cleo/agent-outputs/)"
-output:
-  findings_path: "string — path to the research output markdown file"
-  manifest_entry: "object — 3–7 key findings for pipeline_manifest via cleo manifest append"
-  confidence_levels: "object — per-finding confidence 0.0–1.0"
-  sources: "string[] — cited URLs or file paths"
----
-
-# Research Protocol
-#
-# Provenance: @task T3155, @epic T3147
-# Type: Conditional Protocol
-# Max Active: 3 protocols (including base)
-#
-# Trigger Conditions
-#
-# This protocol activates when the task involves:
-#   Investigation: "research", "investigate", "explore", "study"
-#   Analysis: "analyze", "compare", "evaluate", "assess"
-#   Discovery: "find out", "discover", "learn about"
-#   Documentation: "document findings", "report on"
-#
-# Explicit Override: --protocol research flag on task creation.
-#
-# Requirements (RFC 2119)
-#
-# MUST:
-#   RSCH-001: MUST NOT implement code or make changes to codebase
-#   RSCH-002: MUST document all sources with citations
-#   RSCH-003: MUST write findings to .cleo/agent-outputs/
-#   RSCH-004: MUST append entry via `cleo manifest append`
-#   RSCH-005: MUST return only completion message (no content in response)
-#   RSCH-006: MUST include 3-7 key findings in manifest entry
-#   RSCH-007: MUST set agent_type: "research" in manifest
-#
-# SHOULD:
-#   RSCH-010: SHOULD use multiple independent sources
-#   RSCH-011: SHOULD cross-reference findings for accuracy
-#   RSCH-012: SHOULD include confidence levels for claims
-#   RSCH-013: SHOULD identify gaps or areas needing further research
-#   RSCH-014: SHOULD link research to relevant tasks
-#
-# MAY:
-#   RSCH-020: MAY propose follow-up research tasks
-#   RSCH-021: MAY include visual diagrams or tables
-#   RSCH-022: MAY compare multiple approaches or solutions
-#
-# Tool Allowlist:
-#   Allowed: Read, Grep, Glob, Bash (read-only commands only)
-#   Prohibited: Write, Edit, any code compilation or execution
-#
-# Exit Codes:
-#   EXIT_PROTOCOL_RESEARCH (60) - Research protocol violation
-#
-# Anti-Patterns:
-#   - Implementing code during research (pollutes context, mixes concerns)
-#   - Returning findings in response (wastes orchestrator context)
-#   - Single-source conclusions (risk of bias or error)
-#   - Vague findings without evidence (not actionable)
-#   - Skipping manifest entry (breaks orchestrator workflow)

package/skills/ct-master-tac/bundled/protocols/specification.cant

@@ -1,77 +0,0 @@
----
-kind: protocol
-version: 1.0.0
-id: SPEC
-title: "Specification Protocol"
-status: active
-type: conditional
-audience: "llm-agent, orchestrator"
-tags: "specification, requirements, rfc2119"
-skillRef: ct-spec-writer
-lastUpdated: 2026-04-08
-enforcement: strict
-stage: "specification"
-consult-when: "Writing technical specifications, API contracts, or requirements documents; any task with 'spec', 'specification', 'requirements', 'rfc'; Specification stage only unlocks after an accepted ADR"
-input:
-  adr_id: "string — accepted ADR that governs this specification"
-  scope: "string — what the spec covers"
-  audience: "llm-agent | human | both — intended readers"
-output:
-  spec_path: "string — path to the written specification file"
-  requirement_count: "number — total MUST/SHOULD/MAY requirements"
-  testable_criteria: "string[] — acceptance criteria derivable from the spec"
----
-
-# Specification Protocol
-#
-# Provenance: @task T3155, @epic T3147
-# Type: Conditional Protocol
-# Max Active: 3 protocols (including base)
-#
-# Trigger Conditions
-#
-# This protocol activates when the task involves:
-#   Design: "spec", "specification", "design", "architect"
-#   Contract: "contract", "interface", "API", "schema"
-#   Definition: "define", "formalize", "standardize"
-#   Protocol: "protocol", "workflow", "process"
-#
-# Explicit Override: --protocol specification flag on task creation.
-#
-# Requirements (RFC 2119)
-#
-# MUST:
-#   SPEC-001: MUST use RFC 2119 keywords for requirements
-#   SPEC-002: MUST include version number and status
-#   SPEC-003: MUST define scope and authority
-#   SPEC-004: MUST include conformance criteria
-#   SPEC-005: MUST document related specifications
-#   SPEC-006: MUST use structured format (tables, schemas)
-#   SPEC-007: MUST set agent_type: "specification" in manifest
-#
-# SHOULD:
-#   SPEC-010: SHOULD include examples for each requirement
-#   SPEC-011: SHOULD document failure modes
-#   SPEC-012: SHOULD specify error handling
-#   SPEC-013: SHOULD include changelog
-#
-# MAY:
-#   SPEC-020: MAY include implementation guidance
-#   SPEC-021: MAY reference external standards
-#   SPEC-022: MAY define extension points
-#
-# Version Semantics:
-#   Major (X.0.0): Breaking changes to requirements
-#   Minor (X.Y.0): New requirements, backward compatible
-#   Patch (X.Y.Z): Clarifications, typo fixes
-#
-# Status Lifecycle:
-#   DRAFT -> ACTIVE -> DEPRECATED
-#                  \-> SUPERSEDED (by new spec)
-#
-# Anti-Patterns:
-#   - Vague requirements without levels (cannot verify compliance)
-#   - Missing version number (cannot track changes)
-#   - Undefined scope (unclear authority)
-#   - No examples (hard to implement correctly)
-#   - Skipping RFC 2119 declaration (ambiguous requirement levels)

package/skills/ct-master-tac/bundled/protocols/testing.cant

@@ -1,99 +0,0 @@
----
-kind: protocol
-version: 2.0.0
-id: TEST
-title: "Testing Protocol (Project-Agnostic IVT Loop)"
-status: active
-type: base
-audience: "llm-agent, orchestrator"
-tags: "testing, ivt-loop, autonomous, framework-agnostic, compliance"
-skillRef: ct-ivt-looper
-lastUpdated: 2026-04-08
-enforcement: strict
-stage: "testing"
-consult-when: "Running the IVT loop after implementation; verifying acceptance criteria; any task with 'implement and verify', 'run IVT', 'ship this task', 'verify against spec', or implementation tasks with acceptance criteria"
-input:
-  task_id: "string — task under test"
-  spec_ref: "string | null — specification or acceptance criteria reference"
-  worktree: "string — git worktree path for test execution"
-output:
-  test_framework: "vitest | jest | mocha | pytest | cargo-test | go-test | rspec | phpunit | bats | other"
-  convergence_iterations: "number — IVT loop iterations to convergence"
-  test_results: "object — {passed, failed, skipped} counts"
-  manifest_entry: "object — convergence metrics for pipeline_manifest via cleo manifest append"
----
-
-# Testing Protocol - Project-Agnostic IVT Loop
-#
-# Provenance: @task T260 (replaces T3155 BATS-locked v1)
-# Type: Base Protocol
-# Stage: IVTR - T (Testing, the closure of the IVT loop)
-# Skill: ct-ivt-looper
-#
-# Core Principle:
-#   The loop converges on the spec, not on "tests pass".
-#   Passing tests that don't cover the spec are a failure.
-#
-# Project-Agnostic Mandate:
-#   MUST work in any project. MUST NOT assume a specific language,
-#   test framework, directory layout, or test command.
-#
-# Trigger Conditions
-#
-# This protocol activates when the task involves:
-#   Loop Closure: "ivt loop", "implement and verify", "ship this task"
-#   Test Execution: "run tests", "verify", "test this"
-#   Coverage: "coverage", "test coverage", "missing tests"
-#   Spec Compliance: "satisfy spec", "verify against spec"
-#   Release Gate: "before release", "pre-PR validation", "ship verified"
-#
-# Explicit Override: --protocol testing flag on task creation.
-# Lifecycle Position: After Validation (V), before Release (R)
-#
-# Requirements (RFC 2119)
-#
-# MUST:
-#   TEST-001: MUST identify project test framework via dynamic detection
-#   TEST-002: MUST run IVT loop with explicit iteration counter and MAX_ITERATIONS cap (default 5)
-#   TEST-003: MUST trace each MUST requirement from upstream spec to at least one passing test
-#   TEST-004: MUST achieve 100% pass rate before exiting with ivtLoopConverged: true
-#   TEST-005: MUST exit only when spec is satisfied or MAX_ITERATIONS reached
-#   TEST-006: MUST write test summary to manifest key_findings array
-#   TEST-007: MUST set agent_type: "testing" in manifest
-#   TEST-008: MUST run on feature branch - never on main/master
-#   TEST-009: MUST escalate non-convergence to HITL via exit code 65
-#
-# SHOULD:
-#   TEST-010: SHOULD test edge cases and error paths
-#   TEST-011: SHOULD include setup/teardown fixtures appropriate to framework
-#   TEST-012: SHOULD use descriptive test names tied to spec requirement codes
-#   TEST-013: SHOULD report coverage percentage when framework supports it
-#   TEST-014: SHOULD prefer .cleo/project-context.json testing.command when present
-#
-# MAY:
-#   TEST-020: MAY add golden tests for output verification
-#   TEST-021: MAY add performance benchmarks
-#   TEST-022: MAY add stress/concurrency tests
-#   TEST-023: MAY parallelize IVT loop across independent specs
-#
-# Framework Detection Priority:
-#   1. .cleo/project-context.json testing.command (highest)
-#   2. Auto-detection signals (vitest, jest, pytest, cargo test, go test, etc.)
-#   3. Fallback: ask operator to declare in project-context.json
-#
-# Exit Codes:
-#   0: SUCCESS - Loop converged, manifest recorded
-#   65: HANDOFF_REQUIRED - Non-convergence after MAX_ITERATIONS
-#   67: CONCURRENT_SESSION - Generic testing protocol violation
-#   80: LIFECYCLE_GATE_FAILED - Required gate failed
-#
-# Anti-Patterns:
-#   - Hardcoding vitest/jest/pytest (violates project-agnostic mandate)
-#   - Running tests once and reporting result (testing is a LOOP)
-#   - Skipping validation between iterations
-#   - Bailing silently on non-convergence (must escalate to HITL)
-#   - Marking task complete with failed > 0
-#   - Modifying main/master branch
-#   - Ignoring spec-requirement traceability
-#   - Treating coverage as the convergence metric
-#   - Editing test expectations to match broken code

package/skills/ct-master-tac/bundled/protocols/validation.cant

@@ -1,75 +0,0 @@
----
-kind: protocol
-version: 1.0.0
-id: VALID
-title: "Validation Protocol"
-status: active
-type: base
-audience: "llm-agent, orchestrator"
-tags: "validation, quality, compliance"
-skillRef: ct-validator
-lastUpdated: 2026-04-08
-enforcement: strict
-stage: "validation"
-consult-when: "Validating compliance against a schema, spec, or standard; running quality checks; any task with 'validate', 'compliance', 'verify', 'audit'; post-implementation quality gate"
-input:
-  target: "string — file path, document, or system under validation"
-  schema_ref: "string | null — schema or standard reference"
-  validation_type: "schema | code-style | protocol | document | custom"
-output:
-  passed: "boolean — overall validation result"
-  violations: "object[] — array of {rule, severity, location, message}"
-  report_path: "string — path to detailed validation report"
----
-
-# Validation Protocol
-#
-# Provenance: @task T3155, @epic T3147
-# Type: Conditional Protocol
-# Stage: IVTR - V (Validation)
-# Max Active: 3 protocols (including base)
-#
-# Trigger Conditions
-#
-# This protocol activates when the task involves:
-#   Verification: "validate", "verify", "check", "audit"
-#   Quality: "quality", "qa", "review"
-#   Compliance: "compliance", "conform", "standard"
-#   Smoke Test: "smoke", "sanity", "basic test"
-#
-# Explicit Override: --protocol validation flag on task creation.
-# Lifecycle Position: After Implementation (I), before Testing (T)
-#
-# Requirements (RFC 2119)
-#
-# MUST:
-#   VALID-001: MUST verify implementation matches specification
-#   VALID-002: MUST run existing test suite and report results
-#   VALID-003: MUST check protocol compliance via lib/protocol-validation.sh
-#   VALID-004: MUST document pass/fail status for each validation check
-#   VALID-005: MUST write validation summary to manifest
-#   VALID-006: MUST set agent_type: "validation" in manifest
-#   VALID-007: MUST block progression if critical validations fail
-#
-# SHOULD:
-#   VALID-010: SHOULD verify edge cases identified in specification
-#   VALID-011: SHOULD check for regressions in related functionality
-#   VALID-012: SHOULD validate error handling paths
-#   VALID-013: SHOULD measure against acceptance criteria
-#
-# MAY:
-#   VALID-020: MAY perform performance validation
-#   VALID-021: MAY verify security constraints
-#   VALID-022: MAY suggest additional test cases
-#
-# Exit Codes:
-#   62: Specification mismatch (fix implementation)
-#   64: Implementation protocol violation (fix provenance)
-#   67: Generic protocol violation (review and fix)
-#   68: EXIT_VALIDATION_INCOMPLETE (validation not finished)
-#
-# Anti-Patterns:
-#   - Skipping spec compliance check (missed requirements)
-#   - Not documenting validation results (lost audit trail)
-#   - Ignoring non-critical failures (quality regression)
-#   - Running partial validation suite (false confidence)

package/skills/ct-master-tac/bundled/teams/platform.cant

@@ -1,115 +0,0 @@
-# @source .cleo/teams.cant (canonical seed — copied by ct-master-tac T430)
-# @task T430 @epic T382
-# Canonical platform team for CleoOS multi-agent hierarchy.
-#
-# Mirrors the 3-tier structure from ULTRAPLAN §10 and the Pi multi-team config
-# at /mnt/projects/agentic-engineer/lead-agents/.pi/multi-team/multi-team-config.yaml.
-#
-# Three leads map to the RCASD-IVTR+C lifecycle:
-#   - planning-lead:    research, consensus, architecture-decision, specification, decomposition
-#   - engineering-lead: implementation
-#   - validation-lead:  validation, testing, release
-#
-# Workers under each lead are listed in the `workers:` sub-block.
-# Enforcement is strict — the tool_call hook rejects Edit/Write/Bash on lead-role agents.
-
-team platform:
-  name: Platform Team
-  orchestrator: cleo-prime
-  enforcement: strict
-  consult-when: "Orchestrator-level escalation when a request crosses team boundaries or requires human-in-the-loop governance"
-  stages: [research, consensus, architecture-decision, specification, decomposition, implementation, validation, testing, release]
-
-  leads:
-    planning: planning-lead
-    engineering: engineering-lead
-    validation: validation-lead
-
-  workers:
-    planning: [product-manager, ux-researcher, spec-writer]
-    engineering: [backend-dev, frontend-dev, platform-engineer]
-    validation: [qa-engineer, security-reviewer, release-manager]
-
-agent planning-lead:
-  role: lead
-  description: "Decides WHAT to build and why — owns research, consensus, ADRs, specs, and decomposition. Dispatches to planning workers. MUST NOT execute Edit/Write/Bash directly."
-  consult-when: "Deciding WHAT to build and why — research, consensus, ADRs, specs, decomposition"
-  stages: [research, consensus, architecture-decision, specification, decomposition]
-  workers:
-    - product-manager
-    - ux-researcher
-    - spec-writer
-
-agent engineering-lead:
-  role: lead
-  description: "Decides HOW to build — owns implementation strategy, code review, and refactoring direction. Dispatches to engineering workers. MUST NOT execute Edit/Write/Bash directly."
-  consult-when: "Deciding HOW to build — implementation, code writing, refactoring, API design"
-  stages: [implementation]
-  workers:
-    - backend-dev
-    - frontend-dev
-    - platform-engineer
-
-agent validation-lead:
-  role: lead
-  description: "Verifies it works — owns validation, testing strategy, security review, and release gating. Dispatches to validation workers. MUST NOT execute Edit/Write/Bash directly."
-  consult-when: "Does it work — validation, testing, security review, release"
-  stages: [validation, testing, release]
-  workers:
-    - qa-engineer
-    - security-reviewer
-    - release-manager
-
-agent product-manager:
-  role: worker
-  description: "Requirements, feature prioritization, user stories, acceptance criteria"
-  tier: mid
-  consult-when: "Requirements, feature prioritization, user stories, acceptance criteria"
-
-agent ux-researcher:
-  role: worker
-  description: "User behavior, personas, journey mapping, usability, friction points"
-  tier: mid
-  consult-when: "User behavior, personas, journey mapping, usability, friction points"
-
-agent spec-writer:
-  role: worker
-  description: "Authoring ADRs, technical specifications, and RFC 2119 protocol documents"
-  tier: mid
-  consult-when: "ADR authoring, specification writing, protocol documents"
-
-agent backend-dev:
-  role: worker
-  description: "APIs, databases, infrastructure, background jobs, third-party integrations"
-  tier: mid
-  consult-when: "APIs, databases, infrastructure, background jobs, third-party integrations"
-
-agent frontend-dev:
-  role: worker
-  description: "UI components, layouts, client-side state, browser APIs, CSS"
-  tier: mid
-  consult-when: "UI components, layouts, client-side state, browser APIs, CSS"
-
-agent platform-engineer:
-  role: worker
-  description: "Build systems, CI/CD, monorepo tooling, deployment pipelines"
-  tier: mid
-  consult-when: "Build systems, CI/CD, monorepo tooling, deployment pipelines"
-
-agent qa-engineer:
-  role: worker
-  description: "Test cases, regression testing, automation, bug reproduction"
-  tier: mid
-  consult-when: "Test cases, regression testing, automation, bug reproduction"
-
-agent security-reviewer:
-  role: worker
-  description: "Threat modeling, authentication, authorization, data protection, OWASP"
-  tier: mid
-  consult-when: "Threat modeling, authentication, authorization, data protection, OWASP"
-
-agent release-manager:
-  role: worker
-  description: "Version gating, changelog authoring, npm publish, CalVer policy enforcement"
-  tier: mid
-  consult-when: "Version gating, changelog, npm publish, release notes"

package/skills/ct-master-tac/manifest.json

@@ -1,55 +0,0 @@
-{
-  "_comment": "ct-master-tac manifest — merge into packages/skills/skills/manifest.json skills[] array",
-  "name": "ct-master-tac",
-  "version": "1.0.0",
-  "description": "Master Tactical Bundle: installs all 12 CANT protocol files + platform team definition for a batteries-included CleoOS autonomous execution environment.",
-  "path": "skills/ct-master-tac",
-  "tags": ["bundle", "bootstrap", "protocols", "cant", "meta", "install"],
-  "status": "active",
-  "tier": 1,
-  "token_budget": 4000,
-  "protocol": null,
-  "files": [
-    "bundled/protocols/research.cant",
-    "bundled/protocols/consensus.cant",
-    "bundled/protocols/architecture-decision.cant",
-    "bundled/protocols/specification.cant",
-    "bundled/protocols/decomposition.cant",
-    "bundled/protocols/implementation.cant",
-    "bundled/protocols/validation.cant",
-    "bundled/protocols/testing.cant",
-    "bundled/protocols/contribution.cant",
-    "bundled/protocols/release.cant",
-    "bundled/protocols/artifact-publish.cant",
-    "bundled/protocols/provenance.cant",
-    "bundled/teams/platform.cant"
-  ],
-  "install_targets": {
-    "protocols": "packages/core/src/validation/protocols/cant/",
-    "teams": ".cleo/"
-  },
-  "capabilities": {
-    "inputs": ["--verify", "--force"],
-    "outputs": ["install-summary", "verification-report"],
-    "dependencies": [],
-    "dispatch_triggers": [
-      "install master tac",
-      "bootstrap protocols",
-      "tools.skill.install ct-master-tac",
-      "verify protocol bundle",
-      "repair protocol files",
-      "fresh CleoOS install"
-    ],
-    "compatible_subagent_types": ["general-purpose"],
-    "chains_to": ["ct-cleo"],
-    "dispatch_keywords": {
-      "primary": ["master-tac", "bootstrap", "install", "protocol-bundle"],
-      "secondary": ["cant", "protocols", "team", "fresh-install", "recover"]
-    }
-  },
-  "constraints": {
-    "max_context_tokens": 20000,
-    "requires_session": false,
-    "requires_epic": false
-  }
-}

package/skills/ct-skill-creator/manifest-entry.json

@@ -1,17 +0,0 @@
-{
-  "name": "ct-skill-creator",
-  "version": "1.0.0",
-  "description": "Guide for creating effective CLEO skills with the full v2 standard.",
-  "path": "packages/skills/skills/ct-skill-creator",
-  "status": "active",
-  "tier": 3,
-  "core": false,
-  "category": "meta",
-  "protocol": null,
-  "dependencies": [],
-  "sharedResources": [],
-  "compatibility": ["claude-code", "cursor", "windsurf", "gemini-cli"],
-  "token_budget": 12000,
-  "capabilities": ["skill-creation", "eval-loop", "description-optimization", "quality-eval"],
-  "constraints": ["requires-claude-api-for-eval-loop"]
-}

package/skills/ct-skill-validator/manifest-entry.json

@@ -1,20 +0,0 @@
-{
-  "_comment": "CLEO-only metadata -- add to packages/skills/skills/manifest.json",
-  "name": "ct-skill-validator",
-  "version": "1.0.0",
-  "tier": 2,
-  "token_budget": 6000,
-  "capabilities": {
-    "inputs": [],
-    "outputs": [],
-    "dispatch_triggers": [],
-    "compatible_subagent_types": ["general-purpose"],
-    "chains_to": [],
-    "dispatch_keywords": { "primary": [], "secondary": [] }
-  },
-  "constraints": {
-    "max_context_tokens": 60000,
-    "requires_session": false,
-    "requires_epic": false
-  }
-}