agentleFS
OpenGitCodeOpenGitCode/OpenShell/skills/summarize-pro/SKILL.md

summarize-pro

Skill0 starsChanged 7 months agoMITView on GitHub

Research and summarize information extremely concisely to avoid terminal clutter. Do NOT use Markdown formatting in the final response.

1 other project uses a version of this.

Adopted by

Most recently taken up by

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:

    MAXIMUM BREVITY: If you can say it in 10 words, don't use 20.

    line 17
  2. Distinctive:

    STRUCTURE: Use simple bullets (-) if needed, but avoid long paragraphs.

    line 18

≈ “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

Skill: Summarize Pro

This skill allows for researching topics and returning ultra-compact summaries.

Critical Rules

  1. DO NOT USE MARKDOWN: The response must be plain text. No bold, headers, or code blocks unless strictly necessary.
  2. MAXIMUM BREVITY: If you can say it in 10 words, don't use 20.
  3. STRUCTURE: Use simple bullets (-) if needed, but avoid long paragraphs.

Example Response

Topic: Mars Weather Response: Extreme cold, CO2 atmosphere, global dust storms, -60°C average.

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.