# Skills

Skills give CKEditor AI knowledge of the markup behind an editor feature, such as footnotes or merge fields, so the HTML it writes is what your editor accepts. There is nothing to set up. Skills are part of the service, and the agent loads a skill only when the request needs that feature. This page covers which features the built-in skills cover and where the agent uses them.

<a id="when-to-use-it">

## When to use it

HTML lets you build the same structure in more than one way. Ask a general-purpose model for footnotes, and it picks one shape. If that shape is not the one your editor supports, the editor drops or downgrades the markup when it loads the content. With CKEditor AI, you do not have to describe your markup in every prompt. A skill names the feature, describes its rules, and shows the markup the editor produces.

The agent loads skills where it writes document content: in [chat](../conversations.md) and in [Document Processing](../document-processing.md). Actions and reviews do not load skills. They rely on the model’s own knowledge of HTML.

<a id="built-in-skills">

## Built-in skills

The built-in skills cover CKEditor 5 features such as text formatting and structure, tables and lists, links and bookmarks, media, merge fields, math equations, and footnotes. The agent does not know the markup of your own plugins. The agent also reads your editor configuration. It writes markup only for the features your editor enables, and it uses only the option values your configuration allows.

New and improved skills come with service releases. Your integration does not change.

<a id="next-steps">

## Next steps

* **[How CKEditor AI works](../how-it-works.md)** describes what the agent holds in context and how skills fit into a request.
* **[Context library](context-library.md)** gives the agent knowledge of your content: style rules and reference files.

---

Full index of the Cloud Services documentation: [llms.txt](../../../../llms.txt)