skill-authoring

Create and audit Agent Skills with TDD validation and specification compliance.

1|1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/ntk148v/skills --skill skill-authoring-ntk148v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/ntk148v/skills/tree/main/skills/skill-authoring
Command: npx skills add https://github.com/ntk148v/skills --skill skill-authoring-ntk148v

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skill authoring ensures Agent Skills are built correctly the first time by requiring failing-test baselines and enforcing specification-compliant structure so skills are discoverable, efficient, and dependable.

Core Features & Use Cases

  • TDD-based skill lifecycle: Capture a baseline failure (RED), implement the minimal skill that makes it pass (GREEN), then refactor without breaking compliance (REFACTOR).
  • Specification compliance auditing: Validate required YAML frontmatter fields, enforce “Use when...” trigger-style descriptions, and require key sections like ## Overview and ## When to Use.
  • Duplicate detection & quality control: Identify redundant skills by name/purpose/overlap, and keep the best version while merging improvements and removing inferior duplicates.
  • Operational readiness checklist: Verify directory/name matching, efficiency (word-count guidance), and scenario pass/fail before deployment.

Quick Start

Ask an AI to audit your existing skill directory against SKILL.md frontmatter requirements, required sections, naming alignment, and duplicate risk, then propose the smallest compliant changes.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I validate Agent Skill spec compliance for YAML frontmatter and required sections?

To validate spec compliance, audit your skill directory to enforce required YAML frontmatter fields like name and description, verify trigger-style "Use when..." descriptions, and check for mandated documentation sections such as ## Overview and ## When to Use.

How do I use TDD to create a new Agent Skill?

Using TDD to create an Agent Skill involves capturing a baseline failure, implementing the minimal skill logic to pass the test, and refactoring the skill while maintaining strict specification compliance throughout the lifecycle.

What is the best way to detect duplicate Agent Skills in a library?

The best way to detect duplicate Agent Skills is auditing the library to identify redundant skills by name, purpose, and functional overlap, then merging improvements into the best version while removing inferior duplicates.

What documentation structure is required for Agent Skill discoverability?

Required documentation structure for discoverability includes mandatory YAML frontmatter fields, trigger-style "Use when..." descriptions, and essential sections like ## Overview and ## When to Use to ensure skills are efficient and dependable.

How do I check operational readiness before deploying an Agent Skill?

You check operational readiness by verifying directory and name matching, reviewing efficiency using word-count guidance, and validating scenario pass or fail results before deployment.

Why does my refactored Agent Skill fail specification auditing?

Your refactored skill may fail specification auditing if it violates strict compliance rules, such as missing required YAML frontmatter, lacking mandated documentation sections, or having directory names that no longer match the skill name.