intermediate-example

Metadata enables semantic indexing and discoverability. Use frontmatter fields including name, description, version, author, created, updated, category, tags, complexity, and example references following semantic versioning conventions and lowercase tag standards.

Organize examples in a dedicated `examples/` subdirectory with practical, self-contained scripts. This structure makes skills more understandable and allows users to quickly grasp implementation patterns without searching through core logic.

Yes. Named fields (name, description, version, author, created, updated, category, tags, complexity, has_examples, example_files) and organized example subdirectories satisfy requirements for accurate indexing and user navigation across skill repositories.

Comprehensive metadata including versioning, authorship, categorization, and complexity levels enables accurate semantic indexing. This makes skills findable by search engines and users, bridging gaps between basic and advanced skill development.

A well-structured example includes a `SKILL.md` overview and practical code scripts in the `examples/` directory. This demonstrates metadata integration and provides hands-on illustration of skill usage patterns and entry points.