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

buildbuddy

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

Quality

73%

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/buildbuddy/SKILL.md

Quality

Content

88%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 content is highly actionable with fully executable commands, a clearly sequenced connection workflow backed by explicit state-validation checkpoints and feedback loops, and good section organization, with only minor conciseness and progressive-disclosure refinements possible.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste-ready bash commands and tight tables, with only minor trims needed (the platform-intro paragraph and "It's used by developers and DevOps engineers..." add little Claude does not infer), fitting the "efficient; minor instances of over-explanation" anchor; it does not reach 5 because of that padding.	4 / 5
Actionability	Concrete, executable commands cover install, login, connection ensure/get with --wait, action list/run with --input, and proxy requests with a full flag table, matching the "fully executable; copy-paste ready; specific examples cover common cases" anchor.	5 / 5
Workflow Clarity	The connection workflow is explicitly sequenced with state-based validation checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a feedback loop (poll again after the user completes the action), matching the "clear sequence with explicit validation steps and feedback loops for error recovery" anchor.	5 / 5
Progressive Disclosure	The body is well-organized into clear sections (Overview, Working with BuildBuddy, Popular actions, Best practices) with no nested references, and no bundle files exist to split further; it stays at 4 rather than 5 because some dense CLI reference content (the proxy flag table, clientAction fields) could live in a referenced file, matching the "good structure; minor organization gaps" anchor.	4 / 5
	Total	18 / 20 Passed

Description

57%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 includes both a what and an explicit when-clause and is tied to a distinct product, but its capability list relies on generic verbs (manage, automate) rather than concrete BuildBuddy operations, limiting specificity and trigger-term coverage.

Suggestions

Replace generic verbs with concrete BuildBuddy actions, e.g. "Inspect builds and invocations, view test results, and monitor CI/CD pipelines".

Add natural trigger terms users would say, such as "build failures", "build logs", "test results", or "CI/CD pipelines".

Make the when-clause more specific, e.g. "Use when the user wants to inspect BuildBuddy builds, review invocations, or check test results."

Dimension	Reasoning	Score
Specificity	It names the domain ("Manage data, records, and automate workflows") but the actions are generic verbs rather than concrete operations, matching the "Names the domain but actions are minimal or generic" anchor; it does not reach 3 because no specific BuildBuddy operations (e.g. inspect builds, view test results) are listed.	2 / 5
Completeness	Both a "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with BuildBuddy data") are present, matching the anchor for having both with a when-clause that could be more specific; it falls short of 5 because the when-clause is generic rather than naming concrete triggers.	4 / 5
Trigger Term Quality	Relevant keywords appear ("BuildBuddy", "data", "records", "workflows", "interact with BuildBuddy data") but common variations and concrete trigger phrases (builds, invocations, test results, pipelines) are missing, fitting the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the named product BuildBuddy gives it a clear niche with low conflict risk, but the generic action list keeps it just below a clean 5, matching the "mostly distinct; minor overlap risk" anchor.	4 / 5
	Total	13 / 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/buildbuddy/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.