writing-skills

Create Skill Units with standardized SKILL.md frontmatter and Markdown instructions.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill writing-skills-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jfmyers9/agent/tree/main/skills/writing-skills
Command: npx skills add https://github.com/jfmyers9/agent --skill writing-skills-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps teams create new Skill Units with a mandatory SKILL.md frontmatter at the root, ensuring consistency and discoverability across the skill catalog.

Core Features & Use Cases

  • Enforces a standardized frontmatter (name, description, allowed-tools, argument-hint) for every Skill Unit.
  • Provides a reusable template and conventions for organizing a skill's directory structure.
  • Enables validation and easy onboarding of new skills by new contributors.

Quick Start

Create a new skill by following the template and placing it under skills/{skill-name}/.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a portable Agent Skill that can be easily cataloged and validated?

To create a portable Agent Skill, define a formal Skill Unit by placing a SKILL.md file with mandatory frontmatter at the skill's root directory. This ensures consistency and discoverability across the skill catalog.

What frontmatter fields are required in a SKILL.md file?

A SKILL.md file requires specific frontmatter fields including name, description, allowed-tools, and argument-hint. It also mandates a Markdown body containing actionable instructions for the skill.

How do I structure a skill directory for team onboarding and validation?

Structure a skill directory by following the provided template and placing your new skill under the skills/{skill-name}/ path. This enforces a standardized frontmatter and reusable conventions for easy onboarding.

When do I need to use a standardized frontmatter template for skills?

You need a standardized frontmatter template whenever teams require portable, standards-compliant skill definitions. This approach enforces consistency across the skill catalog and enables easy validation by new contributors.

Can I use custom markdown structures instead of a standard skill template?

Using custom markdown structures bypasses the mandatory SKILL.md frontmatter validation. Applying the standardized template ensures your skill definitions remain portable, cataloged, and compliant with team conventions.

Why does my skill definition fail validation during onboarding?

Skill definitions fail validation when the SKILL.md frontmatter is missing required fields like name, description, allowed-tools, or argument-hint. Ensure the root directory contains a properly structured Markdown body with actionable instructions.