build123d-libs

Use when standard mechanical parts, fasteners, bearings, V-slot rails, T-nuts, wheels, or linear-motion parts are needed in Build123d CAD, and always before modeling a screw into a 3D-printed part — printed screw joints must come from this skill's kit, never hand-modeled.

Quality

79%

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 ./reference/replicator-original/me/build123d-libs/SKILL.md

Quality

Content

73%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 a well-structured, concise overview with a clear workflow and strong reference navigation. Its main weakness is that several referenced bundle files are missing, which undermines the progressive-disclosure promise.

Suggestions

Add the missing bundle files referenced in the Reference Index (kits/printed-screw-joint-v1/KIT.md, kits/vslot-2020-corner-composite-v1/KIT.md and recipe.py, and examples/*.py), or remove their rows so every linked path resolves.

Make the rejection feedback loop explicit as a validate-step (e.g. 'on ScrewJointNotApplicableV1, classify the connection free, then re-confirm the inventory entry is marked free') to lift workflow_clarity toward 5.

Tighten the heat-set-insert parenthetical into a one-line opt-in note and move the exception/strategy detail into the kit reference to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding of concepts Claude already knows; only the heat-set-insert parenthetical and the lengthy hard-constraint rationale border on over-explanation, keeping it just under anchor 5 at 4.	4 / 5
Actionability	Concrete entry points appear inline ("from screwjoint import make_screw_joint_v1", "export_step", the ScrewJointNotApplicableV1 rejection contract), but the deeper executable API is deferred to references, leaving a minor gap consistent with anchor 4.	4 / 5
Workflow Clarity	A clear 7-step sequence routes decisions explicitly ("Read references/decision-guide.md to choose...", "check the kit catalog before assembling") and includes a rejection-to-free feedback loop plus an inventory assertion checkpoint, though re-validation after fixes is only implied.	4 / 5
Progressive Disclosure	An excellent Reference Index table with a purpose column gives strong one-level navigation into the four references/ files, but six of the ten referenced paths (kits/* and examples/*) do not exist in the bundle, so navigation is not fully reliable and it falls between anchors 3 and 4.	3.5 / 5
	Total	15.5 / 20 Passed

Description

85%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 is explicit about both capability and trigger conditions and carves out a distinctive Build123d niche with a memorable hard constraint. It is slightly light on the number of distinct actions and could add library/package name triggers.

Dimension	Reasoning	Score
Specificity	Names many concrete part categories ("fasteners, bearings, V-slot rails, T-nuts, wheels, or linear-motion parts") and one concrete action ("printed screw joints must come from this skill's kit, never hand-modeled"), but the distinct actions are essentially two (use libraries, use the kit), so it sits between anchor 3 and 4.	3.5 / 5
Completeness	Explicitly answers both what (parts come from pre-installed libraries / the screw-joint kit) and when ("Use when standard mechanical parts... are needed... and always before modeling a screw into a 3D-printed part") with concrete trigger phrases, matching anchor 5.	5 / 5
Trigger Term Quality	Strong natural-term coverage ("fasteners, bearings, V-slot rails, T-nuts, wheels, linear-motion parts", "modeling a screw into a 3D-printed part") with synonyms, but library names and file extensions that users might also cite are absent, matching anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	A clear Build123d-specific niche plus the distinctive printed-screw-joint hard constraint gives minimal overlap with other skills, matching anchor 5.	5 / 5
	Total	17.5 / 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
relative_links	Relative link issues: 6 missing, 4 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: JimmyPang02/open-replicator
Path: reference/replicator-original/me/build123d-libs/SKILL.md
Commit: 18436cc

Reviewed: 1 day 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.