hands-on-keyboard

Guides Claude to coach users through coding tasks instead of editing files directly.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/t-step/bindle-archive --skill hands-on-keyboard-t-step
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hands-on-keyboard
Source: https://github.com/t-step/bindle-archive/tree/main/skills/hands-on-keyboard
Command: npx skills add https://github.com/t-step/bindle-archive --skill hands-on-keyboard-t-step

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users want to learn, practice, or stay in control of their terminal and codebase, an AI assistant that silently edits files and runs commands undermines that goal. This Skill keeps the user hands-on by making the assistant act as navigator rather than driver. ## Core Features & Use Cases - Escalation modes: Four explicit levels from explain-only through command coaching, patch proposal, and delegated edit, so the assistant only drives when the user says so. - Default coaching loop: Orient, propose the smallest next step, hand the user the exact command to run, review results together, and checkpoint at decisions. - Scope discipline under delegation: Even when the user says "just fix it," changes stay small, verified with diffs and tests, and free of unrequested refactors. - Use Case: A developer practicing a new test framework says "walk me through this, I want to type the fix myself" — the assistant diagnoses the failing test, explains the cause, and hands over the exact command and one-line fix for the user to apply. ## Quick Start Tell the assistant "walk me through fixing this bug — don't edit anything, I want to run the commands and type the changes myself."

Frequently Asked Questions about hands-on-keyboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop Claude from editing files when I want to do it myself?▼

Invoke hands-on-keyboard behavior by saying you want to stay hands-on, for example "walk me through this" or "I want to type this myself." The assistant then explains, proposes commands for you to run, and only edits after explicit delegation.

How do I pair with Claude on a coding task without full delegation?▼

Use the skill's escalation modes: start at explain-only or command coaching, where Claude gives exact commands and waits for your results. You move up to patch proposals or delegated edits only when you explicitly ask.

What happens when I tell Claude to just fix it under this skill?▼

Explicit delegation moves the assistant to level 4, where it makes the edit and runs commands directly. The change still stays scoped to what was asked, with the diff and test output shown afterward — no silent refactoring or scope expansion.

When should I not use hands-on-keyboard mode?▼

Skip it for fully delegated tasks, low-stakes mechanical work like renames or formatting, urgent time-boxed fixes where speed matters more than practice, and pure read-only research, which it does not restrict.

Does hands-on-keyboard work with AI assistants other than Claude?▼

The SKILL.md file is the Claude Code-specific implementation, but it points to a provider-neutral contract in docs/hands-on-keyboard.md that other assistants can follow manually with the same navigator-not-driver behavior.