This skill is for agents that need to split a content file into two dependable parts: structured metadata and the real body content. gray-matter is a mature parser used across Markdown and static-site workflows, and it is a good fit when an agent has to inspect or transform files that begin with YAML front matter, or in some cases JSON, TOML, or other supported formats. The agent behavior here is concrete: open a file or string, extract the front matter into structured fields, preserve the main body without the metadata wrapper, and optionally write updated front matter back out after linting, migration, or normalization.

Invoke this skill when the job is things like migrating docs between systems, auditing missing metadata fields, generating reports from Markdown collections, or updating front matter keys in bulk before a build. It is especially useful when another downstream step needs clean separation between metadata and content instead of brittle regex scraping.

The scope boundary matters. This is not a CMS, not a site generator, and not a content strategy tool. It does not decide what your taxonomy should be, publish pages, build routes, or render a website. It only handles the bounded file-parsing step around front matter and content, which is exactly why it works as a reusable agent skill.

Common integration points include Markdown repos, docs automation, static-site pipelines, content QA jobs, migration scripts, and any agent flow that needs structured metadata before further transformation.