Stats
Actions
Tags
From core
Batches sequential tool calls like tests, linting, and type-checking without intermediate narration. Reports results only on completion or errors to save 50-100 tokens per batch.
How this skill is triggered — by the user, by Claude, or both
Slash command
/core:silent-executionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
han-core:silent-execution
han-core:silent-execution
When executing a sequence of related tool calls (running tests, fixing lint, applying edits), batch operations and report results only when complete.
Anti-pattern (wasteful):
"Now I'll run the tests..." [runs tests] "Tests passed. Now I'll run the linter..." [runs linter] "Linting clean. Let me check types..."
Pattern (efficient):
[runs tests, linter, type-check] "All quality gates pass: tests (42 passed), lint (clean), types (no errors)."
~50-100 tokens per batch cycle. Over a typical session with 20+ build cycles, this saves 1,000-2,000 tokens.
npx claudepluginhub thebushidocollective/han --plugin coreAuto-loop execution workflow with quality gates. Use when starting any non-trivial implementation task. Provides automatic task decomposition, code implementation, testing (L1-L4), and iterative quality gates until completion. Invoke with /autoworker.
Orchestrates test, lint, and quality automation workflows with a decision guide for different change types. Useful for running suites, interpreting CI failures, and ensuring pre-merge confidence.
Orchestrates parallel agent teams for implementation, simplify/harden audits, and iterative fixes until code compiles cleanly, tests pass, and zero issues found. For multi-file features, hardening, or batch fixes.