Skill Definition WF3 - Load Order
Source: c92 skill-definition — wireframe 3. Argument: show the definition the way the harness discloses it. Skills load progressively — name and description always, the body on trigger, the bundle on demand — so the page's spine is those three tiers, and the reach the skill gains at each one.
Always in context
~118 tokens · in every session on 12 installsThe only part of the skill the model sees before it triggers — the routing text. Verbatim, as the harness lists it.
On trigger
SKILL.md body · 314 lines · ~2140 tokensWhat enters the context when the skill fires — the instructions, and the controls the frontmatter sets on that moment.
This guide covers essential PDF processing operations using Python libraries and command-line tools. For advanced features, JavaScript libraries, and detailed examples, see REFERENCE.md. If you need to fill out a PDF form, read FORMS.md and follow its instructions.
from pypdf import PdfReader, PdfWriter
# Read a PDF
reader = PdfReader("document.pdf")
print(f"Pages: {len(reader.pages)}")
# Extract text
text = ""
for page in reader.pages:
text += page.extract_text()Merge PDFs
writer = PdfWriter()
for pdf_file in ["doc1.pdf", "doc2.pdf"]:
reader = PdfReader(pdf_file)
for page in reader.pages:
writer.add_page(page)
with open("merged.pdf", "wb") as output:
writer.write(output)Use scripts/extract_form_structure.py to dump the field tree before filling a form, and scripts/check_bounding_boxes.py to validate placement afterwards.
pdftotext -layout in.pdf out.txtkeeps column layoutqpdf --decrypt --password=… in.pdf out.pdfstrips owner encryptiongs -sDEVICE=pdfwrite -dPDFSETTINGS=/ebookcompresses for email
Run OCR (ocrmypdf --skip-text) first; the extraction recipes above only see the text layer.
On demand
5 referenced · 6 bundled only · ~11800 tokens if all readFiles the body points to, loaded only when the model follows the pointer — and the files it bundles without pointing to.
Reach
what triggering this skill lets the harness doStatic reads of the bundle, not runtime facts — the runtime side stays the honest zero until a harness emits skill calls.
Readout
The most literate option: it teaches a reader what the model can see at each moment, which is the question a governance person actually asks (“is this description in every session’s context? what runs when it triggers?”). Tier 1 is also the honest answer to “this is configured on 12 installs” — that text is in 12 fleets' prompts today. Costs a page that is longer and more didactic than the sibling detail pages; the tier labels may be better as captions inside WF1 than as sections.
Costs: everything WF1 needs, plus derived facts the inspector or qdash must compute: token estimates per tier, which bundle files the body references (a path grep), placeholder and load-time-shell detection in the body, and the invocation matrix decoded per harness (three spellings across Claude, Codex, Cursor, OpenClaw).