agentleFS
Soul-Brews-StudioSoul-Brews-Studio/arra-oracle-skills-cli/skills/oracle-prism/SKILL.md

oracle-prism

Skill121 starsChanged 7 months agoMITView on GitHub

Multi-perspective analysis — one agent transforms through 5 lenses (Archaeologist, Bug Hunter, Skeptic, Architect, Auditor) inline, no subagents. Use when user says "prism", "oracle-prism", "multi-perspective", "มองหลายมุม", "did we miss anything", "analyze from all angles", or before closing a session/migration/design decision. Presets: --preset retro/design/incident, --lenses N, --custom. Do NOT trigger for adversarial disproving (use /adversarial-analysis) or plain retrospectives (use /rrr).

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    Use --custom to define your own, or pick a preset:

    line 39

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

/oracle-prism — Multi-Perspective Analysis

"แสงเดียวผ่านปริซึม แตกเป็นหลายสี — เรื่องเดียวกัน มองจากหลายมุม เห็นต่างกัน"

One agent, five perspectives, no subagents. Transform inline — shift between lenses to dig through work, decisions, or problems from angles that a single viewpoint would miss.

Usage

/oracle-prism                        # Analyze current session (default)
/oracle-prism "the rename migration"  # Analyze a specific topic
/oracle-prism --lenses 3              # Use 3 lenses instead of 5
/oracle-prism --custom "Security Auditor,Performance Engineer,UX Designer"

How It Works

No subagents. The main agent transforms between perspectives sequentially, producing one section per lens. Each lens sees the same facts but asks different questions.

This is NOT adversarial analysis (which tries to disprove). This is prismatic analysis — same light, different colors.

Default 5 Lenses

#LensEmojiQuestion it asks
1Archaeologist🔍"What actually happened? Timeline, sequence, facts."
2Bug Hunter🐛"What problems did we hit? What's still broken?"
3Skeptic💀"What did we do wrong? What would we redo?"
4Architect🏗️"What changed structurally? What's the before/after?"
5Auditor📋"What's left undone? What's inconsistent?"

Alternate Lens Sets

Use --custom to define your own, or pick a preset:

--preset retro (session retrospective)

LensQuestion
HistorianWhat happened, in what order?
CriticWhat went poorly or slowly?
CheerleaderWhat went well? What should we repeat?
ConnectorWhat patterns connect to past work?
PlannerWhat's the next move?

--preset design (design review)

LensQuestion
UserIs this easy to use? What's confusing?
MaintainerIs this easy to change later?
BreakerHow can this fail? Edge cases?
SimplifierWhat can be removed?
IntegratorHow does this fit with everything else?

--preset incident (post-incident)

LensQuestion
FirefighterWhat happened and how was it fixed?
DetectiveWhat was the root cause chain?
DefenderWhat guards existed? Why didn't they catch it?
ForecasterWhat similar things could happen next?
BuilderWhat systemic fix prevents recurrence?

Output Format

## 🔍 Lens 1: Archaeologist — "What happened?"

[Timeline table or narrative]

---

## 🐛 Lens 2: Bug Hunter — "What broke?"

[Problems found, with evidence]

---

## 💀 Lens 3: Skeptic — "What went wrong?"

[Mistakes, with what should have been done]

---

## 🏗️ Lens 4: Architect — "What changed?"

[Before/after structural view]

---

## 📋 Lens 5: Auditor — "What's left?"

[Table of pending items with status and urgency]

---

**Cross-lens summary:** [2-3 sentences synthesizing what multiple lenses agree on]

Rules

  1. No subagents — all lenses run in the main agent, sequentially
  2. Each lens gets a section with its emoji, name, and guiding question as header
  3. Evidence required — cite files, commits, commands, timestamps. No vague claims
  4. Lenses disagree — if the Architect says "clean" but the Auditor says "incomplete", show both. Don't harmonize
  5. Cross-lens summary at the end — what do multiple lenses converge on?
  6. Tables over prose — use tables for timelines, status lists, before/after comparisons
  7. Session context by default — if no topic given, analyze the current session's work
  8. 3-7 lenses — minimum 3, maximum 7. Default 5. Use --lenses N to adjust

When to Use

SituationWhy prism helps
End of sessionCatch what you missed before closing
After a migration/renameFind inconsistencies across the change
Design decisionSee tradeoffs from user/maintainer/breaker angles
Post-incidentStructured multi-angle without blame
"Did we miss anything?"The Auditor lens exists for this

Relationship to Other Skills

SkillPatternAgents
/oracle-prismMulti-perspective, same agent0 (inline transform)
/adversarial-analysisTry to disprove a claim5 parallel subagents
/rrrSession retrospective0 (or 5 in --deep)
/roundtableDiscussion between personas0 (inline)

Prism is the lightest multi-perspective tool — no agents, no spawning, no coordination overhead. Use it when you want angles, not adversaries.

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.