read-frontmatter
Skill1 starsChanged 7 months agoApache-2.0View on GitHub
Read frontmatter (the whole object or one key) from a file. Types are preserved (numbers stay numbers, arrays stay arrays).
In this repository49 other files it gives its agents.
- AGENTS.mdAGENTS.md
- auto-modeSkill
- autoresearchSkill
- bind-workspaceSkill
- build-search-indexSkill
- canvasSkill
- conventionsSkill
- decision-consolidateSkill
- defuddleSkill
- discover-list-filesSkill
- discover-list-vaultsSkill
- force-new-port-startSkill
- hot-compactSkill
- lockSkill
- manage-deleteSkill
- manage-moveSkill
- meta-attach-vaultSkill
- meta-audit-bridge-readinessSkill
- meta-setupSkill
- meta-statusSkill
- meta-sync-templateSkill
- obsidian-basesSkill
- obsidian-markdownSkill
- read-getSkill
- read-searchSkill
- read-search-smartSkill
- saveSkill
- sync-from-githubSkill
- template-executeSkill
- unlockSkill
- who-is-speakingSkill
- wiki-boundarySkill
- wiki-exportSkill
- wiki-foldSkill
- wiki-graphSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-neighborsSkill
- wiki-pathSkill
- wiki-querySkill
- wiki-refresh-digestsSkill
- wikiSkill
- wiki-tourSkill
- write-appendSkill
- write-bundleSkill
- write-create-or-replaceSkill
- write-frontmatter-mergeSkill
- write-frontmatter-setSkill
- write-patchSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Call the obsidian-router get_frontmatter MCP tool with arguments parsed from $ARGUMENTS.
- Very specific: line 35
If a single key was requested: <key>: <value> with the type-preserved value (number stays number, boolean stays boolean, array shown as …
- Distinctive: line 36
If the whole frontmatter was returned: show it as a YAML-formatted code block.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
read-frontmatter
Call the obsidian-router get_frontmatter MCP tool with arguments parsed from $ARGUMENTS.
Arguments
Required:
path— file path relative to vault root.
Optional:
vault— vault name. Omit for default.key— specific frontmatter property to retrieve. Omit to get the whole frontmatter object.
Argument parsing from $ARGUMENTS
- bare path →
path, returns whole frontmatter <path> <key>→path+keypath=X key=Y vault=Z
Render the result
- If a single key was requested:
<key>: <value>with the type-preserved value (number stays number, boolean stays boolean, array shown as YAML list, etc.). Ifexists: false, say so explicitly. - If the whole frontmatter was returned: show it as a YAML-formatted code block.
Note: this tool reads via application/vnd.olrapi.note+json content negotiation, so values keep their type (numbers, booleans, arrays, nested objects) — they aren't all flattened to strings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

