create-bubble
Create a new Bubble integration for Bubble Lab following all established patterns and best practices from CREATE_BUBBLE_README.md
70
55%
Does it follow best practices?
Impact
100%
2.94xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/create-bubble/SKILL.mdQuality
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a specific domain (Bubble integrations for Bubble Lab) but is otherwise thin. It lacks a 'Use when...' clause, does not enumerate concrete actions beyond 'create', and relies on an external document (CREATE_BUBBLE_README.md) rather than being self-contained. It would be difficult for Claude to reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'new Bubble integration', 'add integration to Bubble Lab', 'scaffold Bubble connector'.
List specific concrete actions the skill performs, e.g., 'Scaffolds integration files, configures API endpoints, registers the integration in the manifest, and sets up authentication patterns'.
Include natural language variations a user might use, such as 'plugin', 'connector', 'add a new Bubble app integration'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | It names a specific domain ('Bubble integration for Bubble Lab') and a single action ('Create'), but does not list multiple concrete actions or elaborate on what creating an integration entails beyond referencing an external README. | 2 / 3 |
Completeness | It describes what (create a Bubble integration) but has no explicit 'Use when...' clause or equivalent trigger guidance. Per the rubric, a missing 'Use when' clause caps completeness at 2, and the 'what' itself is also thin, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes domain-specific terms like 'Bubble integration' and 'Bubble Lab' which are relevant but niche. Missing common natural language variations a user might say (e.g., 'add a new integration', 'connect to Bubble', 'plugin', 'connector'). | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Bubble Lab' and 'Bubble integration' provides some specificity, but 'integration' is a broad term that could overlap with other integration-related skills. The reference to a specific README helps somewhat but isn't enough for a clear niche. | 2 / 3 |
Total | 7 / 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 for a complex multi-step integration task. Its main strength is the precise enumeration of all 12 registration locations and concrete code templates. The primary weakness is that it's quite lengthy and could benefit from offloading some detailed templates and patterns to referenced files, especially since it already points to CREATE_BUBBLE_README.md.
Suggestions
Consider moving the detailed integration flow test template (Step 6) and schema best practices to referenced files, keeping only a brief summary and link in the main skill.
Remove slight redundancy between the Quality Checklist and instructions already stated in earlier steps (e.g., '.describe() on ALL fields' is mentioned in Step 3, Key Patterns, and the checklist).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long but most content is necessary for the complex multi-step registration process. However, some sections like the template code in Step 6 and the type safety patterns could be more concise or deferred to the referenced CREATE_BUBBLE_README.md, and there's some redundancy between the quality checklist and inline instructions. | 2 / 3 |
Actionability | The skill provides concrete folder structures, executable TypeScript code templates, specific file paths for all 12 registration locations, and exact bash commands for verification. The guidance is highly specific and copy-paste ready. | 3 / 3 |
Workflow Clarity | The 8-step workflow is clearly sequenced with explicit verification commands in Step 8, a quality checklist before completion, and the requirement to update all 12 registration locations is enumerated precisely. The checklist serves as a validation checkpoint before finishing. | 3 / 3 |
Progressive Disclosure | The skill references CREATE_BUBBLE_README.md and specific reference implementations for deeper study, which is good. However, the skill itself is quite long and some content (like the full integration flow test template and detailed schema best practices) could be split into separate referenced files rather than inlined. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- bubblelabai/BubbleLab
- Commit
1a11b95
- 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.