lilmgenius/paperthin

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 th…

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/lilmgenius/paperthin --skill prism

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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.

Rules

  • Independent lenses, not roles. A "security reviewer" and a "senior security reviewer" are one lens, not two.
  • One reason per lens — the load-bearing one. A lens that returns a list is hedging.
  • Disagreement is the product. A prism that agrees on everything did not need to be run.
  • Never average. If two lenses split, the answer is the question that resolves the split, not the midpoint of their verdicts.
  • Draw the lenses fresh for the artifact in hand. A lens useful for a spec may be useless for a migration; don't carry lenses across artifacts.
  • Don't manufacture disagreement. A run that finds none returns the shared verdict and stops.
  • User-invoked on purpose: plural lenses are an opt-in spend, and their convergence must never masquerade as automatic proof, so this fires only when deliberately reached for.

Verification

The result reads as a picture, not a checklist — a reader sees which lenses agreed, which disagreed, and the one question that matters, and can act on it without re-running the prism. If they'd need to re-run it to know what to do next, step 5 was skipped.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
lilmgenius
커뮤니티

re0-order

Move items only, reword nothing; realign a listing whose order has gone arbitrary (a list, table, catalog, sections, an enum) into a logical sequence under one stated principle. Nothing is added or removed. Use when the user names a listing, or a scope holding one, whose order no longer helps a reader follow the set, or when a pipeline the user invoked passes that scope on. Acts only inside that scope.

1시간 설치 수
5
GitHub Stars
1.5천
업데이트
11월 15일
lilmgenius
커뮤니티

readback

Verify the model's understanding of a user's instruction before spending non-trivial work. Use when a request is long, bundled, high-stakes, hard to undo, or has ambiguous scope or referents such as this, that, it, the other one, whatever is cleaner, or whichever order makes sense. Restate internally, cross-check against available context, proceed silently when resolved, and surface only a genuine surviving fork.

1시간 설치 수
5
GitHub Stars
1.5천
업데이트
11월 15일
lilmgenius
커뮤니티

whychk

Right after you pick an option, have a fresh outsider find the sharpest gap in the choice, then explain that gap in your own words, one gap at a time.

1시간 설치 수
5
GitHub Stars
1.5천
업데이트
11월 15일
lilmgenius
커뮤니티

aim

When data lands with a thin ask (files, a repo, a paste, a chat scrollback), read it and propose what the user is trying to do with it for them to confirm. Use the moment material arrives without a fully-formed ask, or when the ask reads thinner than the data suggests.

1시간 설치 수
4
GitHub Stars
1.5천
업데이트
11월 15일