writing-product-metadata

Author and maintain product.yaml metadata files aligned with Schema.org types.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/musher-dev/bundles --skill writing-product-metadata
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-product-metadata
Source: https://github.com/musher-dev/bundles/tree/main/product-profile-authoring/skills/writing-product-metadata
Command: npx skills add https://github.com/musher-dev/bundles --skill writing-product-metadata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation and maintenance of product.yaml files, ensuring product metadata is accurate, structured, and aligned with industry standards like Schema.org for better discoverability and integration.

Core Features & Use Cases

  • Canonical Metadata Authoring: Create and update product.yaml files as the single source of truth for product information.
  • Schema.org Alignment: Ensures all metadata fields conform to Schema.org Product/SoftwareApplication types.
  • Use Case: When launching a new product, use this Skill to author its product.yaml file, defining its identity, audiences, capabilities, and compliance posture according to Schema.org best practices.

Quick Start

Use the writing-product-metadata skill to author a new product.yaml file for a product named 'AwesomeApp'.

Frequently Asked Questions about writing-product-metadata

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

FAQPage Schema
How do I create a canonical product.yaml file for a new product launch?

Canonical product metadata maintains a single source of truth by structuring product identity, capabilities, and compliance posture in a standardized format. This approach ensures accurate discoverability and integration across systems using Schema.org alignment.

How do I align product catalog fields with Schema.org Product types?

Schema.org alignment maps product identity, audiences, capabilities, and integrations to structured data output conforming to Product and SoftwareApplication types. This ensures your metadata follows industry standards for better discoverability.

What should I include in a product profile to define compliance posture and differentiators?

Defining compliance posture and differentiators requires specifying product identity, audiences, capabilities, integrations, and compliance status in your metadata. This skill structures these elements into a canonical product.yaml file for complete product profiles.

Does this approach support maintaining existing product metadata files?

Maintaining canonical product metadata involves updating existing product.yaml files to ensure continued accuracy and Schema.org alignment. This skill supports both authoring new files and maintaining current ones as the single source of truth.

What is the best way to structure product metadata for system discovery and integration?

The best way to structure product metadata for discovery and integration is using a canonical product.yaml file aligned with Schema.org types. This ensures accurate, structured metadata conforming to industry standards for seamless system integration.