SKILLEMALL.ai

CD component-extraction

Domain-neutral methodology for the third level of Adler-style reading - extracting structured components (terms, propositions, arguments, solutions) from a document section by section. Selects a reading strategy appropriate to document size and structure (section-based for documents under 50 pages with clear sections; windowing for long documents without breaks; targeted for hybrid content where only specific sections matter). Writes per-section extraction notes that downstream synthesis can consume. Reusable across any extraction workflow - skill creation from a methodology document, Pass-2 content grasp on a paper's full text, evidence-mining from a long-form report. Use when an agent has done structural analysis and now needs to extract the actual atomic content. Trigger keywords - component extraction, section-by-section extraction, extract terms, extract propositions, extract arguments, Adler Level 3, interpretive reading.

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

Domain-neutral methodology for the third level of Adler-style reading - extracting structured components (terms, propositions, arguments, solutions) from a…

As a process D 49/100 · Unfinished process — References files that are not bundled: ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md, ../research-claim-map/SKILL.md

ProcedureResearchAI and agentstype 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: ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md, ../research-claim-map/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: ../structural-analysis/SKILL.md
  • warning missing-ref reference to a missing file: ../synthesis-application/SKILL.md
  • warning missing-ref reference to a missing file: ../research-claim-map/SKILL.md
  • warning missing-ref reference to a missing file: ../paper-three-pass-extraction/SKILL.md

Process rating: all ten parameters 49/100

Will not run. References files that are not bundled: ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md, ../research-claim-map/SKILL.md
  • 0Tools and files. 4 referenced file(s) missing: ../structural-analysis/SKILL.md, ../synthesis-application/SKILL.md, ../research-claim-map/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
  • 30Running it twice. 1 mutating operations with no state check
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 27 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1774 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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 941: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 27 items
  • +3Output format is stated explicitly
  • +4Has examples (2 code blocks)

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