Skills
A skill is a reusable set of instructions that carries a task's goal, method, source preferences, boundaries, and delivery standard in one package. A skill added to a chat determines how MORATUS handles that task: which steps it follows and in what order, which rules it keeps to, and in what form it delivers the result.
For example, Research Synthesizer verifies sources, separates contradictions, and produces a reliable research summary; Data Analyst cleans raw data, analyzes it, and turns it into actionable insights.
Anatomy of a skill
Every skill comes with a short definition you see in the catalog and the detailed instructions applied while it works. The example below shows how the Data Analyst skill keeps this information together.
{ "id": "data-analyst", "name": "Data Analyst", "category": "expert", "icon": "BarChart3", "description": "Cleans raw data, analyzes it, and turns it into actionable insights.", "whenToUse": [ "CSV, Excel, or spreadsheet analysis", "KPI, trend, anomaly, and segment review", "Executive summary or decision-support report" ], "workflow": [ "Get to know the dataset and its fields", "Clean missing, duplicate, and invalid records", "Choose and run the analysis that fits the question", "Explain outliers and uncertainties", "Visualize the findings and tie them to a recommendation" ], "rules": [ "Base every calculation on the data", "Don't present correlation as causation", "Call out missing or doubtful data" ], "output": { "format": "Executive summary and analysis file", "includes": [ "Key findings", "Segment breakdowns", "Assumptions and limits", "Recommended next steps" ] }}| Field | What it defines | Where you see it |
|---|---|---|
id | The skill's unique identifier. It stays the same whether you use the skill in English or Turkish. | Behind the scenes |
name, description | The skill's name and one-sentence description. | The Skills page; the name also shows on the skill chip in the composer |
category, icon | The catalog tab and icon: expert Everyday experts, business Business and operations, creative Content and communication, builder Building and coding. | Category tabs |
whenToUse | The situations the skill fits; helps you pick the right skill. | The When to use it column of the built-in skill catalog |
workflow | The steps the skill follows, in order. | Skill workflow in the skill's details |
rules | The boundaries and quality rules kept in every run. | Applied in the responses |
output | The shape of the result and what it must include. | Expected output in the skill's details |
Note
Built-in skills come with this information; you don't need to write or edit a file to use them. The example shows what a skill tells MORATUS.
How does a skill come into play?
MORATUS uses a skill in stages, so the context window holds only what is needed at that moment (see Context window).
- Definition: The name, description, and when to use it are known up front; MORATUS recognizes the skill by this short definition.
- Instructions: When the skill is applied to a task, its workflow, rules, and expected output come into play.
- Resources: Large resources such as templates and examples are used only when the task needs them.
Desktop The Desktop agent's tool skills load on demand on the same principle (see Agent skills).
What does a skill change?
| Aspect | Without a skill | With a skill |
|---|---|---|
| Method | You describe it again with every request. | The skill's workflow is followed in the same order every time. |
| Context | Given again in every chat. | Loaded when needed. |
| Sources | Vary with the request. | Which sources come first and how claims are verified is set. |
| Output | Its shape can differ every time. | Delivered in the structure of the Expected output. |
| Quality standard | Depends on the prompt. | The same in every run. |
To see the difference on the same request, see Usage.
Skills, connectors, and project instructions
| Component | What it sets | Example |
|---|---|---|
| Skill | How a job is done: method, rules, and output format. | Analyzing a sales sheet with Data Analyst |
| Connector | Where the work happens: connected apps and tools (see Connectors). | Reading the sales sheet in Google Sheets |
| Project instructions | Lasting rules applied to every chat in a project (see Project components). | “Keep answers short and cite sources for key results.” |
The three work together: in a project, for example, you can analyze the sales sheet in Google Sheets with the Data Analyst skill and get the result in the shape the project's instructions ask for.
When should you add a skill?
- When you do the same kind of work often: a weekly report, a sprint plan, or a content calendar.
- When you want the result to meet the same standard and format every time.
- When the task needs expertise: data analysis, a security review, SEO, or localization.
- Short, one-off questions don't need a skill; MORATUS answers them without one.