writing-skills

Name: writing-skills
Availability: InStock
Author: jwmossmoz

Enforce Mozilla CI agent-skills house style for SKILL.md documentation.

3|Updated Jan 8, 2026

Search Tags:#documentation #markdown #frontmatter #references #gotchas #style-guide #skill-authoring

Ready to run

npx skills add https://github.com/jwmossmoz/agent-skills --skill writing-skills-jwmossmoz

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jwmossmoz/agent-skills/tree/main/skills/writing-skills
Command: npx skills add https://github.com/jwmossmoz/agent-skills --skill writing-skills-jwmossmoz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

House style for authoring and maintaining Mozilla CI agent-skills in this repo. It defines the expected structure and wording for SKILL.md, the description frontmatter, references/ and scripts/ as needed, reducing ambiguity and maintenance overhead.

Core Features & Use Cases

Enforces a consistent frontmatter schema (name, description, metadata) across skills.
Guides writers on structure, tone, and required sections to ensure predictable loading and discovery.
Helps teams review and edit SKILL.md, ensuring references/ and scripts/ exist when used.

Quick Start

Edit or create the SKILL.md in this directory following these house-style guidelines.

Frequently Asked Questions about writing-skills

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

FAQPage Schema

What is the required structure for SKILL.md documentation in Mozilla CI?▼

SKILL.md documentation requires specific sections including Prerequisites, Usage, Gotchas, and Related Skills, along with a frontmatter schema containing name, description, and metadata to ensure predictable loading and discovery.

How do I write frontmatter for a CI agent-skill?▼

Frontmatter for CI agent-skills must enforce a consistent schema with name, description, and metadata fields, reducing ambiguity and maintenance overhead across the repository.

What sections are mandatory when creating a new skill markdown file?▼

Creating a new skill markdown file requires mandatory sections: Prerequisites, Usage, Gotchas, and Related Skills, ensuring predictable loading and clear maintenance guidelines for contributors.

Can I include references and scripts directories in my skill documentation?▼

Yes, references and scripts directories are optional but supported components of skill authoring, and the house style guidelines help teams ensure these directories exist when referenced in SKILL.md.

How does a style guide help maintain agent-skills repositories?▼

A style guide maintains agent-skills repositories by defining expected structure and wording for SKILL.md files, frontmatter, and references, which reduces ambiguity and lowers maintenance overhead for teams.

When should I not use a standardized documentation format for agent-skills?▼

Standardized documentation formats for agent-skills should not be bypassed when working within this repository, as deviating from the house style increases ambiguity and breaks predictable loading and discovery mechanisms.