Research Frontmatter
- 1 installs
- 21 repo stars
- Updated August 5, 2026
- joaquimscosta/arkhe-claude-plugins
Enforces a standard YAML frontmatter (title, version, status, created, last_updated) on research documents in docs/research/.
About
Ensures research files carry standard YAML frontmatter so GitHub renders metadata and readers can judge staleness. A developer uses it when creating, editing, or promoting research documents.
- Five required frontmatter fields
- Version-increment guidance for content maturity
Research Frontmatter by the numbers
- 1 all-time installs (skills.sh)
- Ranked #1,366 of 1,879 Documentation skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/joaquimscosta/arkhe-claude-plugins --skill research-frontmatterAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| repo stars | ★ 21 |
| Last updated | August 5, 2026 |
| Repository | joaquimscosta/arkhe-claude-plugins ↗ |
What it does
Enforces a standard YAML frontmatter (title, version, status, created, last_updated) on research documents in docs/research/.
Files
Research Frontmatter Standard
Ensure all research files in docs/research/ have standard YAML frontmatter so GitHub renders metadata as a table and readers can judge staleness.
Required Frontmatter
Every research file MUST have these 5 fields at the top of the YAML block:
---
title: "Human-readable title"
version: "1.0.0"
status: Published # Published | Draft | Living Document
created: YYYY-MM-DD
last_updated: YYYY-MM-DD
---Additional fields (slug, tags, aliases, promoted_at, last_refreshed, sources) MAY follow the standard fields.
Field Definitions
| Field | Required | Format | Description |
|---|---|---|---|
title | Yes | Quoted string | Human-readable document title |
version | Yes | Semver string | Content maturity version |
status | Yes | Enum | Published, Draft, or Living Document |
created | Yes | YYYY-MM-DD | Date first authored (from git or inline) |
last_updated | Yes | YYYY-MM-DD | Date of last substantive content change |
When to Increment Version
- Patch (1.0.0 -> 1.0.1): Typo fixes, formatting, minor clarifications
- Minor (1.0.0 -> 1.1.0): New sections added, examples updated
- Major (1.0.0 -> 2.0.0): Complete rewrite, fundamental scope change
README Index
The docs/research/README.md table MUST use these columns:
| Topic | Version | Status | Created | Last Updated |When adding a new entry, append a row matching this format.
Template
New research files should follow docs/research/TEMPLATE.md.
Validation Checklist
When triggered, verify: 1. File has YAML frontmatter (starts with ---) 2. All 5 required fields are present 3. status is one of the 3 allowed values 4. Dates use ISO 8601 format (YYYY-MM-DD) 5. Standard fields appear before any extra fields 6. README.md entry exists and columns match
Related skills
Lark MarkdownInstantly turn any markdown file into clean, formatted Lark/Figma-compatible documents without manual reformatting.488k
Lark DocCreate, read, update, summarize, rewrite and manage Feishu/Lark cloud documents directly from agent workflows.401k16.1kLark WikiCreate, organize, query, and manage documents, spaces, and members inside Lark (Feishu) knowledge bases directly from AI agent workflows.397k16.1k
Domain ModelingBuild and sharpen a project's domain model: pin down domain terminology in a glossary and record architectural decisions as ADRs.318k202k
Opensource Guide CoachGet expert, attribution-safe guidance on launching and sustaining an open-source project.270k71Readme I18nMaintain consistent, updatable language selector blocks across every README variant in a multilingual repository.270k71