agentleFS
q2522879285-sourceq2522879285-source/red-monkey-reasoning-kit/skills/expert-perspective-panel/SKILL.md

expert-perspective-panel

Skill2 starsChanged 2 months agoMITView on GitHub

Synthesize a complex problem through three genuinely complementary professional lenses in one response. Use when the outcome depends on distinct disciplines or stakeholder systems and no single lens covers the risks. Skip simple expert questions, requests for real named-person opinions, two-sided disputes better handled by bidirectional steelman, screenplay roundtables, and tasks needing actual independent agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when a systemic problem genuinely spans distinct disciplines, stakeholder systems, or failure modes and the user needs synthesis rather …

    line 12
  2. Distinctive:

    Never impersonate or fabricate the opinion of a real person.

    line 26
  3. Distinctive:

    Do not spawn agents merely because three perspectives are requested.

    line 27
  4. Very specific:

    Use $fact-claim-audit for shared external facts.

    line 28
  5. Very specific:

    Add $bidirectional-steelman only when the synthesized plan still contains one material conclusion-flipping choice.

    line 29

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

Complementary Perspective Panel

Own a single-response reasoning structure built from three complementary method lenses. It is not a claim that real experts were consulted and is not an execution topology.

Route

Use when a systemic problem genuinely spans distinct disciplines, stakeholder systems, or failure modes and the user needs synthesis rather than one expert answer. Select three lenses that change what is noticed, not three titles that repeat the same viewpoint.

Skip simple domain questions, ordinary brainstorming, requests for an actual named expert’s view, or a single pro/con dispute that $bidirectional-steelman can own. Route screenplay diagnosis to $script-doctor-roundtable. Use $agent-harness-review-loop only when real multi-agent execution is separately authorized.

Procedure

  1. Restate the problem, known facts, goal, constraints, and unresolved decision.
  2. Choose three complementary lenses and state why each is necessary.
  3. For each lens, provide: its reframing, recommended route, risk the other lenses may miss, and evidence that would change its view.
  4. Cross-question the lenses to find shared facts, genuine branch points, and the different assumptions behind disagreement.
  5. Synthesize a recommendation, applicability conditions, largest risk, exit condition, and first action.

Handoffs and Boundaries

  • Never impersonate or fabricate the opinion of a real person.
  • Do not spawn agents merely because three perspectives are requested; multiple agents and majority voting are not evidence.
  • Use $fact-claim-audit for shared external facts.
  • Add $bidirectional-steelman only when the synthesized plan still contains one material conclusion-flipping choice.

Completion Gate

The three lenses are materially different, each contributes a unique risk or constraint, disagreements trace to explicit assumptions, and the final synthesis includes conditions, risk, exit rule, and first step.

Source Status

Distilled from the user-supplied “专家会诊” method card. The card proposes a multi-perspective prompt; it does not document real expert involvement or 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.