@cleocode/skills 2026.9.19 → 2026.9.21
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/_shared/task-system-integration.md +1 -1
- package/skills/ct-adr-recorder/SKILL.md +5 -0
- package/skills/ct-artifact-publisher/SKILL.md +5 -0
- package/skills/ct-cleo/SKILL.md +73 -9
- package/skills/ct-cleo/__tests__/injection-content.test.ts +62 -13
- package/skills/ct-cleo/references/session-protocol.md +6 -1
- package/skills/ct-codebase-mapper/SKILL.md +5 -1
- package/skills/ct-consensus-voter/SKILL.md +5 -0
- package/skills/ct-contribution/SKILL.md +5 -1
- package/skills/ct-council/SKILL.md +5 -0
- package/skills/ct-dev-workflow/SKILL.md +2 -1
- package/skills/ct-docs-lookup/SKILL.md +5 -1
- package/skills/ct-docs-review/SKILL.md +5 -1
- package/skills/ct-docs-write/SKILL.md +5 -1
- package/skills/ct-documentor/SKILL.md +11 -8
- package/skills/ct-epic-architect/SKILL.md +5 -1
- package/skills/ct-grade/SKILL.md +5 -1
- package/skills/ct-ivt-looper/SKILL.md +5 -0
- package/skills/ct-lead/SKILL.md +5 -0
- package/skills/ct-master-tac/SKILL.md +5 -1
- package/skills/ct-master-tac/__tests__/install.test.ts +25 -4
- package/skills/ct-memory/SKILL.md +5 -0
- package/skills/ct-orchestrator/SKILL.md +21 -2
- package/skills/ct-provenance-keeper/SKILL.md +5 -0
- package/skills/ct-release-orchestrator/SKILL.md +2 -0
- package/skills/ct-research-agent/SKILL.md +5 -1
- package/skills/ct-skill-creator/SKILL.md +5 -0
- package/skills/ct-skill-validator/SKILL.md +5 -0
- package/skills/ct-spec-writer/SKILL.md +5 -1
- package/skills/ct-stickynote/SKILL.md +5 -1
- package/skills/ct-task-executor/SKILL.md +4 -7
- package/skills/ct-task-executor/references/common-failures.md +2 -2
- package/skills/ct-task-executor/references/evidence-and-gates.md +1 -0
- package/skills/ct-validator/SKILL.md +5 -1
- package/skills/manifest.json +1258 -442
- package/skills/signaldock-connect/SKILL.md +5 -0
|
@@ -2,8 +2,10 @@
|
|
|
2
2
|
name: ct-orchestrator
|
|
3
3
|
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."
|
|
4
4
|
metadata:
|
|
5
|
-
version:
|
|
6
|
-
|
|
5
|
+
version: 4.0.0
|
|
6
|
+
tier: core
|
|
7
|
+
install: harness
|
|
8
|
+
lastReviewed: 2026-09-28
|
|
7
9
|
stability: stable
|
|
8
10
|
---
|
|
9
11
|
|
|
@@ -229,6 +231,23 @@ On an idle host every ready task is `admitted` and behaviour is unchanged.
|
|
|
229
231
|
### 4. Report to Human
|
|
230
232
|
|
|
231
233
|
After each wave or on request: what completed, blockers needing HITL, next actions.
|
|
234
|
+
Report only when work is done or a decision is needed; no routine status chatter.
|
|
235
|
+
|
|
236
|
+
## Asking the Owner (HITL ask tool)
|
|
237
|
+
|
|
238
|
+
Whenever the owner must answer, decide, approve or choose ANYTHING, ask through
|
|
239
|
+
the ask tool (`AskUserQuestion` in Claude Code, or the provider equivalent from
|
|
240
|
+
CAAMP's `PROVIDER_ASK_TOOLS`) with concrete, detailed, selectable options. Never
|
|
241
|
+
ask inside a response, and never bury a question or decision in prose. Each option
|
|
242
|
+
states what happens and its trade-offs, with the recommended option first.
|
|
243
|
+
|
|
244
|
+
- **Subagent relay.** Subagents never ask the human (most harnesses deny them the
|
|
245
|
+
ask tool). A subagent that needs a decision returns `blocked` with
|
|
246
|
+
`{question, options[{label, description}], recommended}` in its manifest entry;
|
|
247
|
+
you, the orchestrator, put that question to the owner via your ask tool, then
|
|
248
|
+
re-spawn or continue with the answer.
|
|
249
|
+
- **Fallback.** When your harness has no ask tool, emit one LAFS `hitl.request`
|
|
250
|
+
envelope `{question, options[{label, description}], recommended}` and stop.
|
|
232
251
|
|
|
233
252
|
## Handoff Chain Protocol
|
|
234
253
|
|
|
@@ -1,6 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-provenance-keeper
|
|
3
3
|
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."
|
|
4
|
+
metadata:
|
|
5
|
+
version: 1.0.0
|
|
6
|
+
tier: on-demand
|
|
7
|
+
install: harness
|
|
8
|
+
stability: stable
|
|
4
9
|
---
|
|
5
10
|
|
|
6
11
|
# Provenance Keeper
|
|
@@ -2,7 +2,6 @@
|
|
|
2
2
|
name: ct-research-agent
|
|
3
3
|
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.
|
|
4
4
|
version: 2.0.0
|
|
5
|
-
tier: 2
|
|
6
5
|
core: false
|
|
7
6
|
category: recommended
|
|
8
7
|
protocol: research
|
|
@@ -20,6 +19,11 @@ compatibility:
|
|
|
20
19
|
- windsurf
|
|
21
20
|
- gemini-cli
|
|
22
21
|
license: MIT
|
|
22
|
+
metadata:
|
|
23
|
+
version: 2.0.0
|
|
24
|
+
tier: on-demand
|
|
25
|
+
install: harness
|
|
26
|
+
stability: stable
|
|
23
27
|
---
|
|
24
28
|
|
|
25
29
|
# Research Context Injection
|
|
@@ -2,6 +2,11 @@
|
|
|
2
2
|
name: ct-skill-creator
|
|
3
3
|
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.
|
|
4
4
|
license: MIT
|
|
5
|
+
metadata:
|
|
6
|
+
version: 1.0.0
|
|
7
|
+
tier: internal
|
|
8
|
+
install: internal
|
|
9
|
+
stability: deprecated
|
|
5
10
|
---
|
|
6
11
|
|
|
7
12
|
# Skill Creator
|
|
@@ -3,6 +3,11 @@ name: ct-skill-validator
|
|
|
3
3
|
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.
|
|
4
4
|
disable-model-invocation: true
|
|
5
5
|
allowed-tools: Bash(python *)
|
|
6
|
+
metadata:
|
|
7
|
+
version: 1.0.0
|
|
8
|
+
tier: internal
|
|
9
|
+
install: internal
|
|
10
|
+
stability: deprecated
|
|
6
11
|
---
|
|
7
12
|
|
|
8
13
|
# CLEO Skill Validator
|
|
@@ -2,7 +2,6 @@
|
|
|
2
2
|
name: ct-spec-writer
|
|
3
3
|
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.
|
|
4
4
|
version: 2.1.0
|
|
5
|
-
tier: 2
|
|
6
5
|
core: false
|
|
7
6
|
category: recommended
|
|
8
7
|
protocol: specification
|
|
@@ -20,6 +19,11 @@ compatibility:
|
|
|
20
19
|
- windsurf
|
|
21
20
|
- gemini-cli
|
|
22
21
|
license: MIT
|
|
22
|
+
metadata:
|
|
23
|
+
version: 2.1.0
|
|
24
|
+
tier: on-demand
|
|
25
|
+
install: harness
|
|
26
|
+
stability: stable
|
|
23
27
|
---
|
|
24
28
|
|
|
25
29
|
# Specification Writer Context Injection
|
|
@@ -3,7 +3,6 @@ name: ct-stickynote
|
|
|
3
3
|
description: Quick ephemeral sticky notes for project-wide capture before formal classification
|
|
4
4
|
version: 1.0.0
|
|
5
5
|
category: productivity
|
|
6
|
-
tier: 0
|
|
7
6
|
protocol: null
|
|
8
7
|
tags: [sticky, notes, capture, quick, ephemeral]
|
|
9
8
|
triggers: [note, sticky, jot, capture]
|
|
@@ -11,6 +10,11 @@ compatibility: [claude-code, gemini-cli, codex-cli, opencode]
|
|
|
11
10
|
dependencies: []
|
|
12
11
|
sharedResources: []
|
|
13
12
|
license: MIT
|
|
13
|
+
metadata:
|
|
14
|
+
version: 1.0.0
|
|
15
|
+
tier: internal
|
|
16
|
+
install: internal
|
|
17
|
+
stability: deprecated
|
|
14
18
|
---
|
|
15
19
|
|
|
16
20
|
# Sticky Notes Skill
|
|
@@ -1,12 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ct-task-executor
|
|
3
3
|
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.
|
|
4
|
-
version: 2.
|
|
5
|
-
metadata:
|
|
6
|
-
version: 2.2.0
|
|
7
|
-
lastReviewed: 2026-09-19
|
|
8
|
-
stability: stable
|
|
9
|
-
tier: 2
|
|
4
|
+
version: 2.7.0
|
|
10
5
|
core: true
|
|
11
6
|
category: core
|
|
12
7
|
protocol: implementation
|
|
@@ -26,7 +21,9 @@ compatibility:
|
|
|
26
21
|
license: MIT
|
|
27
22
|
metadata:
|
|
28
23
|
version: 2.7.0
|
|
29
|
-
|
|
24
|
+
tier: core
|
|
25
|
+
install: harness
|
|
26
|
+
lastReviewed: 2026-09-19
|
|
30
27
|
stability: stable
|
|
31
28
|
---
|
|
32
29
|
|
|
@@ -43,8 +43,8 @@ not in the worktree's branch.
|
|
|
43
43
|
(persistent shell state was not reset between tool calls), or
|
|
44
44
|
deliberately followed an absolute path from a prior session's notes.
|
|
45
45
|
|
|
46
|
-
**Fix.** The spawn prompt's
|
|
47
|
-
|
|
46
|
+
**Fix.** The spawn prompt's FIRST ACTION guard, `cd '<path>' || exit 1`
|
|
47
|
+
(single-quoted, so it survives spaces), MUST start every Bash call. All subsequent paths SHOULD be absolute within the worktree.
|
|
48
48
|
If unsure, prefix with `git rev-parse --show-toplevel` first.
|
|
49
49
|
|
|
50
50
|
## Cherry-Pick Instead of Merge
|
|
@@ -140,6 +140,7 @@ cleo memory observe "..." --title "..."
|
|
|
140
140
|
| — | `E_EVIDENCE_INSUFFICIENT` | Gate atom kind doesn't match required | See gate-atom table above |
|
|
141
141
|
| — | `E_EVIDENCE_TESTS_FAILED` | `tool:test` exit non-zero | Fix failing tests first |
|
|
142
142
|
| — | `E_EVIDENCE_TOOL_FAILED` | Lint/typecheck/etc exit non-zero | Fix source and re-run |
|
|
143
|
+
| — | `E_EVIDENCE_TOOL_VACUOUS` | Tool exited 0 but provably checked nothing (`tsc` without `-b` on a references-only tsconfig) | Add a covering `typecheck` script (e.g. `tsc -b`) or set `typecheck.command` in `.cleo/project-context.json` |
|
|
143
144
|
| — | `E_EVIDENCE_STALE` | Files or commit changed after verify | Re-verify before complete |
|
|
144
145
|
| — | `E_EVIDENCE_INVALID_DECISION` | Decision ID not found in BRAIN | Use `cleo memory decision-find` |
|
|
145
146
|
| — | `E_FLAG_REMOVED` | Tried `cleo complete --force` | `--force` removed per ADR-051 |
|
|
@@ -2,7 +2,6 @@
|
|
|
2
2
|
name: ct-validator
|
|
3
3
|
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.
|
|
4
4
|
version: 2.0.0
|
|
5
|
-
tier: 2
|
|
6
5
|
core: false
|
|
7
6
|
category: recommended
|
|
8
7
|
protocol: validation
|
|
@@ -20,6 +19,11 @@ compatibility:
|
|
|
20
19
|
- windsurf
|
|
21
20
|
- gemini-cli
|
|
22
21
|
license: MIT
|
|
22
|
+
metadata:
|
|
23
|
+
version: 2.0.0
|
|
24
|
+
tier: on-demand
|
|
25
|
+
install: harness
|
|
26
|
+
stability: stable
|
|
23
27
|
---
|
|
24
28
|
|
|
25
29
|
# Validator Context Injection
|