> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/appendix/skills-based-routing.md).

# Skills Based Routing

Skills based routing will route an incoming interaction to an agent based on skill set specified and on agent availability.

Skills based routing steps:

1. [Create Skill Category.](/appendix/skills-based-routing/skill-category.md) e.g. "Language"
2. Create Skills. e.g. "English" and "Spanish"
3. [Assign skill(s) to Users.](/appendix/skills-based-routing/user-skills.md)
4. [Set queue routing method to Skills](/appendix/skills-based-routing/queue-skills.md).
5. [Select skills category(s) and and required skill(s) for queue.](/appendix/skills-based-routing/queue-skills.md)

{% hint style="info" %}
Real world scenario:

A queue is created with skills based routing. The required skill category is Language with an importance of 10. The selected skill required is French.

There are three users:

Shanon has French language skill level 10

Traci has French language skill level 5

Miles does not have French language skill

When an interaction comes into the queue, a list of qualified agents are generated from most qualified to least qualified. In this scenario, the interaction is sent to Shanon if she is available. If Shannon is not available, the interaction is sent to Traci.  The interaction is never sent to Miles because she does not have the French language skill.
{% 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://cc.docs.landis.cloud/appendix/skills-based-routing.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.