ckeditor — Claude Code plugin: what it does, how to install
Set up CKEditor 5 in a JavaScript project or update an existing integration. Use it when adding the editor or moving a project to another version.
MIT ★ 4 updated 2026-10-23
/plugin install ckeditor@claude-plugins-official
/plugin marketplace add anthropics/claude-plugins-officialWhat ckeditor does
The plugin includes the ckeditor skill, which guides installation, editor setup with or without a framework wrapper, feature configuration, CSS, and license keys. Its setup path also covers premium features. Reference files on installation, frameworks, licensing, and other topics load when needed.
The ckeditor-update skill handles an existing integration: it selects a migration path, applies changes from the version guides, checks the result, and reports the edits. Legacy predefined builds are covered too. The skills rely on current documentation for version-specific details, so access to live docs helps; Kapa MCP is optional.
What it helps with
- choose an installation method for CKEditor 5 in a JavaScript project
- wire the editor with or without a framework wrapper
- configure editor features, CSS, and a license key
- migrate an existing integration and apply version changes
Example prompts for the agent
- Set up CKEditor 5 in this JavaScript project and configure the features I need.
- Check the license setup and enable CKEditor 5 premium features.
- Update this CKEditor 5 integration to a newer version and verify the changes.
How to install ckeditor
Plugin marketplace
/plugin install ckeditor@claude-plugins-official/plugin marketplace add anthropics/claude-plugins-officialStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about ckeditor
How do I install ckeditor in Claude Code?
Run these commands in order: /plugin marketplace add anthropics/claude-plugins-official, then /plugin install ckeditor@claude-plugins-official.
What does the ckeditor plugin do?
It guides CKEditor 5 setup in JavaScript projects and upgrades existing integrations using the relevant version guides.
Does ckeditor require an MCP server?
No. The skills work on their own; Kapa MCP is an optional way to search CKEditor documentation.
Source text
SKILL.md · MIT
# CKEditor skills
Official **[Agent Skills](https://agentskills.io/home)** for working
with CKEditor, designed to be portable across AI coding agents (Claude Code,
Cursor, Codex, and any tool that supports the open skill format).
> [!TIP]
> **New to CKEditor skills?** Start with the
> [Using CKEditor 5 with AI coding agents](https://ckeditor.com/docs/ckeditor5/latest/getting-started/ai-coding-agents.html)
> guide. It explains what the skills do, which agents are supported, how to
> install them, and how to connect your agent to the live documentation.
The first skill, **`ckeditor`**, takes a developer and their coding agent from
"I want a rich-text editor" to a **working, configured, correctly-licensed
CKEditor 5** — picking an install method, wiring the editor (vanilla or a
framework wrapper), configuring features, loading CSS, setting the license key,
and unlocking premium features. It's an **umbrella router**: it detects the
project's state and routes to the right path, in any JavaScript environment.
The second skill, **`ckeditor-update`**, updates an **existing** CKEditor 5
integration from one version to another — including legacy setups such as
predefined builds. It walks the official update guide of every major version in
the range, applies the breaking changes in code (not only in `package.json`),
keeps every feature the editor had, verifies the result, and reports each change
with the guide section that required it.
> [!NOTE]
> **Want a skill for something else with CKEditor?** This repo is meant to grow
> beyond install + configure. If you'd like a skill for a specific feature,
> workflow, or integration, [open an issue](https://github.com/ckeditor/skills/issues)
> and tell us what you need — requests help us decide what to build next.
## Install
**skills.sh** (any supported agent):
```bash
npx skills add ckeditor/skills
```
**Claude Code plugin marketplace:**
```
/plugin marketplace add ckeditor/skills
/plugin install ckeditor@ckeditor
```
**Manual:** copy `skills/ckeditor/` (and `skills/ckeditor-update/`) into your
agent's skills directory (e.g. `.claude/skills/ckeditor/`).
Once installed, the skills load automatically: `ckeditor` when you ask your
agent to install, set up, configure, or troubleshoot CKEditor, and
`ckeditor-update` when you ask it to update CKEditor to a newer version.
## What's in here
```
skills/ckeditor/
├── SKILL.md # umbrella router + core workflow (loads first)
└── references/ # loaded on demand
├── installation.md # npm / CDN / ZIP, single-package model, versions
├── frameworks.md # any-JS baseline, official wrappers, SSR
├── configuration.md # editor types, plugins/toolbar, CSS, i18n, TS, CSP
├── licensing.md # free/GPL, commercial keys, premium, trial/portal
├── gotchas.md # universal gotchas, "don'ts," troubleshooting
├── documentation-access.md # doc sources (Kapa MCP, docs site, llms-full.txt, TypeScript types, llms.txt) + docs request tags
└── skill-feedback.md # how to report wrong/missing guidance
skills/ckeditor-update/
├── SKILL.md # migration workflow: detect → route → walk guides → apply → verify → report
└── references/
├── documentation-access.md # update guides, migration guides, release notes, LTS policy URLs + docs request tags
├── guide-reader-prompt.md # prompt for the sub-agents that read the guides
└── skill-feedback.md # how to report wrong/missing guidance
.claude-plugin/ # Claude Code plugin + marketplace manifests
.github/ISSUE_TEMPLATE/ # skill-feedback issue form
scripts/ # release process + docs request tags (rule templates, update script)
tests/ # tests of the scripts + checks of the docs URLs in the skills
```
The skills are **version-agnostic by design**: they carry durable, universal
knowledge and point the agent at the live docs for anything version-specific.
## Staying current
The skills work standalone, but are more effective with live docs access:
- **Docs:** <https://ckeditor.com/docs/ckeditor5/latest/>
- **`llms-full.txt`** (<https://ckeditor.com/docs/llms-full.txt>) — the guides as
one fetchable text bundle (no API reference); and **`llms.txt`**
(<https://ckeditor.com/llms.txt>) — a product overview (capabilities, lineup,
pricing) with links.
- **Kapa documentation MCP** (optional): semantic search over the docs — setup in
[`skills/ckeditor/references/documentation-access.md`](skills/ckeditor/references/documentation-access.md).
## Feedback
Found wrong, stale, or missing guidance? [Open an
issue](https://github.com/ckeditor/skills/issues/new?template=skill-feedback.yml)
with the **skill feedback** template. Agents are encouraged to file these (with
the user's awareness) when reality contradicts a skill.
## License
[MIT](LICENSE.md) © CKSource. CKEditor® is a trademark of [CKSource](https://cksource.com).
© CKEditor (CKSource) · MIT · ckeditor/skills