popup-studio-aipopup-studio-ai/bkit-claude-code/skills/control/SKILL.md

control

Skill605 starsChanged 3 months agoApache-2.0View on GitHub

Control bkit automation level (L0-L4), view trust score, and manage guardrails. Trust level directly drives SPRINT_AUTORUN_SCOPE (v2.1.13): L0 manual+stopAfter=prd, L4 full-auto+stopAfter=archived. Also gates PDCA phase transitions and destructive operations. Triggers: control, automation level, trust score, guardrail

8 other projects use a version of this.

Adopted by

Most recently taken up by

koltyakov/controltheir own version, first seen Nov 3, 2026
SynchronetBBS/sbbstheir own version, first seen Oct 9, 2026
BackToCimaCoppi/Praxistheir own version, first seen Sep 23, 2026
ww-w-ai/bkit-claude-codeword for word, first seen Aug 14, 2026
Nexus-Organization-Infosec/ClaudeSkillstheir own version, first seen Aug 4, 2026
wildewouter/skillstheir own version, first seen Jul 2, 2026

Other versions8 projects use a version of this.
Word for word · 1
ww-w-ai/bkit-claude-code★ 605100% same
Edited · 0
None found.
Wrote their own version · 7
SynchronetBBS/sbbs★ 115same name
ww-w-ai/bkit-gemini★ 66same name
BackToCimaCoppi/Praxis★ 6same name
koltyakov/control★ 3same name
Nexus-Organization-Infosec/ClaudeSkills★ 1same name
dacrypt/tesla-claude-plugin★ 0same name
wildewouter/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- auditSkill
- bkend-authSkill
- bkend-cookbookSkill
- bkend-dataSkill
- bkend-quickstartSkill
- bkend-storageSkill
- bkit-evalsSkill
- bkit-exploreSkill
- bkit-rulesSkill
- bkitSkill
- bkit-templatesSkill
- btwSkill
- cc-version-analysisSkill
- claude-code-learningSkill
- code-reviewSkill
- deploySkill
- desktop-appSkill
- development-pipelineSkill
- dynamicSkill
- enterpriseSkill
- mobile-appSkill
- pdca-batchSkill
- pdca-fast-trackSkill
- pdcaSkill
- pdca-watchSkill
- phase-1-schemaSkill
- phase-2-conventionSkill
- phase-3-mockupSkill
- phase-4-apiSkill
- phase-5-design-systemSkill
- phase-6-ui-integrationSkill
- phase-7-seo-securitySkill
- phase-8-reviewSkill
- phase-9-deploymentSkill
- plan-plusSkill
- pm-discoverySkill
- qa-phaseSkill
- rollbackSkill
- skill-createSkill
- skill-statusSkill
- sprintSkill
- starterSkill
- zero-script-qaSkill

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.

0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read runtime control state from .bkit/runtime/control-state.json
line 56
Very specific:
Read trust score from .bkit/state/trust-score.json
line 57
Very specific:
Read active guardrails from lib/control/ configuration
line 58
Very specific:
Read current level from .bkit/runtime/control-state.json
line 87
Distinctive:
If escalating (going higher), warn user about reduced oversight
line 88
Distinctive:
If de-escalating, apply immediately without confirmation
line 89
Very specific:
Update .bkit/runtime/control-state.json with new level
line 90
Very specific:
Write audit log entry via lib/audit/audit-logger.js
line 91
Very specific:
Write audit log: automation_paused
line 113
Very specific:
Read previousLevel from .bkit/runtime/control-state.json
line 120
Distinctive:
If not paused, display: "Automation is not paused."
line 121

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Control Skill

User-invocable skill for managing bkit automation level and system status.

Arguments

Argument	Description	Example
(none)	Show current status (same as `status`)	`/control`
`status`	Show automation level, trust score, guardrails	`/control status`
`level <0-4>`	Set automation level manually	`/control level 2`
`pause`	Pause all automation (equivalent to L0)	`/control pause`
`resume`	Resume to previous automation level	`/control resume`
`trust`	Show trust score details and history	`/control trust`

Automation Levels

