/add-frontmatter
Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
$ npx -y skills add markmdev/meridian --skill add-frontmatter --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/add-frontmatter
Context preview
The summary Claude sees to decide when to auto-load this skill.
Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
SKILL.md
add-frontmatter.SKILL.mdname: add-frontmatter
description: Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
Add Frontmatter
Scan every `.md` file in the project and ensure it has the required frontmatter so Reflex can discover and route it.
Required frontmatter format
---
summary: One-line description of what this file covers
read_when:
- keyword or phrase that signals this file is relevant
- another keyword
---
What to skip
- Files already having correct `summary` + `read_when` frontmatter — leave them alone
- Files that have frontmatter with any other keys (e.g. `name`, `description`, `title`) — do not replace or merge, leave them alone
- `node_modules/`, `.git/`, `dist/`, `build/`, `vendor/`, `__pycache__/`
- `.claude/` — agents, skills, commands, hooks all use their own frontmatter schemas
- Files that are purely generated output, changelogs, or boilerplate with no reusable knowledge (e.g. `CHANGELOG.md`, `LICENSE`)
Process
1. Glob all `.md` files, excluding skip dirs 2. For each file: check if frontmatter with `summary` and `read_when` already exists 3. If missing or incomplete: read the file content, infer a concise `summary` and 2-4 `read_when` keywords from the actual content 4. Prepend the frontmatter block (or insert after existing `---` if only partially present) 5. Write the updated file
Quality criteria
- `summary` is a single line, factual, specific — describes what the file actually covers
- `read_when` keywords match how someone would describe a task that needs this file (e.g. `"setting up auth"`, `"debugging routing"`, `"OpenClaw plugin"`)
- Don't invent knowledge not in the file — infer from actual content only
Read more
name: add-frontmatter description: Scan all .md files in the project and add or fix YAML frontmatter (summary + read_when) so they can be discovered by context routers like Reflex.
Add Frontmatter
Scan every `.md` file in the project and ensure it has the required frontmatter so Reflex can discover and route it.
Required frontmatter format
--- summary: One-line description of what this file covers read_when: - keyword or phrase that signals this file is relevant - another keyword ---
What to skip
- Files already having correct `summary` + `read_when` frontmatter — leave them alone
- Files that have frontmatter with any other keys (e.g. `name`, `description`, `title`) — do not replace or merge, leave them alone
- `node_modules/`, `.git/`, `dist/`, `build/`, `vendor/`, `__pycache__/`
- `.claude/` — agents, skills, commands, hooks all use their own frontmatter schemas
- Files that are purely generated output, changelogs, or boilerplate with no reusable knowledge (e.g. `CHANGELOG.md`, `LICENSE`)
Process
1. Glob all `.md` files, excluding skip dirs 2. For each file: check if frontmatter with `summary` and `read_when` already exists 3. If missing or incomplete: read the file content, infer a concise `summary` and 2-4 `read_when` keywords from the actual content 4. Prepend the frontmatter block (or insert after existing `---` if only partially present) 5. Write the updated file
Quality criteria
- `summary` is a single line, factual, specific — describes what the file actually covers
- `read_when` keywords match how someone would describe a task that needs this file (e.g. `"setting up auth"`, `"debugging routing"`, `"OpenClaw plugin"`)
- Don't invent knowledge not in the file — infer from actual content only
Meridian makes Claude Code more reliable on real projects. It adds persistent project context, smarter session handoff, and lightweight workflow enforcement so Claude is less likely to lose the plot halfway through a long task.
Other skills on meridian.
- /create-docs
Create or update .meridian/docs/ knowledge files for a module or directory. Produces reference docs with frontmatter for context routing.
Open skill - /error-audit
Audit code for silent error swallowing, fallbacks to degraded alternatives, backwards compatibility shims, and UI that fails to show errors to the user. Finds and fixes all occurrences in the specified scope.
Open skill - /observability-audit
Audit code for observability gaps — debug logs left in, errors caught without being logged, missing context on log entries, untracked slow operations. Uses the app's existing observability tooling exclusively.
Open skill - /planning
Interview-driven planning methodology that produces implementation-ready plans. Always use this skill INSTEAD of EnterPlanMode — it provides structured interviewing (20-40 clarifying questions), exhaustive parallel codebase exploration (5-15 Explore agents), verbatim
Open skill - /ux-states-audit
Audit UI code for missing loading states, empty states, and error states. Every async operation and data-driven UI must handle all three. Finds gaps and implements the missing states using the app's existing patterns.
Open skill