> For the complete documentation index, see [llms.txt](https://dappos.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dappos.gitbook.io/docs/dappos/xbubble/how-xbubble-works/sop-system.md).

# SOP System

An SOP is xBubble's packaged solution for a specific type of task.

SOP = Skills + runtime + APIs + MCPs + model selection

A Skill alone is not always enough. The result also depends on the runtime environment, the model used, the available APIs, the connected MCPs, and how the task is executed. xBubble packages these parts together so the user does not need to configure them separately.

Compared with a normal Skill marketplace, xBubble's SOP system emphasizes three advantages:

**Stable Performance**

An SOP does not only include a Skill. It also includes the runtime environment, model choice, MCPs, and third-party APIs needed for the task. SOPs are also used within tested scopes. When a user's task matches the SOP's verified range, the output is more stable.

**Easy to Use**

An SOP takes the user's task description as the main input. Users do not need to choose a model, configure APIs, compare multiple Skills, or debug the execution process. Bubble Pilot selects the suitable SOP and runs it.

This moves the operational burden from the user to the system.

**Self-Generated SOPs**

Developing a good Skill requires testing, debugging, and optimization. For non-technical users, this can be difficult and time-consuming.

For many needs, Bubble Engine can help users generate specialized SOPs without requiring them to write or debug Skills themselves. SOPs can be general, or they can be narrower solutions for a specific user or company requirement.

<br>