Luebken Claude Plugins
luebken-claude-plugins is a Claude Code plugin for the Ship phase that validates Markdown frontmatter against schema definitions inside agent workflows.
Validate Markdown files and frontmatter against a schema before you merge docs or skill definitions.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install luebken-claude-plugins@luebken/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:luebken/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:luebken/claude-plugins").
What it does
luebken-claude-plugins is a compact Claude Code plugin set by Matthias Luebken aimed at builders who treat Markdown—with YAML frontmatter—as source of truth for skills, docs, and catalog entries. When you ship agent artifacts or public README bundles, small frontmatter typos break parsers, SEO fields, and downstream importers; this plugin gives Claude a explicit validate-against-schema workflow so you catch missing keys, wrong types, and invalid enums before merge. On Skillselion’s journey map it sits in Ship because the payoff is review and launch prep on files you already wrote, not greenfield coding. Solo operators maintaining SKILL.md trees or markdown-heavy repos get the most value: one consistent validation pass the agent can run on demand. It is narrower than a full docs site generator or linter suite—it focuses on definitional correctness of frontmatter. Combine it with your repo’s JSON Schema or team field list so the plugin’s answers stay deterministic.
Highlights
- Single-plugin collection from Matthias Luebken
- Validates Markdown frontmatter fields against defined schemas
- Catches structural errors in docs, skills, and repo metadata files
- Schema-driven checks instead of ad-hoc grep in agent chats
- Useful gate before publishing catalogs or shared agent instructions
Why builders use it
Docs and skill repos break silently when frontmatter drifts from the expected schema and nobody runs a structured check before merge.
After registration, Claude can flag invalid frontmatter and schema mismatches in Markdown files before you ship or publish.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is luebken-claude-plugins for?
It is for developers and catalog maintainers who author Markdown with frontmatter and want Claude Code to validate those files against schema rules.
When should I use luebken-claude-plugins?
Use it in Ship/review when you are about to merge docs, skills, or plugin manifests and need a quick schema pass on frontmatter fields.
How do I add luebken-claude-plugins to my agent?
Add the luebken/claude-plugins repository as a Claude Code plugin source and enable its plugin per the repo README, keeping your schema definitions available in the project.
Comments
Share how you use luebken-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.