> For the complete documentation index, see [llms.txt](https://docs.dorg.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dorg.pro/create-competency/getting-started/quickstart.md).

# What is an Operational Competency

From a functional perspective, an **Operational Competency (or Skill)** within Dorg is a **bounded, accountable capability** that enables a Dorg to perform a **recognizable business function** autonomously, reliably, and within defined constraints.

From a technical perspective, an **Operational Competency** is an **atomic and reusable** software unit that:

* encapsulates a well-defined functional capability
* can be invoked by a Dorg agent
* is described by a **JSON manifest**
* is implemented as a **standard MCP module**

In the following documentation you'll find all details that allow you to create a new Dorg Operational Competency and publish it in the Dorg University.

{% hint style="info" %}
From now on, we will use the simplified term "Competency" with the meaning of "Operational Competency". Dorg manages also other type of Competencies that are not treated here.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dorg.pro/create-competency/getting-started/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.