Level	Name	Description	Approval Gates
L0	Manual	All actions require explicit user approval	Every phase transition
L1	Guided	Suggestions provided, user confirms each step	Every phase transition
L2	Semi-Auto	Routine transitions auto, key decisions gated	do->check, check->report, report->archive
L3	Auto	Most transitions auto, only destructive ops gated	report->archive
L4	Full-Auto	Fully automated PDCA cycle, minimal intervention	Initial feature approval only

Action Details

status (Default)

Display the current automation control state.

Read runtime control state from .bkit/runtime/control-state.json
Read trust score from .bkit/state/trust-score.json
Read active guardrails from lib/control/ configuration
Display formatted status panel

Output Format:

--- bkit Control Panel ----------------------------
Automation Level : L2 (Semi-Auto)
Trust Score      : 72/100
Active Guardrails: 8/8
Paused           : No
Features Active  : 2/3
---------------------------------------------------
Guardrails:
  [ON] Destructive operation detection
  [ON] Blast radius limiter (max 10 files)
  [ON] Loop breaker (max 5 iterations)
  [ON] Checkpoint auto-creation
  [ON] Permission escalation gate
  [ON] Stale feature timeout (7d)
  [ON] Context overflow protection
  [ON] Concurrent write lock
---------------------------------------------------

level <0-4>

Set the automation level manually.

Validate input is a number 0-4
Read current level from .bkit/runtime/control-state.json
If escalating (going higher), warn user about reduced oversight
If de-escalating, apply immediately without confirmation
Update .bkit/runtime/control-state.json with new level
Write audit log entry via lib/audit/audit-logger.js
Display confirmation with new level details

Escalation Rule: Level increases require explicit confirmation via AskUserQuestion. Level decreases are immediate (safe direction).

Level Mapping to Automation:

Level	automationLevel	Description
L0	manual	All manual
L1	guide	Guided suggestions
L2	semi-auto	Semi-automatic (default)
L3	auto	Mostly automatic
L4	full-auto	Fully automatic

pause

Pause all automation immediately.

Save current level to .bkit/runtime/control-state.json as previousLevel
Set level to L0 (Manual)
Set paused: true flag
Write audit log: automation_paused
Display confirmation: "Automation paused. All operations require manual approval."

resume

Resume automation to the previous level before pause.

Read previousLevel from .bkit/runtime/control-state.json
If not paused, display: "Automation is not paused."
Restore level to previousLevel
Clear paused flag
Write audit log: automation_resumed
Display confirmation with restored level

trust

Show trust score details and contributing factors.

Read trust score from .bkit/state/trust-score.json
Calculate score breakdown:
- PDCA completion rate (0-25 points)
- Match rate average (0-25 points)
- Error recovery rate (0-20 points)
- Session stability (0-15 points)
- User override frequency (0-15 points, inverse)
Display detailed breakdown

Output Format:

--- Trust Score Details ---------------------------
Overall Score: 72/100

Breakdown:
  PDCA Completion Rate  : 18/25  (72% cycles completed)
  Match Rate Average    : 22/25  (88% average)
  Error Recovery Rate   : 14/20  (70% recovered)
  Session Stability     : 12/15  (80% stable)
  User Override Freq    :  6/15  (40% override rate)
---------------------------------------------------
Level Recommendation: L2 (Semi-Auto)
  Score 0-30  -> L0 (Manual)
  Score 31-50 -> L1 (Guided)
  Score 51-70 -> L2 (Semi-Auto)
  Score 71-85 -> L3 (Auto)
  Score 86+   -> L4 (Full-Auto)
---------------------------------------------------

State Files

File	Purpose
`.bkit/runtime/control-state.json`	Runtime control state (level, paused, previousLevel)
`.bkit/state/trust-score.json`	Trust score and contributing metrics

Module Dependencies

Module	Function	Usage
`lib/control/automation-controller.js`	`getLevel()`, `setLevel()`	Read/write automation level
`lib/control/automation-controller.js`	`pause()`, `resume()`	Pause/resume automation
`lib/audit/audit-logger.js`	`writeAuditLog()`	Record control changes

Usage Examples

# Check current status
/control

# Set to Semi-Auto
/control level 2

# Pause all automation
/control pause

# Resume previous level
/control resume

# View trust score
/control trust

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free