Name: letsbuild
Rating: 61.6 (1 reviews)
Author: membranedev

letsbuild

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

Quality

72%

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/letsbuild/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 is highly actionable with concrete, copy-paste-ready commands and a clear connection state machine. The main gaps are minor trimmable prose and an implied rather than explicitly numbered end-to-end workflow.

Suggestions

Trim the introductory marketing sentence and filler lines like 'Use action names and parameters as needed.' to tighten conciseness.

Add an explicit numbered quick-start sequence (install → login → connection ensure → action list → action run) so the full workflow is unambiguous.

Consider moving the proxy flag table and detailed clientAction state handling into a short referenced file to reduce top-level length.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, leading with executable commands and state-handling that Claude genuinely needs, with only minor trimmable prose such as the marketing-style intro and 'Use action names and parameters as needed.', placing it just below the fully-lean 5.	4 / 5
Actionability	It provides copy-paste-ready bash commands for every stage (install, login, connection ensure/get, action list, action run, request) plus a flag table, matching 'fully executable; copy-paste ready code or commands; specific examples cover the common cases'.	5 / 5
Workflow Clarity	The connection sub-flow is clearly sequenced with explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a poll-again feedback loop, but the overall install→auth→connect→search→run flow is implied rather than a single explicit numbered sequence, so it falls short of 5.	4 / 5
Progressive Disclosure	The content is well-organized into clearly labeled sections in a single file with no external bundle references present, which is appropriate for this CLI integration guide; because it exceeds 50 lines it does not qualify for the auto-5 simple-skill exception, leaving it at 'good structure; most content appropriately placed'.	4 / 5
	Total	17 / 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 correctly pairs a what and a when and leverages a distinctive product name, but its capabilities and triggers are generic. Tightening the action list and adding concrete trigger phrases would lift specificity and completeness.

Suggestions

Replace generic verbs with concrete LetsBuild capabilities (e.g., 'create and track RFIs, submittals, and checklists') to raise specificity.

Expand the 'Use when...' clause with concrete trigger phrases users would say (e.g., 'Use when the user wants to create RFIs, manage submittals, or track construction issues in LetsBuild').

Add common synonyms or feature names (RFI, submittal, checklist, project) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the LetsBuild domain and a couple of actions ('Manage data, records, and automate workflows'), but those actions are generic rather than concrete capabilities, matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor and not reaching the specific-action list of 4.	3 / 5
Completeness	It provides both a 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with LetsBuild data'), but the trigger is generic so it falls short of the concrete trigger phrases required for 5.	4 / 5
Trigger Term Quality	The natural keyword 'LetsBuild' appears in an explicit trigger clause, but coverage is thin with no synonyms or common variations beyond 'data', fitting 'some relevant keywords but missing common variations' rather than the broader coverage of 4.	3 / 5
Distinctiveness Conflict Risk	Binding everything to the named product 'LetsBuild' gives a clear niche with low conflict risk, but the generic action phrasing ('manage data, records') leaves minor overlap with other data/integration skills, so it is not the minimal-risk 5.	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/letsbuild/SKILL.md
Commit: f484c82

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