agentleFS
LilMGeniusLilMGenius/paperthin/skills/depth/crossthink/SKILL.md

crossthink

Skill1.4k starsChanged todayMITView on GitHub

When every option on the table is a variation of one route or waits on the same sign-in, approval, person or dependency, list the options that frame already gives, then map working mechanisms from five or more distant domains onto the problem and report the ones the first list lacked, each with where it breaks. Use when work is stuck inside one frame, when the user asks how another field or industry would solve it, or asks for an analogy that actually transfers. Not for re-reading a decision at a larger scale (macrothink), listing options when no single frame is stuck, or checking claims (factchk).

Trending

Less talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 5 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the LilMGenius/paperthin repository that our weekly crawl found: only 10 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Who's talking about LilMGenius/paperthin

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

See all 10

Talked about on GitHub (10 times).

On GitHub · 10

5 more on GitHub

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    List the frame's own options first: Write the distinct mechanisms the problem already yields directly, one line each: how it works here and …

    line 17
  2. Very specific:

    Never invent a fact about a source domain.

    line 30
  3. Distinctive:

    Read-only and advisory: it proposes options and changes nothing, and choosing among them stays with the main work.

    line 32
  4. Distinctive:

    No reported mechanism is already on the step 2 list, and rows sharing one operation were folded.

    line 40
  5. Distinctive:

    Every rejected row, the already-direct ones included, is listed with its reason.

    line 41

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

List what the problem's own frame already offers, then borrow working mechanisms from distant domains and keep only the ones that list lacked.

Goal

A problem stuck in one frame keeps producing variations of one route. A mechanism that already works in another domain can open a route the frame hides, but only when the transfer is operational: the source mechanism is real, the target mapping says who or what does which step here, and the breaks-where names the condition in this setting under which it fails. The run returns the new mechanisms with their breaks-where, or says honestly that the mapping found none.

The mapping does not replace direct generation. On the problems it was tried on, direct generation found more usable mechanisms, and the mapping still found ones direct generation missed, most of them about keeping the work safe while the blocker stands (reconciliation, staging against a stand-in, escalation, findings kept as text).

Workflow

  1. State the problem and its frame. Write the goal, the hard constraints, the stated unknowns and the frame that narrows the options now: the route every current option takes and the step it waits on, if any. Keep the problem's facts; drop the session's preferred answer.
  2. List the frame's own options first. Write the distinct mechanisms the problem already yields directly, one line each: how it works here and what it needs. This list is the baseline the mapping is judged against, so write it before choosing any domain.
  3. Map distant domains until five rows are accepted. Pick domains far from the problem's field (logistics, biology, law, finance, film, games, hardware, cognitive science, real estate, or others). For each, fill three cells:
    • source mechanism: an operation or causal process that actually works in that domain, stated as what happens, not as a slogan;
    • target mapping: the concrete option it yields here, saying who or what performs which step and what it requires;
    • breaks-where: the specific condition in this setting under which the transfer fails, and how to handle it when it can be handled. "May not work" or a cost alone is not a condition.
  4. Reject what does not transfer. A row with an empty cell, a mapping that only renames words with no operation behind it, and a source mechanism you cannot state as a working operation (reject it as unverified; this pass does not check sources) go to a rejected list with the reason.
  5. Fold and subtract. Fold rows that share one working operation into one mechanism; a different domain, vendor, tool, parameter or wording does not make a new one. Move every mechanism already on the step 2 list to the rejected list with the reason already direct: <its step 2 line>. What remains is the result.
  6. Report. Lead with the new mechanisms, each with its domain, target mapping and breaks-where: first those that remove the blocker, then those that limit its damage while it stands. Name the cheapest observation that would confirm or break the first one. Close with the rejected list. Zero new mechanisms is a valid result: say so and keep the step 2 list as the answer.

Rules

  • Direct options are written first and never replaced by the mapping; the mapping is judged only by what it adds.
  • A rejected row is kept with its reason, never deleted.
  • Never invent a fact about a source domain. Checking a claim against sources belongs to factchk.
  • Re-reading the same decision at a larger scale, purpose or horizon is a vertical read and belongs to macrothink; this skill reads sideways, across domains.
  • Read-only and advisory: it proposes options and changes nothing, and choosing among them stays with the main work.

Verification

Before finishing, confirm:

  1. The frame and the step 2 list were written before any domain was mapped.
  2. At least five rows were accepted. Each has a source mechanism, a target mapping and a concrete breaks-where.
  3. No reported mechanism is already on the step 2 list, and rows sharing one operation were folded.
  4. Every rejected row, the already-direct ones included, is listed with its reason.
  5. The report names one next observation, or states that the mapping added nothing.

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.