Skip to content

Skills are procedures as data, discovered and checked, never registered

A skill is a provider-neutral procedure for one bounded kind of work, front matter under a schema over a body with a purpose, a procedure and an output contract; the source class discovers it, skills check holds every one to its contract, and nothing loads a skill unless the task is about it.

A skill is one directory under the layer; adding it is the whole act, and the command line, the website and MCP all read it from the same file.

status
stable
exposed through

What it does

majordomus skills list shows every skill the source class discovered, skills show one of them, skills check every one against its contract; the website's skills section and the MCP resources are projections of the same files.

What it does not do

A skill that merely describes is documentation and belongs in the docs. Nothing ranks skills and nothing loads one by default.

The commands that run it

  • majordomus skills work · read-only

    The repository's skills — provider-neutral procedures under the skills section — listed, shown and checked from the one catalogue every surface reads.

The objects it is made of

Kinds of the layer. Each is a schema, a source class and a file on disk; the number beside it is what this repository holds today, counted at build time.

  • skill3

The rules that hold it

What is guaranteed

Executable use cases