> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/moving-skills-to-sor-master.md).
# Moving Skills to SOR Master
## Context
Skills are the schedule of rates of type labour, as of now these are maintained as separate master’s data into MDMS while these should be part of SOR.
This will help to maintain these in one place and make effective in both the places Estimate and Muster Roll.
## Details
1. Skills to be created as SOR.
2. In estimate and muster roll, data to be fetched from SOR.
3. Separate Skills master data to be discarded.
4. It has to be ensure all the features are intact and working properly after making this changes.
## Acceptance Criteria
1. Separate skills master data is discarded.
2. Skills data is fetched from SOR in all the places.
3. All the affected feature to be tested properly to ensure things are working fine.
---
# 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.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/moving-skills-to-sor-master.md?ask=&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.