command-discipline

Included with Lifetime

$97 forever

Run shell commands bare — no decorative echo headers ("=== X ==="), no echo-then-cmd chains, no trailing "echo done". Use the Bash tool's description field for any narration. Triggers any time you're about to issue a Bash command.

General

What this skill does


# Command Discipline

When you run a shell command, run it directly. No decoration, no chained echos, no preamble.

## What to stop doing

```bash
# WRONG — decorative header before the real command
echo "=== running tests ===" && planemo test workflow.ga

# WRONG — narration-by-echo
echo "Checking workflow lint" && planemo workflow_lint --iwc .

# WRONG — trailing status echo
planemo test workflow.ga && echo "tests passed"

# WRONG — semicolon variant of the same
echo "=== before ===" ; ls test-data/
```

## What to do instead

```bash
# RIGHT — bare command, narration in the Bash tool's description field
planemo test workflow.ga
planemo workflow_lint --iwc .
ls test-data/
```

If you want the user to know what step you're running, put that text in the **Bash tool `description` parameter**. The user sees it in the tool-call panel. It does not need to be inside the shell command.

## Why

1. **The user already sees the command** — both in the tool-call panel and in the description field. The leading `echo "=== X ==="` is redundant noise that pushes the real command later in the line.
2. **It breaks permission-rule auto-approval.** Permission rules typically match commands by what the first segment starts with (`Bash(planemo workflow_lint *)`). When you prefix with `echo "..." && ...`, the first segment is the echo, which usually isn't covered by the same allow rule, so the user gets prompted unnecessarily.
3. **Trailing `&& echo done` adds nothing.** The Bash tool already reports exit code and the absence of an error message is itself the "done" signal.
4. **It looks like a tutorial blog post.** You're not writing shell tutorials; you're executing one command per tool call. Pretend the panel headings don't exist and just run the thing.

## Legitimate echo uses (do NOT avoid these)

These are real uses of `echo`, not decoration:

```bash
echo "$VAR"                       # printing a value
echo "$(date -u +%Y-%m-%d)"       # capturing a value
echo "line of data" >> log.txt    # generating content
echo "stdin payload" | python -   # piping data into a program
```

The rule blocks **echo-as-narration**, not echo-as-data-flow.

## Edge cases worth keeping

- `[ -f file ] && echo "exists"` — quick existence probe. Fine when the echo IS the result you wanted to see. Prefer `ls file 2>/dev/null; echo "rc=$?"` only if you actually need the rc.
- `cmd1 && cmd2` chains where neither cmd is echo — totally fine; the rule is specifically about echo decoration.

## When in doubt

Ask: "If I removed this echo, would the user lose any information they wouldn't already see?" If no, remove it.

Files: 1

Size: 2.9 KB

Complexity: 12/100

Category: General

Source: https://github.com/delphine-l/claude_global/tree/main/skills/claude-meta/command-discipline

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts