agentleFS
Sign inStart free
nuttakulsvnuttakulsv/think-like/skills/hopper/SKILL.md

hopper

Skill2 starsChanged 41 days agoMITView on GitHub

Grace Hopper's way of moving people and organizations: make abstract costs physical and visible (like her 11.8-inch "nanosecond" wires), build a working demo instead of arguing, and make technology usable by people who aren't specialists. Use when you need to convince stakeholders, explain a technical cost or risk to non-engineers, justify a refactor or performance work, write a proposal, or challenge a process kept only out of habit. Triggers: "think like Grace Hopper", "explain to management", "convince the team", "make it concrete", "demo it", "คิดแบบเกรซ ฮอปเปอร์", "อธิบายให้ผู้บริหารเข้าใจ", "โน้มน้าวทีม".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. satsilem/claude-skills-pantheon★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository25 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Show, don't argue: If people doubt something is possible or worth it, build the smallest working demo, prototype, or before/after …

    line 35
  2. Distinctive:

    Lower the barrier for users: Ask who else could use this if it were easier: plain-language interfaces, defaults that work, error messages a …

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Think like Hopper

Computer pioneer and U.S. Navy rear admiral. Her team built A-0, one of the first compilers, and Flow-Matic, the first language with English-like commands, which shaped COBOL. She was famous for handing out pieces of wire about 30 cm (11.8 in) long: the distance electricity travels in a nanosecond, so people could hold a delay in their hands.

When to use

  • A technical cost or risk must be explained to managers, product, or customers
  • A proposal for a refactor, migration, or performance project
  • People are debating whether something is possible
  • A rule or process exists "because we've always done it"

Method

  1. Find the decision the audience has to make and what they care about (money, time, customers, risk). Speak to that, not to the technology.
  2. Make the cost physical. Translate the abstract into something people can picture or count: hours of staff time per month, baht per year, customers lost per day, seconds a user waits, the length of a queue on screen.
  3. Show, don't argue. If people doubt something is possible or worth it, build the smallest working demo, prototype, or before/after measurement and show it.
  4. Lower the barrier for users. Ask who else could use this if it were easier: plain-language interfaces, defaults that work, error messages a non-engineer can act on.
  5. Question habits. For each step in the process being discussed, ask what problem it solves today. Keep it if there's an answer; propose removing it if there isn't.

Output

  • Audience and decision: who decides, what they care about
  • The cost, made concrete: one or two numbers or images anyone can grasp
  • Demo or evidence: what to show (or what you built), and the result
  • Ask: the specific decision requested, in one sentence
  • Short, plain language, no jargon. Write in the user's language.

Anti-patterns

  • Slides of architecture diagrams for a business decision
  • Arguing for weeks about something a one-day prototype could settle
  • Talking in milliseconds and CPU to people who think in customers and baht
  • Keeping a process nobody can explain

Example (illustration)

User: I need management to approve two sprints to fix our slow CI.

Audience and decision: engineering manager and product lead; they care about release dates.

The cost, made concrete: CI takes 38 minutes; 14 engineers wait for it about 5 times a day. That is roughly 44 engineer-hours a day, more than five full-time people doing nothing but waiting.

Demo or evidence: a branch where test sharding and dependency caching bring one pipeline to 11 minutes, with screenshots of both runs.

Ask: two sprints for the CI work, in exchange for getting back the equivalent of about five engineers' time from next month.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free