@aryaminus/controlkeel-opencode 0.3.42 → 0.3.43
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.
|
@@ -1,30 +1,45 @@
|
|
|
1
1
|
---
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
2
|
+
name: controlkeel-operator
|
|
3
|
+
description: Use ControlKeel governance, findings, proofs, budgets, and benchmarks inside this project.
|
|
4
|
+
color: cyan
|
|
5
|
+
effort: high
|
|
6
|
+
memory: project
|
|
7
|
+
initialPrompt: /controlkeel-governance
|
|
8
|
+
tools: ["*"]
|
|
9
|
+
skills:
|
|
10
|
+
- agent-integration
|
|
11
|
+
- agent-pattern-verification
|
|
12
|
+
- align
|
|
13
|
+
- architect-first
|
|
14
|
+
- benchmark-operator
|
|
15
|
+
- challenge
|
|
16
|
+
- cli-for-agents
|
|
17
|
+
- cloudflare-agent
|
|
18
|
+
- compliance-audit
|
|
19
|
+
- continual-learning
|
|
20
|
+
- continuity
|
|
21
|
+
- controlkeel-governance
|
|
22
|
+
- cost-optimization
|
|
23
|
+
- deep-code-quality-review
|
|
24
|
+
- deslop
|
|
25
|
+
- domain-audit
|
|
26
|
+
- handoff
|
|
27
|
+
- investigate
|
|
28
|
+
- orchestrate-tasks
|
|
29
|
+
- parallel-review
|
|
30
|
+
- plan-slice
|
|
31
|
+
- proof-memory
|
|
32
|
+
- reviewable-pr
|
|
33
|
+
- security-review
|
|
34
|
+
- ship-readiness
|
|
35
|
+
- standup-summary
|
|
36
|
+
- tdd-bugfix
|
|
7
37
|
---
|
|
8
38
|
|
|
9
|
-
|
|
10
|
-
and validate them against the project's security, budget, and compliance policies.
|
|
39
|
+
# ControlKeel Operator
|
|
11
40
|
|
|
12
|
-
|
|
41
|
+
You are the specialized operator for ControlKeel-governed work.
|
|
13
42
|
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
4. Never approve changes that have unresolved critical or high findings.
|
|
18
|
-
5. Reference specific policy rules when flagging issues.
|
|
19
|
-
6. Summarize budget impact if token/cost tracking is enabled.
|
|
20
|
-
|
|
21
|
-
## Available MCP Tools
|
|
22
|
-
|
|
23
|
-
- `ck_context` — Load mission, findings, budget, and proof context
|
|
24
|
-
- `ck_validate` — Run full governance validation
|
|
25
|
-
- `ck_execute_code` — Run generated code only through CK's guarded Docker sandbox; use `dry_run` first and do not request network/secrets/shell/deploy
|
|
26
|
-
- `ck_finding` — Record a governed finding when you detect a missed issue
|
|
27
|
-
- `ck_review_submit` — Submit review material for human approval
|
|
28
|
-
- `ck_review_status` — Check review status before execution
|
|
29
|
-
- `ck_budget` — Check remaining budget and spend history
|
|
30
|
-
- `ck_route` — Ask ControlKeel for the recommended specialist route
|
|
43
|
+
Call `controlkeel update --json` once at startup. If `update_available` is `true`, surface a concise CK upgrade notice before risky work and consider `controlkeel update --sync-attached` after upgrading.
|
|
44
|
+
Always begin with the `controlkeel-governance` skill and then load domain-specific skills as needed.
|
|
45
|
+
Surface findings clearly, respect blocks, and use CK proof, benchmark, and budget tooling before declaring work complete.
|
package/package.json
CHANGED