agentleFS
aka-kikaaka-kika/akakika-skills/skills/session-rituals/spread/SKILL.md

spread

Skill11 starsChanged 3 months agoMITView on GitHub

Before improving anything, show the spread of what can concretely be done on this specific input — a short menu of 3-5 interventions from lightest to heaviest touch, then wait for the user to pick. Domain-agnostic; works on any material the user hands over. Trigger when the user says "spread", "show me my options", "what can you do with this", or asks to improve or fix something without specifying how. Do NOT trigger when the user has already named a specific fix — then just do the fix.

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    Read the input fully.

    line 17
  2. Distinctive:

    Stop. Ask which level the user wants.

    line 21
  3. Distinctive:

    Only list what you can actually complete with what's available.

    line 25
  4. Distinctive:

    If the honest spread is thin, say so.

    line 26
  5. Distinctive:

    Keep the whole output under one screen.

    line 27

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

Spread

Show the capability spread on one concrete input before doing any work. Do not pick one interpretation of "fix this" and run with it. Enumerate the real options on this exact material, scope each honestly, and let the user choose the level.

Hard rule: no input, no run

This skill operates on a specific thing the user provides. If triggered without one, ask what the thing is and wait. Never produce a generic capabilities list.

Procedure

  1. Read the input fully.
  2. List 3-5 interventions you can concretely perform on it — actual operations against actual parts of the material, not categories or generic advice.
  3. Order them lightest to heaviest touch.
  4. Give one line per item on scope and risk.
  5. Stop. Ask which level the user wants. Do zero work until they pick.

Constraints

  • Only list what you can actually complete with what's available. If an option needs something missing, mark it "needs: X" inline.
  • If the honest spread is thin, say so. Fewer real options beat padded ones.
  • Keep the whole output under one screen. No emojis, no headers inside the output.

After the pick

Execute only the chosen option at its stated scope. If mid-work that scope can't achieve the goal, stop and say so — offer to move up one level, don't just do 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.