agentleFS
Sign inStart free
richkuorichkuo/rk-skills/skills/tldr/SKILL.md

tldr

Skill50 starsChanged 6 days agoMITView on GitHub

Use when the user types /tldr to get a plain-simple-English summary, written in ASD-STE100, of the most recent response, aiming for under 30 words and never over 55.

40 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use explain, handoff and 2 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.
  • sunnyclinches44Skill

    explain

    Explains code using real-world analogies and ASCII diagrams

    Also in 3 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 6 projects that use this

  • Google CloudSkill

    triage

    Gather context on a change or bug and plan the implementation.

    Also in 3 projects that use this

  • GoogleSkill

    grill-me

    A relentless interview to sharpen a plan or design.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

TLDR

Produce a dead-simple recap of your most recent substantive response.

Rules

  1. Write it as a Plain simple English block in ASD-STE100 (Simplified Technical English) per the Response Style rules in CLAUDE.md/AGENTS.md. Aim for under 30 words. If 30 words would cut critical information (a caveat, a decision, or a required action), use more, up to a hard maximum of 55 words. No headers.
  2. Summarize the prior answer, not the original question. If there is no prior substantive response in the conversation, say so in one line and ask what to summarize.
  3. Keep critical caveats. Simplify the answer without dropping a caveat that changes what the reader should do.

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