geronimo-iia/llm-wiki-skills/frontmatter

Frontmatter Reference

Background knowledge for writing correct frontmatter in wiki pages. This skill is loaded automatically when writing wiki pages.

For type system management (listing, adding, removing types), see the schema skill. For the full type taxonomy, see references/type-taxonomy.md.

Quick template

Get the exact frontmatter scaffold for any type:

wiki_schema(action: "show", type: "<type>", template: true)

Required fields

Every wiki page must have:

Additional required fields depend on the type:

Field conventions

title

Do not include the page type in the title ("Paper: Switch Transformer" ✗).

summary vs tldr

• summary describes scope ("what is this page about?")
• tldr states the conclusion ("what's the bottom line?")

read_when

Write as situations, not keywords:

read_when:
  - "Reasoning about MoE architecture tradeoffs"
  - "Comparing sparse vs dense model scaling"

Not: ["MoE", "scaling", "routing"] — that's what tags is for.

tags

Flat list, lowercase, hyphenated:

tags: [mixture-of-experts, scaling, transformers]

aliases

Alternative names and synonyms for this concept — keyword-indexed, so synonym queries in wiki_search hit this field directly:

aliases: [Mixture-of-Experts, MoE, sparse routing]

Use for acronyms, prior names, and common informal variants. Lowercase preferred but not required — BM25 keyword matching is exact on FAST fields.

sources

Slugs of source pages that actually contributed claims:

sources: [sources/switch-transformer-2021]

concepts

Slugs of concept pages this page directly discusses or depends on:

concepts: [concepts/scaling-laws]

Apply the backlink quality test: would a reader benefit from navigating there?

confidence

A float 0.0–1.0 on both page and claim objects. Same scale everywhere.

Default to 0.5 when unsure. Omit on claim objects when no certainty signal was recorded (absence is distinct from 0.5 neutral).

claims

Structured claims extracted from sources:

claims:
  - text: "Sparse MoE reduces effective compute 8x"
    confidence: 0.9
    source: sources/switch-transformer-2021
    section: "Results"

owner

Who is responsible — a person, team, or agent session ID.

superseded_by

Slug of the page that replaces this one. Use when a page is effectively replaced, not for minor updates. Creates a superseded-by graph edge.

Graph edges from frontmatter fields

Certain frontmatter fields create typed graph edges at ingest:

Body [[wiki-links]] get a generic links-to relation.

Field aliasing

Skill pages use different field names. The engine aliases them at ingest time so they index uniformly:

Aliases affect indexing only — files on disk are never rewritten.

Accumulation contract

When updating a page:

1. Read the current page first — wiki_content_read
2. Preserve existing list values — do not drop tags, read_when,

sources, concepts, or claims

1. Add new values to lists, do not replace them
2. Update scalar fields only with clear reason
3. Write the complete file, then wiki_ingest

Common mistakes