plain-skill

To run a self-contained automation task, you use a Skill directory containing a SKILL.md file with YAML frontmatter for metadata and a Markdown body for operational instructions, requiring no external references.

A SKILL.md file defines a local task by combining a YAML frontmatter with name and description properties with a Markdown body that provides the execution instructions for the automation agent.

No external dependencies are needed to execute a Markdown-based automation skill, as the workflow is self-contained and only optionally loads local resources or scripts if they are present in the directory.

Yes, you can include optional local scripts and resources in a self-contained skill directory, which the execution agent will load and integrate if they are provided alongside the SKILL.md file.

The best way to standardize small automation tasks is using a minimal SKILL.md format with YAML frontmatter, ensuring predictable execution without external references for each local project.

You should not use a self-contained skill for automation tasks that require external references, complex dependencies, or fall outside the scope of basic, lightweight local project scenarios.