Tiptap integration: build rich-text editors with AI assistance
The official Tiptap team's skill for agents — integrate the headless rich-text editor correctly: version pinning, docs-first grounding, and feature recipes from collaboration to AI toolkits
- What
- The official Tiptap team's skill for agents — integrate the headless rich-text editor correctly: version pinning, docs-first grounding, and feature recipes from collaboration to AI toolkits
- Cost
- Free
- Needs
- git, node/npm, and a project where you want a rich-text editor — the skill is guidance the agent follows (docs + source grounding discipline), not software the agent installs for you
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @ueberdosis's official tiptap skill (authored by the Tiptap team itself): instructions for coding agents to integrate and work with the Tiptap headless rich-text editor. The core discipline: never guess or invent patterns — ground every decision in the Tiptap docs and source (docs are fetched as Markdown by appending .md to any tiptap.dev/docs URL; llms.txt lists every page; read installed source from node_modules/@tiptap/*; clone only shallowly for demos you can't get otherwise). Best practices: resolve the latest stable version with npm view, pin all monorepo extension packages to one version line (never mix majors, upgrade Tiptap 2 projects first), resolve pro packages from the registry (never from @tiptap/core), set immediatelyRender: false for SSR, default to the Composable API for React. Feature recipes with doc links: real-time collaboration (Y.Doc + Collaboration extension + TiptapCollabProvider with Cloud appId/token), comments, tracked changes, import/export (DOCX, PDF, Markdown), the AI Toolkit (agentic document work, server-side default), basic AI generation, version history, snapshot compare, pages. Honest caveats: real-time collaboration runs on Tiptap Cloud (free tier exists, paid tiers for production scale — get the appId/token from the Cloud dashboard) and some pro extensions come through a private npm registry (see the pro-extensions guide); retired AI extensions (AI Agent, AI Changes, AI Suggestion, AI Assistant) must not be implemented from the deprecated docs. MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: git, node/npm, and a project where you want a rich-text editor — the skill is guidance the agent follows (docs + source grounding discipline), not software the agent installs for you Install "Tiptap integration: build rich-text editors with AI assistance" for me. It gives my agent the official Tiptap team's skill: docs-first integration (fetch docs as Markdown from tiptap.dev/docs, read node_modules source, shallow-clone demos only when needed), best practices (stable version resolution, single version line pinning, no major mixing, SSR immediatelyRender:false, Composable API for React), and feature recipes with doc links (real-time collaboration, comments, tracked changes, import/export, AI Toolkit, basic AI generation, version history, snapshot compare, pages). MIT-licensed. Repository: https://github.com/ueberdosis/tiptap/blob/main/skills/tiptap/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tiptap". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. npm install @tiptap/core and the extensions for your framework; set up a Tiptap Cloud account if you want real-time collaboration). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.