tiptap
Build rich text editors with Tiptap - headless editor framework with React and Tailwind v4. Covers SSR-safe setup, image uploads, prose styling, and collaborative editing. Use when creating blog editors, comment systems, or Notion-like apps, or troubleshooting SSR hydration errors, typography issues, or image upload problems.
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that excels across all dimensions. It provides specific capabilities, uses natural trigger terms users would actually search for, includes an explicit 'Use when' clause with concrete scenarios, and carves out a distinct niche around Tiptap-based rich text editing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build rich text editors', 'SSR-safe setup', 'image uploads', 'prose styling', and 'collaborative editing'. Also mentions specific technologies (Tiptap, React, Tailwind v4). | 3 / 3 |
Completeness | Clearly answers both what (build rich text editors with specific capabilities) AND when (explicit 'Use when' clause with concrete scenarios like 'creating blog editors' and troubleshooting specific error types). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'rich text editors', 'blog editors', 'comment systems', 'Notion-like apps', 'SSR hydration errors', 'typography issues', 'image upload problems', plus framework names like 'Tiptap', 'React', 'Tailwind'. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche targeting Tiptap specifically, with clear triggers around rich text editing, SSR hydration, and the specific framework combination. Unlikely to conflict with general React or Tailwind skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent code examples and clear workflows. The main weakness is verbosity - the 'Why this matters' explanations, detailed issue descriptions, and inline content that could be in reference files inflate the token count. The critical SSR warning and setup patterns are well-highlighted, making this immediately useful despite its length.
Suggestions
Move the 7 Known Issues section to references/common-errors.md and keep only a brief summary with links in the main skill
Remove 'Why this matters' explanations - Claude understands why peer dependencies and typography plugins are needed
Move the complete package.json versions block to templates/package.json and reference it instead of duplicating
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations (e.g., 'Why this matters' sections explaining obvious concepts, verbose issue descriptions). The content could be tightened by removing explanatory prose Claude already knows while keeping the critical warnings and code examples. | 2 / 3 |
Actionability | Excellent actionable content with fully executable code examples, specific npm commands, copy-paste ready configurations, and concrete patterns. Every major section includes working code that can be directly used. | 3 / 3 |
Workflow Clarity | Clear 3-step setup process with explicit validation checkpoints (the setup checklist at the end), numbered sequences for multi-step operations, and explicit error prevention guidance. The image upload pattern shows a clear 4-step workflow with feedback loop. | 3 / 3 |
Progressive Disclosure | References templates and reference files appropriately, but the main document is quite long (~600 lines) with content that could be split out (e.g., the 7 known issues section, advanced topics, complete package.json). The structure is good but the document itself is monolithic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (693 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.