SKILLEMALL.ai

CD 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 document, literature triage, reading-list pruning. Use when an agent needs to convert "I have a document, what is it" into structured downstream-actionable input. Trigger keywords - inspectional reading, systematic skimming, document classification, Adler reading, skim before reading, skill-worthiness check, paper triage, reading triage.

lyndonkl/claude Agent Skills author: lyndonkl 1 file body ≈ 1 802 tokens Open the sourcegithub.com↗ analyzed 16 h ago

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…

As a process D 49/100 · Unfinished process — References files that are not bundled: ../paper-three-pass-extraction/SKILL.md, ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md

ProcedureResearchtype and topics are labelled automatically from the skill text
JSON
Technical rating
C
89/100
safety, quality, tests
Safety 60%
100
Quality 40%
72
Run on models
none yet
Process rating
D
49/100
Unfinished process
References files that are not bundled: ../paper-three-pass-extraction/SKILL.md, ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../paper-three-pass-extraction/SKILL.md
  • warning missing-ref reference to a missing file: ../structural-analysis/SKILL.md
  • warning missing-ref reference to a missing file: ../synthesis-application/SKILL.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../paper-three-pass-extraction/SKILL.md, ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md
  • 0Tools and files. 3 referenced file(s) missing: ../paper-three-pass-extraction/SKILL.md, ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 15 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1802 tokens
  • 100Running it twice. No mutating operations
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The skill ranks results itself: that belongs to the system behind the tool, not the model

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 934: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 11 headings
  • +3Step-by-step instructions: 15 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.