e2e-publish-check

To validate skill metadata and packaging before publishing, run an end-to-end check that verifies required frontmatter fields, directory structure, and packaging integrity to ensure your package is publish-ready.

Yes, you can test skill publishing without deploying by using a dry-run simulation. This catches errors and validates readiness across environments without performing an actual deployment.

You can enforce skill publishing quality gates in CI/CD pipelines by integrating an end-to-end validation check into your automated workflows to verify metadata and packaging integrity before release.

Skill validation checks required frontmatter fields to ensure metadata correctness. The validation process verifies that all necessary frontmatter fields are present and properly formatted before publishing.

Skill validation works across both local development and CI environments. It applies to skill directories during CI workflows and local development when preparing a publish-ready package, validating required fields and packaging integrity.

You need end-to-end validation for skill publishing when preparing a package for release. It ensures metadata correctness, packaging integrity, and dry-run publish requirements are met before actual deployment across environments.