> For the complete documentation index, see [llms.txt](https://docs.amesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amesa.com/identify-agent-skills/generate-activity-clusters.md).
# Generate Activity Clusters
## Identify Activity Clusters
Activity clusters are distinct operating regions where the system needs to perform differently in order to succeed. Each cluster represents a single scenario — the conditions present in the system, as captured by sensor data — paired with a single "skill," meaning the actions an operator or agent must take to succeed under those conditions. A complex process can contain hundreds of activity clusters, each corresponding to a different combination of conditions and required actions.
### Clustering Lens
The clustering algorithm relies on a "lens" to determine how activity clusters are formed. This lens defines the axis along which the state space is divided, and can be applied in a few different ways:
* **Cluster by time**: For phased processes, clustering by time organizes the state space into regions based on which conditions occur together at the same point in time.
* **Cluster by a specific variable**: Choosing a variable — such as machines or SKUs — organizes the state space into regions based on similarities between groups within the data.
* **Cluster in aggregate**: Aggregate clustering considers all variables at once, forming clusters based on the combined similarity across every dimension of the data simultaneously.
### Cluster Labels
Each cluster is defined by a specific range of sensor variable values. To make these clusters easier to interpret, an LLM automatically generates a human-readable label for each region — for example, naming a cluster "Stable Flow" or "Overheat" based on the sensor ranges it covers. These labels make it possible to quickly identify which regions correspond to successful operation versus which represent strain, stress, or failure conditions. Agents use these labeled regions to optimize the process: they learn to identify the successful regions and steer operation toward them.
## Why Identify Activity Clusters?
Identifying activity clusters serves two key purposes.
First, activity clusters are foundational to designing a team of agents. Each activity cluster will later be configured as its own scenario, with a dedicated agent assigned to it. That agent then practices within its assigned scenario, receiving feedback until it becomes an expert operator for that one specific skill.
Second, activity clusters help build a deeper understanding of the task itself. Domain experts will typically recognize most of the clusters from their own experience, confirming that the analysis reflects real-world operating conditions. At the same time, the clustering process often surfaces additional clusters that weren't previously known to experts — revealing patterns or edge cases in the data that hadn't been identified before.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.amesa.com/identify-agent-skills/generate-activity-clusters.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.