Enforce Ghost documentation conventions across user-facing docs and CLI help text.
npx skills add https://github.com/mrtolkien/GHOST --skill docs-mrtolkien
Please help me install this Agent Skill. Skill: docs Source: https://github.com/mrtolkien/GHOST/tree/main/.agents/skills/docs Command: npx skills add https://github.com/mrtolkien/GHOST --skill docs-mrtolkien
Ensures consistent, high-quality Ghost documentation by enforcing standard conventions, file mappings, and terminology rules.
Read these conventions before creating or updating any docs page or CLI text.
High-intent search queries and answers about installing and using this skill.
To standardize Ghost documentation, you enforce consistent conventions by requiring frontmatter with name and description, applying terminology rules, and mapping change types to correct doc files to prevent drift across the site.
The required frontmatter fields for Ghost docs are name and description. Including these ensures user-facing documentation and CLI help text adhere to standard formatting guidelines and remain discoverable.
You map code changes to the correct Ghost CLI and configuration doc files by following established file mappings for change types, directing updates to core tools, CLI help text, configuration, and knowledge categories accurately.
Yes, Ghost documentation workflows require build verification steps before publishing. Running these checks alongside consistent formatting rules ensures user-facing docs and CLI text maintain high quality and prevent terminology drift.
Ghost docs develop inconsistent terminology when standard conventions are not enforced. Applying terminology rules and standardized formatting across user-facing docs and CLI help text prevents this drift and maintains quality.
Everyone-Needs-A-CopilotValidate and fix YAML frontmatter in Markdown documentation files.
sunny0826Generate POSIX-compliant CLI help text from raw command definitions.
Tobbe3108Automate static site deployment to GitHub Pages via gh-pages and CI/CD workflows.
AbeJitsuApply user-defined formatting standards across code, documentation, and content outputs using ESLint and Prettier.
