markdown-editor

Generate and organize Markdown documents with standardized YAML frontmatter and directory structure.

1|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/jander99/skills --skill markdown-editor-jander99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdown-editor
Source: https://github.com/jander99/skills/tree/main/skills/markdown-editor
Command: npx skills add https://github.com/jander99/skills --skill markdown-editor-jander99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Markdown documentation often suffers from inconsistent frontmatter, scattered files, and vague naming, making updates and discovery hard. This skill provides a guided workflow to create, edit, and organize Markdown content with standardized frontmatter, descriptive filenames, and clear directory structure.

Core Features & Use Cases

  • Create and edit Markdown files with consistent YAML frontmatter (title, created, last_modified, author, type, tags).
  • Organize docs by type into directories (docs/research, docs/plans, etc.), generate descriptive kebab-case filenames, and ensure predictable structure.
  • Extract author from git config and automatically populate metadata; preserve created timestamp on edits and support updating last_modified.
  • Handle special files (README, TODO, CHANGELOG) without frontmatter where appropriate and maintain clean project-wide documentation.
  • Use cases include drafting README files for projects, capturing research notes, and maintaining ongoing documentation plans.

Quick Start

Ask me to create or update a Markdown document with frontmatter in the appropriate docs folder.

Frequently Asked Questions about markdown-editor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add YAML frontmatter to Markdown documentation automatically?

To add YAML frontmatter to Markdown documentation automatically, this skill generates standardized metadata fields like title, created, last_modified, author, type, and tags. It extracts the author from your git config and applies ISO 8601 timestamps to ensure consistent project docs.

What is the best way to organize project READMEs and research notes in directories?

The best way to organize project READMEs and research notes is by grouping files into structured directories like docs/research or docs/plans. This approach uses descriptive kebab-case filenames and standardized frontmatter to ensure predictable structure and easy content discovery.

Can I update existing Markdown files without changing the original creation timestamp?

Yes, you can update existing Markdown files without changing the original creation timestamp. The workflow preserves the created timestamp during edits while automatically updating the last_modified field, ensuring your documentation metadata remains accurate over time.

How do I manage special files like CHANGELOG or TODO without adding frontmatter?

To manage special files like CHANGELOG or TODO without frontmatter, the workflow recognizes these specific project files and excludes YAML metadata generation where appropriate. This maintains clean project-wide documentation while enforcing standards on standard notes and plans.

Does this Markdown documentation workflow require any external dependencies?

No, this Markdown documentation workflow does not require any external dependencies or components to function. It operates independently to enforce YAML frontmatter standards, extract git config metadata, and organize directory structures.