writing-skills

Validate and standardize SKILL.md frontmatter and structure for skill directories.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hbvg234/jnmt.vn --skill writing-skills-hbvg234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/writing-skills
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill writing-skills-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent skill definitions make discovery and activation unreliable. This guide enforces a standard frontmatter shape, ensures trigger-phrase quality, and requires proper lockfile registration to improve consistency and safety.

Core Features & Use Cases

  • Enforces the required name and description frontmatter fields to align directory names with their identifiers.
  • Validates trigger phrases and ensures skills are ready for registration and automated testing.
  • Provides a formal template and a checklist to streamline skill creation and integration into the system.

Quick Start

Follow the standard template to create a new skill by placing a properly formatted SKILL.md at core/skills/<name>/ with a valid name and description frontmatter.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I validate SKILL.md frontmatter and trigger phrases for quality?

To validate SKILL.md frontmatter, you must enforce a standard metadata shape by checking required fields like name and description, and evaluating trigger-phrase quality in the description to ensure reliable skill activation and discoverability.

What sections are required in skill documentation to pass validation?

Required sections in skill documentation include explicit "When to use" and "What NOT to do" blocks, alongside valid name and description frontmatter, which collectively support automated indexing and safety checks.

Why does inconsistent skill metadata cause discovery and activation failures?

Inconsistent skill metadata causes discovery failures because automated indexing relies on a standardized frontmatter shape and proper lockfile registration to reliably parse directory names, trigger phrases, and toxicity safeguards.

How do I standardize YAML frontmatter for skill creation?

To standardize YAML frontmatter for skill creation, apply a formal template by placing a properly formatted SKILL.md at core/skills/<name>/ with aligned directory names, valid descriptions, and captured dependencies.

Can I use a checklist to streamline skill integration and lockfile registration?

Yes, you can use a formal template and validation checklist to streamline skill integration, ensuring your triggers pass quality checks and your metadata is fully ready for lockfile registration and automated testing.

What should I not do when defining skill triggers and metadata fields?

When defining skill triggers and metadata fields, you should not omit the "What NOT to do" section, use misaligned directory names, or neglect toxicity safeguards, as these inconsistencies break automated indexing and safety checks.