agentleFS
Yeachan-HeoYeachan-Heo/oh-my-claudecode/skills/in-your-own-words/SKILL.md

in-your-own-words

Skill41k starsChanged 7 days agoMITView on GitHub

Play back the goal, the problem, and the success check in your own words when a brief is genuinely ambiguous — vague, contested, or leaving real forks open — so misunderstanding is caught cheaply. Not for well-specified or routine tasks.

34 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about Yeachan-Heo/oh-my-claudecode

The biggest 5 of 81 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 81

Talked about on GitHub, YouTube, Bluesky and the web (81 times).

On GitHub · 50

45 more on GitHub

On YouTube · 20

15 more on YouTube

On Bluesky · 10

5 more on Bluesky

On the web · 1

Used with

Projects with it also use poteto-help, principle-explain-the-number and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 10 projects that use this

  • ianclearySkill

    principle-explain-the-number

    Apply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.

    Also in 20 projects that use this

  • jaydubya818Skill

    principle-test-behavior-not-implementation

    Apply when tests mirror internals instead of asserting observable outcomes.

    Also in 21 projects that use this

  • jaydubya818Skill

    principle-attack-the-premise

    Apply when repeated fixes fail and a shared assumption may be wrong.

    Also in 19 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 10 projects that use this

  • +2 more from jaydubya818

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    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:

    Before the first tool call on genuinely ambiguous work — a brief that is vague, contested, or leaves real forks open — say back what you …

    line 17

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “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

In Your Own Words

Before the first tool call on genuinely ambiguous work — a brief that is vague, contested, or leaves real forks open — say back what you understood — in your words, not the user's phrasing echoed. Misunderstanding caught now costs a sentence; caught after execution it costs the work. A well-specified brief needs no playback: start, and report what you did.

The playback

Three parts, plain language:

  1. The goal: what the user will have when this is done.
  2. The problem (if any): what stands in the way, as you understand it.
  3. The success check: how we will know it worked.

Then one line: "Right? Correct me where I drifted." — and stop for the answer on risky work; proceed-and-report on clearly reversible work (principles skill, Never block on the human).

Rules

  • Playback is a paraphrase, not a copy: if you can only repeat the brief, you have not understood it yet.
  • Name your assumptions inline ("I am assuming staging, not production").
  • Disagreement between your playback and the brief is the point — surface it, do not smooth it.

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.