Every skill here was built by a student, tested on a real task, and merged only after the evidence was reviewed. Nothing lands on a promise.
Reviewed, evidenced, and installable in 30 seconds.
Skills ship as pull requests, not issues โ an issue is a conversation that gets closed, a PR is files that get merged and stay installable.
Fork this repo, clone your copy, then git checkout -b skill/my-skill.
Test it on a real task. You need a transcript โ a description of one will not pass.
That it fires on the symptom, and that it stays quiet on a near-miss.
python scripts/validate_skill.py โ then open the PR and review someone else's.
Full step-by-step guide โ The template
That validator is a gate, not a suggestion. The same script runs in CI and blocks the merge if it fails. A rule in prose is advisory; a rule in code is enforced โ which is the whole lesson of Module 5B, applied to the repo you are contributing to.