Control logo

Control

Organization
ww-w-ai
control

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

Overview

Publisherww-w-ai
Repositorybkit-claude-code
Skill namecontrol
Stars
601
Forks
154
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by ww-w-ai on GitHub. Read the source before you install it.

Installation

Install the Control AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/ww-w-ai/bkit-claude-code.git /tmp/bkit-claude-code
mkdir -p .claude/skills
cp -r /tmp/bkit-claude-code/skills/control .claude/skills/control
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Control in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Control on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Control is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Control Skill

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

Arguments

ArgumentDescriptionExample
(none)Show current status (same as status)/control
statusShow automation level, trust score, guardrails/control status
level <0-4>Set automation level manually/control level 2
pausePause all automation (equivalent to L0)/control pause
resumeResume to previous automation level/control resume
trustShow trust score details and history/control trust

Automation Levels

LevelNameDescriptionApproval Gates
L0ManualAll actions require explicit user approvalEvery phase transition
L1GuidedSuggestions provided, user confirms each stepEvery phase transition
L2Semi-AutoRoutine transitions auto, key decisions gateddo->check, check->report, report->archive
L3AutoMost transitions auto, only destructive ops gatedreport->archive
L4Full-AutoFully automated PDCA cycle, minimal interventionInitial feature approval only

Action Details

status (Default)

Display the current automation control state.

  1. Read runtime control state from .bkit/runtime/control-state.json
  2. Read trust score from .bkit/state/trust-score.json
  3. Read active guardrails from lib/control/ configuration
  4. 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.

  1. Validate input is a number 0-4
  2. Read current level from .bkit/runtime/control-state.json
  3. If escalating (going higher), warn user about reduced oversight
  4. If de-escalating, apply immediately without confirmation
  5. Update .bkit/runtime/control-state.json with new level
  6. Write audit log entry via lib/audit/audit-logger.js
  7. 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:

LevelautomationLevelDescription
L0manualAll manual
L1guideGuided suggestions
L2semi-autoSemi-automatic (default)
L3autoMostly automatic
L4full-autoFully automatic

pause

Pause all automation immediately.

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

resume

Resume automation to the previous level before pause.

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

trust

Show trust score details and contributing factors.

  1. Read trust score from .bkit/state/trust-score.json
  2. 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)
  3. 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

FilePurpose
.bkit/runtime/control-state.jsonRuntime control state (level, paused, previousLevel)
.bkit/state/trust-score.jsonTrust score and contributing metrics

Module Dependencies

ModuleFunctionUsage
lib/control/automation-controller.jsgetLevel(), setLevel()Read/write automation level
lib/control/automation-controller.jspause(), resume()Pause/resume automation
lib/audit/audit-logger.jswriteAuditLog()Record control changes

Usage Examples

bash
# 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

Frequently asked questions

What does the Control AI skill do?

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

Why use Control on TypingMind?

Because you install it once and use it with any model. Control is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Control in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ww-w-ai/bkit-claude-code/tree/main/skills/control. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Control?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Control?

As many as you like. As long as a model supports skills, you can use Control with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Control AI skill free?

Yes. It is published on GitHub by ww-w-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