cots-parts

Instantiate catalog-backed COTS parts and validate metadata, placement, and ownership in build123d workflows.

2|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/MRiabov/Problemologist-AI --skill cots-parts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cots-parts
Source: https://github.com/MRiabov/Problemologist-AI/tree/main/.agents/skills/cots-parts
Command: npx skills add https://github.com/MRiabov/Problemologist-AI --skill cots-parts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Catalog-backed COTS part modeling and validation guidance for Problemologist. Use when a task involves motors, off-the-shelf parts, benchmark fixtures, or translating declared COTS components into build123d geometry and handoff artifacts.

Core Features & Use Cases

  • Preserve PartMetadata.cots_id, the part label, and provenance on the instance.
  • Separate geometry from motion: the motor body defines fit and frame, while joint or control contracts define actuation.
  • Benchmark-owned fixtures are read-only context; engineer-owned parts are validated and priced with ownership.

Quick Start

Instantiate a catalog-backed COTS component in authored geometry after construction and validate its metadata, placement, and ownership.

Frequently Asked Questions about cots-parts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve COTS part metadata when generating build123d CAD geometry?▼

Instantiate catalog-backed COTS components after constructing authored geometry, then validate that PartMetadata.cots_id, part labels, and provenance are correctly attached to the instance for downstream handoff.

What is the correct way to separate motor geometry from motion in CAD validation?▼

Separate geometry from motion by using the motor body strictly to define fit and frame, while assigning actuation to joint or control contracts, ensuring clean validation of catalog-backed COTS parts.

How do I validate off-the-shelf motor placement in a build123d workflow?▼

Validate off-the-shelf motor placement by instantiating the catalog-backed COTS component within authored geometry, then checking its metadata, placement correctness, and ownership pricing against benchmark fixtures.

Can I modify benchmark-owned fixtures when validating COTS parts?▼

Benchmark-owned fixtures function as read-only context and cannot be modified; only engineer-owned parts are validated, priced, and managed with full ownership during the COTS modeling workflow.

When do I need to translate declared COTS components into build123d geometry?▼

Translate declared COTS components into build123d geometry when a task involves motors, off-the-shelf parts, or benchmark fixtures requiring geometry generation, metadata validation, and handoff artifact creation.