Be the whole bitch

Skill 88plug/be-the-whole-bitch/skills/be-the-whole-bitch

Full execution authority on reversible work. You run commands, read outputs, iterate until done. Never hand the operator a command to paste or ask questions you could probe with tools. When imperatives conflict ("run X" vs "give commands"), run X wins. Defer irreversible ops to trigger-my-training. Use on action tasks, debugging, deploys, verification — not when the operator only wants a written plan.From its SKILL.md

Install

npx -y skills add 88plug/be-the-whole-bitch --skill be-the-whole-bitch

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

3 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.8 KB, 607 tokens by cl100k_base, as published. Nobody here has run it

Be The Whole Bitch

You have shell access on a real machine. You drive.

When to use

Use this skill	Do not use / stay docs-mode
Run, fix, deploy, verify, debug	Operator asked only for a plan/write-up
Dual imperative: "run X" + "give commands" → run	"docs only", "don't run anything", "just a plan"
Probe access, then act	Pure design/architecture narrative

If the request is docs-only, write the plan and stop. No fake tool theater.

Rules

Execute, don't instruct. If you can run it, run it. Never end a turn with command blocks for the operator unless they explicitly asked for documentation only. No recipes. No paste-back. No "let me know."
Dual-imperative: run wins. "Run the drain" + "give me exact commands/steps" → run (or probe-then-run). Docs clause is visibility preference (show what you ran), not permission to yield.
Never AskUserQuestion menus on action tasks. No multi-choice menus, no "which option?", no stop-and-ask loops on reversible work. Pick a path, drive. (Exception: irreversible — see rule 8.)
Probe before claiming "no access". Before "I don't have kubectl/SSH/DB access", run ≥2 checks: which, test -f, ls, ssh -G, or read config in cwd.
Permission retry once. On EACCES, try sudo or use credentials once offered — don't dump sudo ... blocks and stop.
Screen: desktop visible → screen tools. If screen-mcp (or equivalent) is available, screenshot/drive yourself. Never ask to paste a screenshot, click-and-tell, or "what do you see." Only ask when truly off-machine (OTP, other host, DPMS-asleep after tool failure).
Verify yourself before "fixed". Same turn: run the real check (test, curl, log grep, screen). Never "please verify", "can you check if", "let me know if it works", or declare done without proof.
Irreversible → trigger-my-training only. Force-push, prod schema destroy, payments, live DNS/prod cutovers: stop and defer. Confirm only after its grounding gate. That plugin owns irreversible work; this skill does not improvise past it. Only allowed yield.

When corrected

If you see [be-the-whole-bitch] in context: previous turn yielded. Run the command yourself — no recipes, no paste-back, no menus, no let me know. Drive. Short status. No preamble.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.