step-parts

Use when Replicator needs off-the-shelf STEP parts for screws, bearings, motors, servos, connectors, boards, rails, or other purchasable CAD components before creating placeholder geometry.

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 ./skills/step-parts/SKILL.md

Quality

Content

86%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.

A concise, highly actionable skill body with well-structured progressive disclosure and a real bundled script and reference. The main gap is the absence of an explicit error-recovery loop for failed checksum verification in the workflow.

Suggestions

Add a feedback step after sha256 verification (e.g., "If the checksum mismatches, re-download once; if it still fails, treat the source as unverified and ask for the real file").

Trim the repeated component-type list and the repeated "no placeholder geometry" directive to a single authoritative statement to tighten conciseness.

Make workflow step 6 ("Record the result...") concrete by naming the exact artifact/field to write, mirroring the provenance fields already listed in the Replicator Boundary section.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence (no explanations of what STEP/CAD is), with only minor repetition: the component-type list and the "no placeholder geometry" directive each reappear across the intro, boundary, and workflow sections.	4 / 5
Actionability	Provides copy-paste-ready examples for both interfaces — a concrete `cad.step_parts({...})` native call and real `download_step_part.py` CLI invocations covering query, id, and limit cases — plus a clearly enumerated options list.	5 / 5
Workflow Clarity	A clear 6-step sequence with explicit validation ("Verify sha256 when the API record provides it") and a retry-on-empty feedback step, but it lacks an explicit recovery loop for what to do when sha256 verification fails, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Well-organized overview sections with API detail offloaded to a clearly signaled, one-level-deep reference ("Read references/step-parts-api.md...") and a real bundled downloader script; no nested reference chains.	5 / 5
	Total	18 / 20 Passed

Description

73%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.

A well-targeted description with explicit trigger guidance and a distinct niche, weakened only by a lightness of explicit action verbs and missing file-extension synonyms. It reads mostly as a "when" clause with the "what" implied rather than crisply stated.

Suggestions

Lead with a concrete action clause (e.g., "Searches and downloads off-the-shelf STEP parts...") before the "Use when" trigger so the "what" is explicit.

Add file-extension synonyms such as ".step" and ".stp" to broaden natural trigger coverage.

Name 2-3 concrete actions (search, download, verify checksum) to lift specificity from 1-2 actions to several.

Dimension	Reasoning	Score
Specificity	Names the domain richly ("off-the-shelf STEP parts for screws, bearings, motors, servos, connectors, boards, rails") and gives one concrete behavioral directive ("before creating placeholder geometry"), but lists no explicit multi-action verbs like search/download/verify, so it stops at the 1-2 concrete actions anchor.	3 / 5
Completeness	Has an explicit "Use when..." trigger with concrete component phrases (the "when") and an implied action of supplying real STEP parts instead of placeholders (the "what"), but the "what" is folded into the trigger clause rather than crisply stated as a leading action list.	4 / 5
Trigger Term Quality	Strong natural-term coverage ("screws, bearings, motors, servos, connectors, boards, rails") that users would actually say, but it omits file extensions (.step/.stp) and synonyms, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear, narrow niche (purchasable CAD STEP parts within Replicator) with distinct component-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JimmyPang02/open-replicator
Path: skills/step-parts/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.