Name: bubble
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bubble

Bubble integration. Manage Applications. Use when the user wants to interact with Bubble data.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/bubble/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable CLI commands and a clear, validated connection workflow, but it opens with unnecessary background on Bubble and keeps reference-style material inline. It is a strong, practical integration guide with light token waste.

Suggestions

Cut the opening "Bubble is a no-code development platform..." paragraph and the "so you can focus on the integration logic" aside; Claude already knows what Bubble is.

Move the full Popular actions table and the proxy flags table into a separate reference file (e.g. ACTIONS.md) and link to it, keeping only the key examples inline.

Fix the broken step labels: define an explicit "Step 2" and renumber the "1b" wait-for-ready subsection so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explains what Bubble is and who uses it, plus lines like "so you can focus on the integration logic rather than auth plumbing", which Claude does not need; the bulk of CLI guidance is efficient, so it is mostly efficient with some unnecessary explanation.	3 / 5
Actionability	Copy-paste-ready commands cover the common cases end-to-end (install, login, connection ensure, action list/run, request proxy) with explicit flags and placeholders, matching the fully-executable anchor.	5 / 5
Workflow Clarity	The connection flow is sequenced with an explicit feedback loop (poll until READY, handle CLIENT_ACTION_REQUIRED, surface CONFIGURATION_ERROR), but references like "Skip to Step 2" and "1b" lack a matching Step 1a/Step 2 label, leaving minor gaps.	4 / 5
Progressive Disclosure	The single SKILL.md is well-sectioned (overview, install, auth, connecting, searching, actions, proxy, best practices) with no nesting; it is not a 5 because the full action table and proxy flag reference could live in a one-level-deep reference file.	4 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

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 correctly answers both what and when in third person and is clearly distinct via the Bubble brand, but the capability list is generic and trigger-term coverage is narrow. It lands as a solid, somewhat thin description rather than a comprehensive one.

Suggestions

Replace the generic "Manage Applications" with 2-3 concrete Bubble actions (e.g., "Create and update records, trigger backend workflows, list data types") to lift specificity.

Expand trigger terms to include natural user phrasings like "Bubble app", "Bubble application", "Bubble data type", or "Bubble workflow".

Tighten the when-clause to reference concrete Bubble surfaces (apps, data types, API workflows) so the trigger is more actionable.

Dimension	Reasoning	Score
Specificity	"Manage Applications" names the Bubble domain with one concrete-but-generic action, matching the anchor that lists 1-2 actions without comprehensive coverage; not a 2 because an actual action is stated, not a 4 because coverage is thin and generic.	3 / 5
Completeness	It states a what ("Bubble integration. Manage Applications.") and an explicit when ("Use when the user wants to interact with Bubble data"), satisfying both; not a 5 because the what is generic and the trigger could list concrete Bubble surfaces.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Bubble data" surfaces the brand term and one phrase, but misses natural variations like "Bubble app", "Bubble application", or "Bubble workflow" that users would say.	3 / 5
Distinctiveness Conflict Risk	Naming the specific Bubble platform with a dedicated trigger ("interact with Bubble data") gives it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/bubble/SKILL.md
Commit: f484c82

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.