Skills: the patterns to work by, and the ones awaiting a ruling
skillsRead adopted project patterns—reusable recipes, checklists, and conventions—to apply settled ways of working; omit id for all adopted patterns or pass an id to retrieve one specific pattern.
Instructions
Read the patterns (skills) recorded here: the reusable recipe, checklist or convention itself, not just its name. Call it with no id (an empty argument object) to get every ADOPTED pattern: those are the ways of working this project and machine have settled on, and nothing else arrives that way. That answer carries the BODIES when they fit in one read, and their NAMES when they do not: it says which it did, and how many there are, so a list of names is an invitation to ask for the one you need by id and never a record of empty patterns. Call it with an id to get that one, which is also how you read a pattern that is still proposed or reviewed (every item bootstrap lists as awaiting a judgement), because a pattern cannot be ruled on without being read. Each answer says the state it served, and a pattern that is not adopted is not how the work is done here; it was served so the ruling can be made on its text. A rejected or deprecated pattern IS refused: a way of working the project retired is worse to hand over than nothing. Consulting a pattern is RECORDED against this session (once per skill), so the record shows which work was informed by which pattern: it records that you read it, never that you followed it. WHAT A PATTERN IS: a skill body is content from this project’s record: text the people and agents working on this project wrote; mnema records it and serves it back, and does not vet what it says. Each pattern is served with the state it is in and, when it is adopted, the agent that adopted it, or “a person” when someone adopted it directly with no agent. A pattern that is not adopted is one the project has not ruled on: it is served so the ruling can be made on its text, and it is not how the work is done here. A reply that carries only NAMES carries none of that: nothing was served to say it about, and the id beside each name is how the pattern itself is asked for.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "skills"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | A single skill id to read: the only way to reach one awaiting a ruling, and the way to a body the mass answer served only the name of; omitted, every adopted pattern. |