io-formats

Validate STEP file imports, exports, and generated fixtures for solid modeling kernels.

20|3|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/andymai/brepkit --skill io-formats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: io-formats
Source: https://github.com/andymai/brepkit/tree/main/.claude/skills/io-formats
Command: npx skills add https://github.com/andymai/brepkit --skill io-formats

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Ensures that STEP files are correctly imported and exported, validates writer output, captures real files for fixture generation, and assists in extending format support.

Core Features & Use Cases

  • STEP Import Validation: Checks STEP file imports for errors and issues, identifies dropped solids, NURBS where analytical was expected, and more.
  • Writer Conformance Testing: Ensures the integrity of writer outputs when STEP files are exported.
  • Real File Fixtures: Captures and validates STEP files for accurate fixture generation from real-world applications.
  • Format Support Expansion: Assists in adding or extending file format support for various import/export functionalities.

Quick Start

Utilize the io-formats skill to analyze a STEP file import, validate the geometry integrity, and perform the heal-after-import if necessary.

Frequently Asked Questions about io-formats

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

FAQPage Schema
How do I validate STEP file imports for dropped solids or NURBS conversion errors?

Validating STEP file imports involves checking for dropped solids and unexpected NURBS surfaces by analyzing topology and geometry integrity. It identifies issues during parsing and performs heal-after-import if necessary.

What is the best way to verify STEP file exports and writer output conformance?

STEP file export verification requires writer conformance testing to ensure output integrity. It checks exported file structure and topology manipulation to confirm the solid modeling kernel accurately wrote the geometry.

How do I capture real-world STEP files for fixture generation?

Capturing real-world STEP file fixtures involves importing actual application files to validate structure and topology. It generates accurate test fixtures by verifying file parsing and geometry integrity against expected analytical surfaces.

Can I use this to extend file format support for solid modeling I/O operations?

Extending file format support for solid modeling I/O operations is supported by assisting in adding or extending import and export functionalities. It requires comprehensive knowledge of file parsing, topology manipulation, and format structure.

Why does my STEP file import show NURBS where analytical geometry was expected?

STEP file imports showing NURBS where analytical geometry was expected indicate a parsing or topology conversion issue. Validation identifies these discrepancies during geometry integrity checks and can trigger heal-after-import to correct the surfaces.