<skill-name-kebab-case>

Provide a frontmatter-driven Skill Unit template with optional resource directories.

41|9|Updated May 22, 2026
One-click install
npx skills add https://github.com/amoslee2026/Babel --skill skill-name-kebab-case
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: <skill-name-kebab-case>
Source: https://github.com/amoslee2026/Babel/tree/main/harness_engineering_training/templates/skill-skeleton
Command: npx skills add https://github.com/amoslee2026/Babel --skill skill-name-kebab-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skeleton provides a ready-to-fill Skill Unit template that enforces a consistent entry point and field structure, accelerating the creation of new skills.

Core Features & Use Cases

  • Provides a standard SKILL.md frontmatter with required name and description.
  • Supports optional resources directories (scripts/, references/, assets/) for on-demand loading.
  • Enables consistent discovery and activation workflows across Skill Units.

Quick Start

Use the harness-engineering-training skill skeleton to scaffold a new Skill Unit.

Frequently Asked Questions about <skill-name-kebab-case>

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

FAQPage Schema
How do I create a standardized Skill Unit template with consistent frontmatter?

To create a standardized Skill Unit template, use a skeleton structure that enforces a consistent entry point and required frontmatter fields like name and description for rapid skill creation.

What is a Skill Unit skeleton and when do I need it?

A Skill Unit skeleton is a ready-to-fill template enforcing a minimal, frontmatter-driven schema. You need it when accelerating the creation of new skills with standardized discovery and activation workflows.

Can I include optional resource directories like scripts and assets in my Skill Unit?

Yes, you can include optional resource directories such as scripts, references, and assets within your Skill Unit to support on-demand loading across workflows.

What's the best way to enforce a consistent entry point across multiple Skill Units?

The best way to enforce a consistent entry point is using a minimal, frontmatter-driven schema with a skeleton body, enabling consistent discovery and activation workflows across multiple Skill Units.

Do I need dependencies to use a frontmatter-driven skill skeleton for documentation?

No dependencies are required to use the frontmatter-driven skill skeleton. It provides a standalone template to populate with documentation and skill logic.