Thanks for helping. The most valuable contribution is a correction or addition backed by a source.
- Cite it. New claims need a source or a dated observation, and one of the three labels
(verified, observed, general) described in
skills/github-seo/SKILL.md. - Date it. Registry flows, subreddit rules and gallery requirements change. Include the date you checked.
- Keep it short. The skill should stay easy for a model to follow. Move depth into
references/. - No client data. Never include names, domains or details from private projects.
-
Fork and branch from
main. -
Make the change.
-
CI checks the skill frontmatter, the evals, the manifests and the internal links on each pull request. To run the same check before you push:
sed -n '/<<.EOF./,/^ *EOF$/p' .github/workflows/ci.yml | sed '1d;$d' | sed 's/^ //' | python3 -
-
If you changed when the skill should trigger, update
skills/github-seo/evals/evals.json. -
Add a line to
CHANGELOG.mdunder an Unreleased heading. -
Open a pull request and fill in the template.
Open an issue using the bug report template and link the source that contradicts the skill.