I prefer a clear CLI operation to a prompt trying to anticipate every move an agent makes. Reusing work should reduce how much I need to explain. When the solution requires memorizing a manual for every task, maintenance has merely moved somewhere else and now consumes context too.
Mistral introduced Spaces in March 2026 as a CLI for people and agents, covering scaffolding, configuration, and staging deployments. Looking back in October 2026, I am interested in that shared interface. An operation I can understand at a terminal can also give an agent a predictable way to execute part of a job.
In August 2026, I requested delegated research to turn a capability into a reusable skill. A month earlier, in July, I had raised another concern: the rules we created to organize models might constrain newer models. I want to reuse the research without requiring the next agent to repeat every decision made by its predecessor.
Take a hypothetical command that prepares a project structure and reports what it created. The skill explains when to use it and how to check the result. If the request needs a different structure, the agent should recognize the difference. Forcing every task to fit the available command is a remarkably laborious way to save effort.
Parameters need to explain what they select. If one identifies an environment, I want that meaning to be legible. When a prerequisite is missing, the tool should name it. That makes choosing the next step possible without interpreting a vague message as success. It helps me at the terminal and the agent using the same interface.
The response also needs to describe the change made. Receiving only done means I have to hunt down the result before continuing. I do not want a giant report; I want enough information to connect the operation with the state it left behind. That is a small, concrete responsibility I can assign to a CLI.
My rule is to keep documentation close to the command and have the skill refer to it. Copying the entire contract into several prompts multiplies maintenance when the tool changes. For the next reusable operation, I want to check two requests: one it handles and another that requires leaving the prepared route. The skill needs to help an agent recognize both before I call it useful.