cm-example

Standardize cross-platform skill formatting with a universal frontmatter schema.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-example
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-example
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-example
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-example

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize cross-platform skill formatting to enable a single definition to be compiled into multiple platform configurations.

Core Features & Use Cases

  • Unified frontmatter schema: ensures name and description are defined in the root SKILL.md.
  • Cross-platform compatibility: the same skill can be compiled for Antigravity, Claude, Cursor, and OpenClaw.
  • Use Case: publish a universal skill that can be consumed by multiple agents without rewriting the core logic.

Quick Start

Place a valid SKILL.md at the root with a descriptive name and a clear, actionable description.

Frequently Asked Questions about cm-example

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

FAQPage Schema
What is cross-platform skill formatting for AI agents?

Cross-platform skill formatting standardizes a single skill definition with universal frontmatter so it can be compiled into multiple platform configurations for agents like Antigravity, Claude, Cursor, and OpenClaw.

How do I create a universal skill that works across multiple platforms?

To create a universal skill, place a valid SKILL.md at the root directory with a descriptive name and clear, actionable description in the frontmatter to enable compilation across Antigravity, Claude, Cursor, and OpenClaw.

Does a cross-platform skill format require separate logic for each agent platform?

No, cross-platform skill formatting enables a single definition to be compiled into multiple platform configurations, allowing you to publish a universal skill consumed by multiple agents without rewriting core logic.

What directories are used during cross-platform skill activation?

Optional directories such as scripts/, references/, and assets/ can be used by platforms and tools during skill activation to support the compiled configurations across different agents.

Why should I standardize skill formatting instead of writing platform-specific skills?

Standardizing skill formatting solves the problem of maintaining multiple definitions by enabling a single universal frontmatter schema to compile into configurations for Antigravity, Claude, Cursor, and OpenClaw without rewriting logic.