CtrlK
BlogDocsLog inGet started
Tessl Logo

cad-review

Independently audit one complete committed CAD build using cad.look image evidence and cad.inspect geometry facts. Use only for the Host-owned CAD handoff review that returns prioritized P0/P1 issues as ordinary text; do not use for CAD editing, finite-element analysis, physical load certification, or export.

75

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 crisp, well-structured instruction-only skill: lean, concrete, and easy to follow, with a clear output contract and boundary guidance. The only weakness is workflow_clarity, where an explicit validation/checkpoint step would push it to a 5.

Suggestions

Add an explicit verification checkpoint in the workflow (e.g. a step that confirms every suspected problem is backed by cited image evidence before composing the report).

Consider a short pre-report self-check (each finding has both an imagePath/view citation and a clear P0/P1 label) to close the validation gap.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line (evidence-class distinction, workflow, P0/P1 definitions, output format) earns its place.

5 / 5

Actionability

Highly actionable instruction-only guidance with concrete tool parameters ('pass them as focus', 'isolate with context: "ghost"', 'hide the enclosing part', 'cite the exact imagePath and view') and a precise output contract; absence of code is appropriate for this audit process.

5 / 5

Workflow Clarity

A clear 8-step sequence with conditional refinement ('decide where closer evidence is needed', 'zoom only if the first focused view is still too wide') and explicit terminal states, but it lacks an explicit validate-then-proceed checkpoint, leaving minor validation gaps.

4 / 5

Progressive Disclosure

Well under 50 lines with no need for external references; the body is cleanly organized into an intro, a Workflow section, a no-findings terminal state, and a boundary note, which is sufficient structure for a skill this size.

5 / 5

Total

19

/

20

Passed

Description

92%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 tight, highly specific description that nails what, when, and distinctiveness, with strong negative-scope boundary guidance. The only soft spot is trigger-term naturalness, since several terms are internal tool/host jargon.

Suggestions

Add a user-natural trigger phrase (e.g. 'Use when asked to review or audit a CAD build for handoff') alongside the 'Host-owned CAD handoff review' phrasing.

Consider mentioning common synonyms like 'review', 'check', or 'sign-off' so the description matches how a user would phrase the request.

DimensionReasoningScore

Specificity

Names concrete actions with specific tools ('audit one complete committed CAD build using cad.look image evidence and cad.inspect geometry facts') and a concrete output ('returns prioritized P0/P1 issues as ordinary text'), giving comprehensive coverage of the narrow audit domain.

5 / 5

Completeness

Explicitly answers both what (audit a CAD build, return P0/P1 issues as text) and when ('Use only for the Host-owned CAD handoff review'), with concrete trigger phrasing plus a negative-scope clause.

5 / 5

Trigger Term Quality

Good natural-term coverage ('audit', 'CAD build', 'CAD handoff review', 'P0/P1 issues') but tool names like cad.look/cad.inspect and 'Host-owned' are internal jargon rather than phrases a user would naturally say, leaving a few natural synonyms missing.

4 / 5

Distinctiveness Conflict Risk

The explicit negative scope ('do not use for CAD editing, finite-element analysis, physical load certification, or export') carves a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
JimmyPang02/open-replicator
Reviewed

Table of Contents

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.