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.
-
assess-before-deletingactive v1Assess before deleting
Remove a file, branch, worktree, record or process only after each candidate has been classified by what depends on it and what would be lost, and the reversible step has been taken first.
cleanupsafetyevidenceworktrees -
deploy-siteactive v1Deploy 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 -
evolveactive v1Evolve the repository's know-how
Turn what sessions observed into reviewed knowledge and into the rule, skill, document or test each lesson belongs in, then deliver the change and tell every peer what moved.
knowledgereviewdeliverycoordination -
implementactive v1Implement 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 -
pack-for-chatgptactive v1Pack the sources for a ChatGPT project
Turn a committed tree into token-bounded Markdown shards that a ChatGPT project's file search indexes, verified to carry no binary, worktree, link, build output, projection or leaked value, and hand them over with the commit they were cut from.
reviewarchiveprivacychatgpt -
pack-for-reviewactive v1Pack the repository for an outside reviewer
Prepare a bounded, reproducible snapshot of the tracked tree for a reviewer who cannot read the repository directly, with the local half and anything secret left out and the questions the review must answer written down.
reviewarchiveprivacy -
repo-reviewactive v1Repository 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 -
report-verification-stateactive v1Report by verification state
Write the outcome of a piece of work as claims each marked VERIFIED, PARTIAL or BLOCKED by the evidence actually observed, so a reader can tell what was proved from what was only done or intended.
reportingevidencehandover
In Claude Code, by name
69 skills are projected into .claude/skills/: 1 command, 60 domain, 8 skill. A domain is one module of the capability registry, typed as /mj-<module>; a command is a capability that declares its own name; a skill points at a workflow above. A capability that changes something runs only when a person asks for it.
| Name | Kind | What it reaches |
|---|---|---|
| /intent | command | Propose an intent: what must become true. Runs the Majordomus capability intents.propose with the text you type as its `statement`. |
| /mj-artifacts | domain | Majordomus artifacts: List the generated artifacts. |
| /mj-blackboard | domain | Majordomus blackboard: Who works on what, now. |
| /mj-brief | domain | Majordomus brief: The session brief. |
| /mj-capabilities | domain | Majordomus capabilities: Describe one capability; List capabilities; Where each capability is projected. |
| /mj-commands | domain | Majordomus commands: One command in full; The whole command graph; Every command, one line each. |
| /mj-commit | domain | Majordomus commit: Judge a range of history; What the working tree would commit; The scope vocabulary; Judge one commit message. |
| /mj-continuity | domain | Majordomus continuity: This device's identity, and its label; Whether and how a published handover can be resumed here; Publish this checkout's newest handover for another machine; Every published handover the local store admits; Resume a handover another machine published; What the lifecycle is… |
| /mj-convergence | domain | Majordomus convergence: Is any work held where it can be lost?. |
| /mj-dashboard | domain | Majordomus dashboard: The Overview: four questions. |
| /mj-delivery | domain | Majordomus delivery: Does this feature exist; Does each feature exist. |
| /mj-deploy | domain | Majordomus deploy: Would these deployments work; One deployment; Deployments; What was deployed, and where. |
| /mj-design | domain | Majordomus design: Whether the declared colours can be read; What a design token means; The design system; The design tokens. |
| /mj-devcontext | domain | Majordomus devcontext: Compile the context for a piece of work; Why one thing is or is not in a compiled context; The compiler's own rules. |
| /mj-devtask | domain | Majordomus devtask: One issue as an executable development task; One milestone as an executable dependency graph. |
| /mj-directories | domain | Majordomus directories: The layer's directory contracts. |
| /mj-distribution | domain | Majordomus distribution: The artifact of a target; This build; The distribution model; Published releases; Whether the published installation works. |
| /mj-economics | domain | Majordomus economics: Refuse unsupported economics claims; Explain one economics metric; Recorded benchmark runs; Token economics summary; Each task's delivery economics. |
| /mj-editors | domain | Majordomus editors: Editor and agent projections. |
| /mj-entity | domain | Majordomus entity: Every kind, and whether every object of it is addressable; Read one entity. |
| /mj-environment | domain | Majordomus environment: Where an environment value came from; Whether Majordomus is in force here, and what proves it; The repository environment. |
| /mj-episodes | domain | Majordomus episodes: Attach this connection to an episode; Close this connection's episode; List episodes. |
| /mj-evidence | domain | Majordomus evidence: What proves this claim; Every claim against the evidence recorded for it; What this test proves. |
| /mj-executions | domain | Majordomus executions: Ask an execution to stop; Demonstrate an execution; An execution's event history; One execution; List executions; The live channel's contract; Start a capability as an execution. |
| /mj-gates | domain | Majordomus gates: Whether this task may be called finished; The CI model; The completion policy; How each gate last went. |
| /mj-graph | domain | Majordomus graph: Derive one graph; List graphs. |
| /mj-guard | domain | Majordomus guard: Judge one edit. |
| /mj-health | domain | Majordomus health: Health of this process. |
| /mj-integration | domain | Majordomus integration: What cleanup would do; The integration audit trail; Why one pull request is where it is; Proof that a dry run moves nothing; The integration queue; How long CI takes; The trains of stacked pull requests. |
| /mj-intent-realization | domain | Majordomus intent realization: Why an intent stands where it stands; Which work realises which intent, and what each still lacks. |
| /mj-intents | domain | Majordomus intents: What a piece of work is bound to before it starts; Which work carries which criterion, and why each issue exists; Every intent, with its derived stage and verdict; Which intent a piece of work serves, or why it may not proceed; Propose an intent: what must become true; One… |
| /mj-knowledge-base | domain | Majordomus knowledge base: Candidates awaiting review; One knowledge record; Whether the deriver is still writing. |
| /mj-layout | domain | Majordomus layout: Refuse a misplaced artifact. |
| /mj-lifecycle | domain | Majordomus lifecycle: The records a clone receives; Every open episode; What each provider's adapter declares; What the store needs somebody to do; The commit this process is answering about. |
| /mj-mcp | domain | Majordomus mcp: The MCP projection of this registry. |
| /mj-mesh | domain | Majordomus mesh: The sccache client configuration for the store this node selected; What every dependency install and build directory is cached under; Claim a scope across the mesh; Cooperation, at a glance; The mesh self-check; Enrol this machine in the mesh; The cooperation journal; The host… |
| /mj-models | domain | Majordomus models: The model catalogue; Route a need to a model. |
| /mj-monitor | domain | Majordomus monitor: Follow everything in one stream. |
| /mj-objects | domain | Majordomus objects: Get one object; List objects; Search objects; Verify the index against the working tree. |
| /mj-obligations | domain | Majordomus obligations: What this task still owes; Every obligation there is. |
| /mj-observatory | domain | Majordomus observatory: Observatory capture; Observatory events; Observatory replay. |
| /mj-pack | domain | Majordomus pack: Plan a source pack; Verify a written source pack. |
| /mj-peers | domain | Majordomus peers: Announce what this peer is working on; List peers. |
| /mj-perf | domain | Majordomus perf: Performance counters. |
| /mj-plan | domain | Majordomus plan: How far each issue's work has travelled; Where the plan's stamps contradict the delivered work; Where the work is now; The issues, filtered by what the graph derived; The whole derived plan; The one issue to take now; One milestone or issue, with everything derived about it; The… |
| /mj-product | domain | Majordomus product: The domains; One feature; The features; Features against interfaces; The providers; Validate the model. |
| /mj-quality | domain | Majordomus quality: Public API quality report; Rustdoc tree integrity. |
| /mj-reasoning | domain | Majordomus reasoning: The advisors and what they can do now; Check that reasoning stays provider-independent; Why a decision was made; What an uncertainty calls for; Record a reasoning step; The session's reasoning state. |
| /mj-recover | domain | Majordomus recover: Classify every stray file of the record stores, and sweep the ones that are nobody's. |
| /mj-release | domain | Majordomus release: What the public contract did, and the smallest version it allows; The changelog; Whether the trunk's landed work is released; The version a landing allocates, and why; The version, and the one the contract requires next. |
| /mj-repository | domain | Majordomus repository: Repository and index state; The repository scope; Judge a path against the scope. |
| /mj-rules | domain | Majordomus rules: What this test proves; Every rule against the proof there is for it; What proves this rule. |
| /mj-served | domain | Majordomus served: What each deployment was last seen serving. |
| /mj-server | domain | Majordomus server: The shared server, and every server of the repository. |
| /mj-session-domain | domain | Majordomus session domain: What identifies this checkout, and how each store spells it; The episode lifecycle, as data. |
| /mj-shell | domain | Majordomus shell: Refuse undeclared shell. |
| /mj-skills | domain | Majordomus skills: One skill, with everything derived about it; Every skill, with its derived standing; What the skills owe and do not have. |
| /mj-trace | domain | Majordomus trace: What contract this commit served; What realised this issue; The whole work graph above the branch. |
| /mj-web | domain | Majordomus web: Every web surface, resolved. |
| /mj-why | domain | Majordomus why: Operational areas; Audiences; Diagnose a selection; The catalogue; One moment; Validate the catalogue. |
| /mj-worktree | domain | Majordomus worktree: One branch: where its worktree belongs and what is there; What it would take to bring every worktree home; Where this is, and whether that is where it belongs; The whole topology; How far a checkout is from the remote trunk; Uncommitted work in the linked worktrees, and what… |
| /assess-before-deleting | skill | Remove a file, branch, worktree, record or process only after each candidate has been classified by what depends on it and what would be lost, and the reversible step has been taken first. |
| /deploy-site | skill | 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. |
| /evolve | skill | Turn what sessions observed into reviewed knowledge and into the rule, skill, document or test each lesson belongs in, then deliver the change and tell every peer what moved. |
| /implement | skill | 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. |
| /pack-for-chatgpt | skill | Turn a committed tree into token-bounded Markdown shards that a ChatGPT project's file search indexes, verified to carry no binary, worktree, link, build output, projection or leaked value, and hand them over with the commit they were cut from. |
| /pack-for-review | skill | Prepare a bounded, reproducible snapshot of the tracked tree for a reviewer who cannot read the repository directly, with the local half and anything secret left out and the questions the review must answer written down. |
| /repo-review | skill | 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. |
| /report-verification-state | skill | Write the outcome of a piece of work as claims each marked VERIFIED, PARTIAL or BLOCKED by the evidence actually observed, so a reader can tell what was proved from what was only done or intended. |
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.