Skills
Provider-neutral procedures for one bounded kind of work each, read from the repository's skills section. Every page is the skill's own file; every listing is derived from it.
Filtering runs in the browser. Without JavaScript every skill below is still listed.
-
deploy-siteactivev1Deploy the site by hand
Publish the website to GitHub Pages from a terminal, through the one script the Pages workflow runs, when waiting for the Actions queue is not acceptable.
sitedeployevidence -
implementactivev1Implement a change
Carry a requested change through the repository evidence-first, from the invariant it must keep to a verified, reconciled, documented and committed tree, without widening its scope.
implementationevidenceinvariantsdrift -
repo-reviewactivev1Repository review
An evidence-driven review of the actual state of the repository, or of one change to it, before meaningful engineering work is recommended or done.
reviewevidenceinvariantsdrift
What a skill is, and where these come from
A skill is a provider-neutral procedure for one bounded kind of work: a directory under the repository's skills section holding SKILL.md, front matter over a body with a purpose, a procedure and an output contract. A worker loads one when the task is about what it covers, never by default.
Nothing on this page is typed into the site. The source class skill in the repository's knowledge sources discovers the files; majordomus skills list, doctor, the MCP resources majordomus://skill/<id> and this page all read that one catalogue, and majordomus skills check refuses a skill whose front matter, directory, sections or references are wrong. Adding a skill is adding its directory; every surface follows.