Name: builderio
Rating: 59.2 (1 reviews)
Author: membranedev

builderio

Builder.io integration. Manage data, records, and automate workflows. Use when the user wants to interact with Builder.io data.

Quality

68%

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/builderio/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 commands and a well-validated connection workflow including feedback loops. Its main weaknesses are mild verbosity in the intro and a slightly loose step-numbering scheme.

Suggestions

Trim the opening paragraph to one line about Builder.io being a visual content platform, and drop the "so you can focus on the integration logic rather than auth plumbing" aside.

Replace the ambiguous "skip to Step 2" / "1b" labels with a consistent numbered sequence (1. Install, 2. Authenticate, 3. Connect, 4. Wait for READY, 5. Search/run actions).

Consider moving the popular-actions and proxy-flag tables into a reference file referenced from SKILL.md to tighten the overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but includes unnecessary explanation Claude doesn't need ("Builder.io is a visual development platform that allows developers and marketers..." and "so you can focus on the integration logic rather than auth plumbing"), matching anchor 3 rather than the lean anchor 4.	3 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request) plus concrete action-key and proxy-flag tables, matching anchor 5's fully executable, common-case-covering guidance.	5 / 5
Workflow Clarity	There is a clear install→auth→connect→poll→search→run→proxy sequence with explicit state-based validation (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the "skip to Step 2" reference and "1b" subsection leave the numbering slightly loose, matching anchor 4.	4 / 5
Progressive Disclosure	The single file is well organized into clearly labeled sections with no nested references, but it runs ~150 lines with inlined action and flag tables that could be split into reference files, matching anchor 4 rather than the cleanly-split anchor 5.	4 / 5
	Total	16 / 20 Passed

Description

62%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 cleanly states both the capability and an explicit use-when trigger anchored on the Builder.io brand, giving it solid completeness and distinctiveness. Its weakness is generic action verbs and thin trigger-term coverage, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs with concrete Builder.io actions, e.g. "Retrieve content entries and models, get rendered HTML, and search content by URL or text."

Expand the use-when trigger with natural variations users might say, e.g. "Use when the user wants to read Builder.io content, fetch models, or get SSR HTML for a page."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Builder.io domain plus a few actions, but the verbs are generic rather than concrete (cf. "extract text, fill forms"), matching anchor 3 and falling short of anchor 4's specific action list.	3 / 5
Completeness	Both what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Builder.io data") are present, but the when clause is a single trigger and not comprehensive enough for anchor 5.	4 / 5
Trigger Term Quality	The main natural trigger is the brand term "Builder.io" plus "data"/"records"/"workflows" in "interact with Builder.io data", but common variations and synonyms are missing, matching anchor 3 rather than the comprehensive coverage of anchor 4.	3 / 5
Distinctiveness Conflict Risk	Explicit "Builder.io integration" branding pins a clear niche with minimal conflict risk, but the generic action phrasing ("manage data, records, automate workflows") leaves minor overlap with general data-management skills, matching anchor 4.	4 / 5
	Total	14 / 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/builderio/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.