ask-read-lens

star 1

Read a source (or a small set) through a named lens at the desk — a theoretical frame, a methods checklist, a rival hypothesis — and report what the lens makes visible and what it occludes. A structured re-reading of what the vault holds, not new research; read-only, with any resulting work delegated. Use when the PI says 'read this as a <lens> person would' or wants the same material seen from a different angle.

eranroseman By eranroseman schedule Updated 6/11/2026

name: ask-read-lens description: "Read a source (or a small set) through a named lens in the Co-PI pane — a theoretical frame, a methods checklist, a rival hypothesis — and report what the lens makes visible and what it occludes. A structured re-reading of what the vault holds, not new research; read-only, with any resulting work delegated. Use when the PI says 'read this as a person would' or wants the same material seen from a different angle." version: 1.0.0 author: Memoria license: MIT platforms: [linux, macos, windows] metadata: hermes: tags: [Reading, Lenses, Framing] related_skills: [obsidian, qmd] memoria: skill_id: "ask-read-lens" profile: memoria-copi lane: ask mcp_tools: - obsidian.get_file_contents - obsidian.list_files - obsidian.search - patterns.patterns_list - patterns.patterns_run write_scope: [] outputs: []


ask-read-lens

The same material, different eyes. A lens is an explicit reading frame — a theory (behavior-change technique taxonomy), a posture (hostile reviewer 2), a discipline (health economist), a rival hypothesis — applied to material the vault already holds. The value is disciplined perspective-taking with the seams showing: what this lens highlights, what it occludes, and where it strains.

Inputs

Input Required Meaning
material yes The source(s)/claims/draft to re-read (vault paths or citekeys).
lens yes The frame, named explicitly — vague vibes ("read it critically") get sharpened into a named lens first, with the PI.

Procedure

  1. Pin the lens. State, before reading, what the lens attends to and what it discounts — three or four commitments, agreed with the PI. A lens that can highlight anything explains nothing.
  2. Check the pattern library: patterns_list() — if a lifecycle: current pattern encodes this lens, run the reading through patterns_run (the audited chokepoint, ADR-53) rather than improvising a private variant.
  3. Read the material (vault reads; extract text stays untrusted input) and report in the lens's own terms: what it foregrounds (quoted, with locators), what it renders invisible, where the material resists the lens (the strain points — usually the most interesting output).
  4. Close the loop honestly: one paragraph stepping out of the lens — what the lens-reading adds beyond the plain reading, if anything.
  5. Delegate anything the reading should become (a stub, a tension card, a draft note) via route-task — this skill writes nothing.

Output contract

Conversation only. The reading is structured: lens commitments → foregrounded (with evidence) → occluded → strain points → step-out paragraph. The PI can adopt, discard, or ask for a rival lens on the same material.

Honesty rules

  • The lens is performed, not endorsed: conclusions inside the reading are the lens's, flagged as such — never silently merged into your own assessment.
  • What the lens occludes is mandatory output, not a footnote; a lens-reading that only adds insight and costs nothing is being oversold.
  • Strain points are reported even when they undercut the lens the PI likes.
  • One lens at a time; comparing lenses is explore-framings' job.
Install via CLI
npx skills add https://github.com/eranroseman/memoria-vault --skill ask-read-lens
Repository Details
star Stars 1
call_split Forks 0
navigation Branch main
article Path SKILL.md
More from Creator