Inspectional Reading
Domain-neutral methodology for the first level of Adler-style reading - systematic skimming to determine what kind of document this is, what it's about as a whole, and whether deeper engagement is worth the time investment. Read title, metadata, table of contents or section headings, abstract or introduction, conclusion, and end-material at a glance. Classify document type (methodology, framework, tool, theoretical, reference, or hybrid). Decide whether to escalate to deeper reading. Reusable across any artifact-from-document workflow - paper extraction, skill creation from a methodology docum
Install
/plugin marketplace add lyndonkl/claudeThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add lyndonkl/claude --skill inspectional-readinggit clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/inspectional-reading ~/.claude/skills/inspectional-readingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# inspectional-reading The first level of Adler's "How to Read a Book" methodology, applied as a reusable skill. Answers two questions before any deeper reading happens: **What kind of document is this?** and **Is it worth reading carefully?** The skill is invoked autonomously by an agent — it reads the document and produces structured output. It does not host a dialogue with the operator. ## Workflow ``` - [ ] Step 1: Read the metadata (title, authors, date, source, length) - [ ] Step 2: Read the abstract / introduction completely - [ ] Step 3: Examine table of contents or section headings - [ ] Step 4: Skim the conclusion and any end-material at a glance - [ ] Step 5: Classify the document type - [ ] Step 6: Assess worthiness for the calling agent's purpose - [ ] Step 7: Output structured findings ``` Time budget: 10-15 minutes for a typical paper / chapter / methodology document. If a document needs more, you've drifted into the next level of reading — stop and produce the inspectional output you have. ## Inputs The calling agent passes: - `source`: the document to read (path or URL or text) - `purpose_context`: a short string describing what this document is being read *for*. The classification and worthiness check both depend on this — reading a paper for synthesis vs reading a methodology document for skill extraction yield different worthiness criteria. Examples: - `purpose=paper_extraction_for_weekly_digest` — caller is paper-synthesizer's pipeline
Details
- Skill name
inspectional-reading- Repository
- lyndonkl/claude
- Path
skills/inspectional-reading/SKILL.md- Repo updated
- 1 September 2026
FAQ
What does the Inspectional Reading skill do?
Domain-neutral methodology for the first level of Adler-style reading - systematic skimming to determine what kind of document this is, what it's about as a whole, and whether deeper engagement is worth the time investment. Read title, metadata, table of contents or section headings, abstract or introduction, conclusion, and end-material at a glance. Classify document type (methodology, framework, tool, theoretical, reference, or hybrid). Decide whether to escalate to deeper reading. Reusable across any artifact-from-document workflow - paper extraction, skill creation from a methodology docum
How do I install the Inspectional Reading skill?
Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Inspectional Reading popular?
It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.
Related skills
Abstraction Concrete Examples
200lyndonkl/claude
Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
Academic Letter Architect
200lyndonkl/claude
Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
Adr Architecture
200lyndonkl/claude
Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
Kill Criteria Exit Ramps
200lyndonkl/claude
Establishes pre-defined, objective conditions for stopping projects and specific decision points for continue/pivot/kill evaluations. Guides through defining kill criteria, setting go/no-go gates, avoiding sunk cost fallacy, and executing disciplined stopping decisions. Use when defining stopping rules for projects, avoiding sunk cost fallacy, setting objective exit criteria, deciding whether to continue/pivot/kill initiatives, or when users mention kill criteria, exit ramps, stopping rules, go/no-go decisions, project termination, or sunk costs.
Glossary Alignment Check
200lyndonkl/claude
For each technical term in a substacker draft's claims, checks shared-context/glossary.md for a writer-specific definition and compares to field-standard. Emits a note for terms where the two diverge (aligned / diverged-safe / diverged-risky). Feeds into classify-claim (which definition governs) and write-review-artifact's Glossary Alignment section. Use on every claim. Trigger keywords — glossary alignment, term definition, writer vs field, load-bearing term.
Mlb Player Analyzer
200lyndonkl/claude
Deep-dive analysis of a single MLB player (hitter or pitcher) for the Yahoo Fantasy Baseball 2K25 league. Web-searches FanGraphs (ATC projections), Baseball Savant (xwOBA/xBA/xERA), MLB.com (lineups, probables), RotoWire (weather, injuries), and RotoBaller (closer depth) to produce the full set of structured player signals defined in the signal framework. Emits form_score, matchup_score, opportunity_score, daily_quality, regression_index, obp_contribution, sb_opportunity, role_certainty for hitters and qs_probability, k_ceiling, era_whip_risk, streamability_score, two_start_bonus, save_role_ce
Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.