Name: holobuilder
Rating: 60.8 (1 reviews)
Author: membranedev

holobuilder

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

82%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 provides highly actionable, copy-paste-ready CLI commands and a clear workflow with a strong connection-state feedback loop. It is concise and well-structured, with only minor over-explanation and slightly inconsistent step numbering.

Suggestions

Tighten the few padded phrases (e.g. remove 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection').

Normalize the step numbering (label the connecting section 'Step 1' to match the '1b' and 'Step 2' references) and add an explicit output-verification note after running actions or proxy requests.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands and a tight proxy-options table, but includes minor over-explanation such as 'so you can focus on the integration logic rather than auth plumbing' and 'This is the fastest way to get a connection.' It is above the 3 anchor (mostly efficient) but not fully lean, so 4.	4 / 5
Actionability	Commands are fully executable and copy-paste ready (npm install, membrane login, connection ensure, action run with --input JSON, request proxy) with clearly marked placeholders covering the common cases. This matches the 5 anchor for fully executable, copy-paste ready guidance.	5 / 5
Workflow Clarity	The connect-to-poll-to-act sequence is clear and the connection state machine (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) provides an explicit feedback loop with retry-after-user-action. Minor validation gaps (no output verification after action run) and slightly loose step numbering ('Step 2' / '1b') keep it at 4 rather than 5.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) and is appropriately self-contained with no oversized reference dump requiring a separate file. No bundle files exist and none are needed, but the loose step numbering is a minor organization gap, so 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Description

61%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 has an explicit trigger clause and a clearly distinct niche, but its capability language is generic ('manage data, records, automate workflows') rather than naming concrete operations. It is functional but would benefit from more specific action verbs.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete HoloBuilder operations such as 'capture 360° site photos, annotate floorplans, and pull project progress data'.

Broaden trigger terms to include natural phrasings users might say, e.g. 'Use when the user wants to track construction site progress, review 360° photo documentation, or query HoloBuilder projects.'

Dimension	Reasoning	Score
Specificity	Names the domain ('HoloBuilder integration') but the actions 'Manage data, records, and automate workflows' are generic rather than concrete operations like extract, fill, or merge. It sits at the 'names domain but actions minimal/generic' anchor, below the 3 anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with HoloBuilder data') are present, and the 'Use when' clause is explicit so it is not capped at 3. The 'what' is generic, keeping it at 4 rather than 5.	4 / 5
Trigger Term Quality	The natural keyword 'HoloBuilder' appears and the trigger phrase 'Use when the user wants to interact with HoloBuilder data' is present, but coverage is limited to the single product name with no synonyms or variations. This matches the 3 anchor ('some relevant keywords but missing common variations').	3 / 5
Distinctiveness Conflict Risk	HoloBuilder is a specific named product (construction 360° documentation), giving it a clear niche with distinct triggers and minimal overlap with other skills. This matches the 5 anchor for a clear niche with distinct triggers.	5 / 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/holobuilder/SKILL.md
Commit: f484c82

Reviewed: 5 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.