AI Skill Report Card

Preferring Terminal Over Memory

A-83·Nov 15, 2026·Source: Web

Terminal first, memory second. If a value can be obtained or verified by running a command, run the command — never answer from internal knowledge alone when a deterministic source exists.

14 / 15

Before answering, ask: "Can a terminal command produce or verify this value?"

  • Yes → run it, use its output as the answer.
  • No (pure reasoning, opinion, creative writing, no tool available) → use internal knowledge.
# Example: "What day of the week is it?"
date +%A

# Example: "What's today's date?"
date +%F

# Example: "Sum these numbers: 1234 + 5678 + 910"
echo $((1234 + 5678 + 910))

# Example: "How many lines in this file?"
wc -l file.txt

Never guess a date, compute arithmetic mentally, or recall file contents from memory if a shell command can answer it directly.

Recommendation▾
Add an edge case for ambiguous queries where terminal output could conflict with context (e.g., user-stated 'today' vs system clock in sandboxed environments)
14 / 15

Progress:

  • Step 1: Classify the question — is it terminal-answerable (time, date, math, file/system/env state, counts, text processing)?
  • Step 2: If yes, write the minimal correct command.
  • Step 3: Execute the command.
  • Step 4: Use the raw output as the factual basis of the answer (don't "correct" it with memory).
  • Step 5: Only if the command fails or no command exists, fall back to internal knowledge and say so explicitly.
Recommendation▾
Include an example showing a command failure and the required explicit fallback disclosure, not just describe it in Best Practices
16 / 20

Example 1: Input: "What day of the week is December 25, 2025?" Output: Run date -d 2025-12-25 +%A → output "Thursday" → answer: "Thursday."

Example 2: Input: "Calculate 15% tip on $84.50" Output: Run python3 -c "print(84.50*0.15)" → output "12.675" → answer: "$12.68 (rounded)."

Example 3: Input: "What's the capital of France?" Output: No terminal command gives a canonical answer better than memory → answer directly from internal knowledge: "Paris."

Example 4: Input: "How many days between 2024-01-01 and 2025-06-15?" Output: Run python3 -c "from datetime import date; print((date(2025,6,15)-date(2024,1,1)).days)" → use exact output, don't estimate manually.

Recommendation▾
Description is slightly long; could be tightened to lead with the core trigger condition more crisply
  • Default to the terminal for: dates, times, timezones, weekdays, arithmetic, unit conversions, counting, sorting, file/directory state, environment variables, process/system info, random number generation.
  • Prefer date, python3 -c, awk, bc, wc, find, grep for quick deterministic computation.
  • Show the command you ran (or at least rely on its exact output) rather than paraphrasing a remembered value.
  • If multiple steps are needed, chain commands or write a short script rather than computing intermediate steps mentally.
  • When the terminal is unavailable, state clearly that the answer is from memory and may be approximate/outdated.
  • Don't answer "what's today's date" or "what day is it" from training data — it's always wrong/stale.
  • Don't do mental arithmetic for sums, percentages, or conversions when bc/python3 is available — rounding/calculation errors creep in.
  • Don't skip verification just because you're "confident" — confidence isn't correctness for computable facts.
  • Don't silently fall back to memory after a command fails — mention the failure and say the answer is a best-effort guess.
  • Don't overuse the terminal for subjective, creative, or general-knowledge questions where no command adds value.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
14/15
Examples
16/20
Completeness
16/20
Format
13/15
Conciseness
14/15