Agent skill
research-frontmatter
Enforce standard YAML frontmatter on research documents in docs/research/. Use when creating, editing, or promoting research files, when user mentions "research metadata", "research frontmatter", or "research staleness".
Install this agent skill to your Project
npx add-skill https://github.com/joaquimscosta/arkhe-claude-plugins/tree/main/.claude/skills/research-frontmatter
SKILL.md
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:
- File has YAML frontmatter (starts with
---) - All 5 required fields are present
statusis one of the 3 allowed values- Dates use ISO 8601 format (
YYYY-MM-DD) - Standard fields appear before any extra fields
- README.md entry exists and columns match
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
Skill Name
What this skill does. Use when user mentions "keyword1", "keyword2", or "keyword3". Keep under 1,024 characters and include specific trigger keywords.
plugin-release-checker
skill-validator
Validate skills against Anthropic best practices for frontmatter, structure, content, file organization, hooks, MCP, and security (62 rules in 8 categories). Use when creating new skills, updating existing skills, before publishing skills, reviewing skill quality, or when user mentions "validate skill", "check skill", "skill best practices", "skill review", or "lint skill".
sync-docs
Sync official Anthropic documentation and analyze impact on project components. Runs docs/reference/update-claude-docs.sh, computes diffs, and reports impacts on the skill validator, plugins, and project documentation. Use when user mentions "sync docs", "update reference docs", "refresh docs", or "check doc changes".
deep-research
Deep research on technical topics using EXA tools with intelligent two-tier caching. Use when user asks to research a topic, investigate best practices, look up information, find patterns, or explore architectures. Also invoked by /research command. Triggers: "research", "look up", "investigate", "deep dive", "find information about", "what are best practices for", "how do others implement".
workflow-orchestration
Coordinate structured thinking and multi-agent parallel execution for complex tasks. Use when tackling multi-step projects, planning parallel work, breaking down complex problems, coordinating specialist tasks, facing architectural decisions, or when user mentions "workflow", "orchestration", "multi-step", "coordinate", "parallel execution", "structured thinking", "break this down", "plan this out", "how should I approach", or needs help planning complex implementations.
Didn't find tool you were looking for?