Skills Specification for clawd-cli

Standardize SKILL.md frontmatter schema for automated skill discovery.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ticruz38/skills --skill skills-specification-for-clawd-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Skills Specification for clawd-cli
Source: https://github.com/ticruz38/skills/tree/main
Command: npx skills add https://github.com/ticruz38/skills --skill skills-specification-for-clawd-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a standardized SKILL.md frontmatter schema and discovery workflow to unify how skills are described, indexed, and activated within the OpenClaw ecosystem.

Core Features & Use Cases

  • Standardized frontmatter fields including name, description, version, author, entry, type, and health checks to ensure consistent discovery.
  • Metadata-driven tooling that enables automated indexing, health checks, and dependency resolution across Skills.
  • Quick-start templates and validation workflows to accelerate skill creation and deployment.

Quick Start

Create a new skill by copying a template, then fill in the key metadata fields so the skill can be discovered and loaded by the runtime.

Frequently Asked Questions about Skills Specification for clawd-cli

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

FAQPage Schema
How do I standardize skill metadata for CLI discovery?

Standardize skill metadata for CLI discovery by defining a SKILL.md frontmatter schema with fields like name, description, version, and entry to enable automated indexing and activation in the OpenClaw ecosystem.

What is SKILL.md frontmatter validation and when do I need it?

SKILL.md frontmatter validation checks metadata conformance for skills in a repository. You need it during onboarding new skills or enabling automated discovery to ensure consistent indexing and health checks across the CLI ecosystem.

How do I create a new skill using a frontmatter template?

Create a new skill by copying a quick-start template, then fill in the key frontmatter metadata fields such as author, type, and health checks so the skill can be discovered and loaded by the runtime.

Can I automate dependency resolution across skills in a repository?

Yes, you can automate dependency resolution across skills by using the metadata-driven tooling defined in the SKILL.md frontmatter specification, which supports automated indexing and health checks.

Does the skill specification work without external dependencies?

Yes, the skill specification operates without external dependencies, relying entirely on the standardized SKILL.md frontmatter schema to drive automated discovery, validation, and deployment workflows.

What are the limitations of using frontmatter for skill discovery?

The frontmatter discovery approach is limited to skills conforming to the SKILL.md schema, meaning any skill lacking the exact required metadata fields cannot be indexed or activated by the CLI runtime.