agentleFS
q2522879285-sourceq2522879285-source/red-monkey-reasoning-kit/skills/cross-domain-mechanism-transfer/SKILL.md

cross-domain-mechanism-transfer

Skill2 starsChanged 2 months agoMITView on GitHub

Transfer mechanisms from distant domains by mapping structural similarity, limits, and failure conditions, then design a reversible experiment. Use when the problem's bottom structure is clear but local solutions are exhausted or homogeneous, or the user explicitly asks for cross-domain mechanisms. Skip loose metaphors, undefined problems, direct mature solutions, and unverifiable historical anecdotes.

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:

    Use when the bottom contradiction and failure of ordinary local fixes are already clear, local candidates are exhausted or too similar, or …

    line 12
  2. Distinctive:

    Remove domain jargon and write the problem as a structure: actors, scarce resource, signal, incentive, bottleneck, feedback, or failure …

    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

Cross-Domain Mechanism Transfer

Own structural-isomorphism mapping, mechanism translation, transfer boundaries, and a reversible experiment. Do not own open-ended metaphor writing or the truth of external cases.

Route

Use when the bottom contradiction and failure of ordinary local fixes are already clear, local candidates are exhausted or too similar, or the user asks to borrow mechanisms from distant fields and test them.

Skip undefined problems, decorative analogies, direct mature solutions with adequate evidence, and requests that require inventing historical examples. Use $socratic-problem-framing or $first-principles-rebuild first when the structure is not stable.

Procedure

  1. Remove domain jargon and write the problem as a structure: actors, scarce resource, signal, incentive, bottleneck, feedback, or failure isolation.
  2. Define similarity axes before searching: variables that must match and surface details that may differ.
  3. Find cases from at least three meaningfully distant domains when breadth is requested; verify material facts rather than relying on folklore.
  4. For each case record the original problem, mechanism, structural mapping, transferable part, boundary, and failure condition.
  5. Select up to three mechanisms by structural match, transfer cost, reversibility, and risk—not by how memorable the analogy is.
  6. Translate the best mechanism into concrete actions, resources, expected signals, and side effects.
  7. Propose one low-cost reversible experiment with success metric, disconfirming signal, and exit condition.

Handoffs and Boundaries

  • $fact-claim-audit verifies external examples.
  • $bounded-explore-select may constrain search budget but does not own structural mapping.
  • $think-one-step-further remains a lightweight reuse check; this skill owns deliberate distant-domain mechanism search and experiment design.

Completion Gate

Each analogy is justified by mechanism rather than surface resemblance, transfer limits are explicit, and the experiment can falsify a key assumption without committing the full system.

Source Status

Distilled from the user-supplied “跨领域借解” method card. The card proposes a transfer pattern but supplies no verified cases or comparative outcome evidence.

<!-- integration-watermark: 红猴子整合 -->

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.