> For the complete documentation index, see [llms.txt](https://docs.itsyourskills.com/skills-thoughts/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itsyourskills.com/skills-thoughts/iys-solution-to-issues-with-skills/a-common-terminology-of-skills.md).

# A common terminology of Skills

We discussed different challenges we face with regard to skills terminologies. One can take a look at them in this page.

{% content-ref url="/pages/-MiMjVjIsMo3n7EsqOvM" %}
[Issues with Skills Nomenclature](/skills-thoughts/issues-with-skills-nomenclature.md)
{% endcontent-ref %}

In the Skills Ontology i.e. the backend, when skills are added, they are normalized. Like in a thesaurus, terms are equated if they refer to the same thing or concept.

There are different scenarios for such equation.

1. Spelling differences
2. Acronyms
3. Synonyms

These have been discussed in the page on Issues with Skills Nomenclature. So we are not going into details here.

For an user who is creating a Skills Profile using the Skills Profiler in the frontend, the system will take the user to the primary term (used by the system) whichever of the equated terms she searches on.\
Examples:\
1\. When Internet Marketing is searched user will be taken to Online Marketing\
2\. When Dotnet is searched user will be taken to .Net\
3\. When user searches on AI the user will be taken to Artificial Intelligence

IYS has spent considerable time curating differentiated but common meaning terms. And this normalization is a continuous activity. 


---

# 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.itsyourskills.com/skills-thoughts/iys-solution-to-issues-with-skills/a-common-terminology-of-skills.md?ask=<question>&goal=<endgoal>
```

`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.