Individual skill
prism
Split one artifact — a claim, plan, or file — across 2 to 5 independent lenses, one per genuinely distinct failure mode (correctness, security, readability, cost, adversarial-user), and return their convergence: where they agree, where they disagree, and the single next question that resolves the disagreement. Use when one reviewer isn't enough because the failure modes are heterogeneous, or a claim looks strong to its author and needs cross-lens pressure before it ships.
skills/mesh/prism/SKILL.md
Source commit 0b1e2c65231b3ce9294844362efae9b3a726e3ed
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,377
- Repository last updated
- Nov 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,110 bytes
Read excerpt
Split one artifact across independent lenses and return where they converge and where they don't.
## Goal
The result is a picture of where the lenses agree, where they disagree, and the smallest question that would resolve the disagreement. Not a checklist, and never an average — averaging the lenses is the failure this skill exists to prevent.
## Workflow
1. Read the artifact end to end before choosing the lenses.
2. Choose one lens per genuinely distinct failure mode — correctness, security, readability, cost, adversarial-user, and the like. Two candidate lenses that share a failure mode are one lens, not two. In practice this lands between **2 and 5**: below 2 there is nothing to converge, and past 5 you are almost always padding with lenses that overlap. There is no default count — the artifact's distinct failure modes set it.
3. Through each lens, produce a one-line verdict — pass, fail, or unclear — with its single most load-bearing reason. No hedging list; if a reason isn't load-bearing, drop it.
4. Compare the verdicts and group them: full agreement, agreement for different reasons, disagreement.
5. Where there is disagreement, name the single next question whose answer would move it into agreement or a clean split with owners. That question is the output, not the individual verdicts.
6. Where every lens agrees, return the shared verdict with the reasons that were load-bearing for at least two lenses.