build-test

Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.

Quality

80%

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 ./plugins/_official/atoms/build-test/SKILL.md

Quality

Content

100%

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

The body is concise, concrete, and action-oriented with a clear convergence workflow and well-organized sections, meeting the rubric's top anchors across all dimensions for this simple skill.

Dimension	Reasoning	Score
Conciseness	Lean and efficient; every section earns its place, uses concrete tables and code blocks, and avoids explaining concepts Claude already knows.	3 / 3
Actionability	Provides concrete commands by framework, an executable output schema, a copy-paste-ready devloop JSONC wiring example, and a clear pointer to the implementing file.	3 / 3
Workflow Clarity	Sequences the atom after patch-edit with a gated 'until' convergence condition and enumerates anti-patterns, giving an explicit feedback loop (run until both signals pass or iterations hit 8).	3 / 3
Progressive Disclosure	For a short, single-purpose skill it is well-organized into focused sections with no external bundle files needed, so the body stands on its own with clear navigation.	3 / 3
	Total	12 / 12 Passed

Description

60%

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 is specific and action-oriented but omits explicit 'use when' trigger guidance, which caps completeness, and relies on some internal jargon that weakens trigger term quality and distinctiveness.

Suggestions

Add a 'Use when ...' clause stating when Claude should invoke this skill (e.g. after editing code in a code-migration run to verify the build).

Replace or gloss the internal jargon 'devloop convergence reads' with natural trigger phrasing a user would actually say.

Add a distinguishing phrase tying it to the critique/devloop pipeline to reduce overlap with generic test-runner skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('Run the project's build / typecheck / lint / test commands', 'emit the build.passing + tests.passing signals') rather than vague descriptions.	3 / 3
Completeness	Clearly answers 'what' it does, but provides no 'Use when...' clause or equivalent trigger guidance for when Claude should reach for it.	2 / 3
Trigger Term Quality	Includes 'build', 'typecheck', 'lint', 'test' which users would say, but lacks natural phrasings like 'run the tests' or 'check the build passes' and leans on internal jargon ('devloop convergence').	2 / 3
Distinctiveness Conflict Risk	Fairly specific to build/test signaling within a devloop, but generic terms like 'build' and 'test' could overlap with other dev-loop or test-runner skills.	2 / 3
	Total	9 / 12 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: nexu-io/open-design
Path: plugins/_official/atoms/build-test/SKILL.md
Commit: f2760fd

Reviewed: about 15 hours 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.