skill-contributor

To submit a new skill, fork the repository, create a feature branch, add your skill with proper frontmatter and naming, validate its structure, update the main README, generate a per-skill README if needed, then open a pull request with a detailed description. The workflow guides you through fork verification, validation checks, documentation updates, and automated PR creation.

Skills must pass structural validation covering frontmatter format, file naming conventions, and internal references. The validation process checks that all required metadata is present, links are correct, and the skill follows repository standards before you submit a pull request.

Yes. Contributing a new skill requires updating the main repository README with your skill entry and creating or updating a per-skill README file. The workflow automates this documentation generation to ensure consistency and visibility.

Create a feature branch from your fork, commit your skill files with descriptive messages, then use the automated PR creation to submit your contribution. The workflow handles branch setup, commit structure, and PR generation with pre-filled descriptions.

Yes. The skill includes built-in validation checks that verify proper structure, frontmatter, naming, and references. Running validation early catches issues before you submit the pull request, reducing review cycles.