my-skill

To create a reusable automation skill for FTC robotics workflows, you add a SKILL.md file with frontmatter fields like name, description, license, and compatibility, then place helper files in optional resource directories such as scripts or references.

Skill discovery in Claude-compatible agent workflows requires a SKILL.md frontmatter with mandatory name and description fields, while optional fields include license, compatibility, and resource directory paths for scripts, references, and assets.

Yes, you can use optional resource directories to organize a robotics skill unit. The structure supports scripts, references, and assets folders, providing on-demand content and tooling that enable activation and reuse across developer teams.

The best way to package a self-contained capability for FTC robotics teams is to encapsulate it as a skill unit with a documented entry point, a mandatory SKILL.md frontmatter, and optional resource folders, ensuring structured discovery and activation via metadata.

No specific dependencies are required to build a Claude-compatible skill unit. The skill is self-contained and relies only on a SKILL.md file with proper frontmatter fields and optional resource directories for scripts, references, and assets.