silent-execution

$npx mdskill add TheBushidoCollective/han/silent-execution

Batch tool calls and suppress narration to reduce token waste during sequential operations.

  • Helps minimize token consumption by avoiding unnecessary descriptions between related actions.
  • Integrates with any tools used in sequences like testing, linting, or type-checking.
  • Decides to batch operations when they are independent and not part of interactive debugging.
  • Presents results only after completing a batch or when unexpected issues arise.

SKILL.md

.github/skills/silent-executionView on GitHub ↗
---
name: silent-execution
user-invocable: false
description: Reduce token waste by batching tool calls and avoiding narration between sequential operations
allowed-tools: []
---

# Silent Execution

## Name
han-core:silent-execution

## Description

When executing a sequence of related tool calls (running tests, fixing lint, applying edits), batch operations and report results only when complete.

## The Pattern

**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)."

## Rules

1. **Batch independent operations** — if operations don't depend on each other, run them all before commenting
2. **No narration** — don't describe what you're about to do for each tool call
3. **Report results** — speak only when the batch is complete or something unexpected happens
4. **Exception: interactive debugging** — when the user is watching you debug, narration helps them follow along

## Token Savings

~50-100 tokens per batch cycle. Over a typical session with 20+ build cycles, this saves 1,000-2,000 tokens.

More from TheBushidoCollective/han

SkillDescription
absinthe-resolversUse when implementing GraphQL resolvers with Absinthe. Covers resolver patterns, dataloader integration, batching, and error handling.
absinthe-schemaUse when designing GraphQL schemas with Absinthe. Covers type definitions, interfaces, unions, enums, and schema organization patterns.
absinthe-subscriptionsUse when implementing real-time GraphQL subscriptions with Absinthe. Covers Phoenix channels, PubSub, and subscription patterns.
act-docker-setupUse when configuring Docker environments for act, selecting runner images, managing container resources, or troubleshooting Docker-related issues with local GitHub Actions testing.
act-local-testingUse when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
act-workflow-syntaxUse when creating or modifying GitHub Actions workflow files. Provides guidance on workflow syntax, triggers, jobs, steps, and expressions for creating valid GitHub Actions workflows that can be tested locally with act.
ameba-configurationUse when configuring Ameba rules and settings for Crystal projects including .ameba.yml setup, rule management, severity levels, and code quality enforcement.
ameba-custom-rulesUse when creating custom Ameba rules for Crystal code analysis including rule development, AST traversal, issue reporting, and rule testing.
ameba-integrationUse when integrating Ameba into development workflows including CI/CD pipelines, pre-commit hooks, GitHub Actions, and automated code review processes.
analyze-performanceAnalyze performance metrics and identify slow transactions in Sentry