fillet-blend

Diagnose fillet and chamfer issues in CAD models by analyzing topology and engine implementations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill addresses common issues related to fillet and chamfer operations in CAD models, aiding in debugging and improving the quality of CAD outputs.

Core Features & Use Cases

  • Engine Identification: Diagnose which CAD engine is responsible for fillet and chamfer bugs.
  • v2 Walking Blend Debugging: Troubleshoot the walking blend engine for accurate and reliable results.
  • No-Op Detection: Avoid silent failures where the fillet or chamfer operation appears to succeed but doesn't change the model.
  • ** deprecated Code Evaluation**: Evaluate the safety of modifying deprecated fillet and chamfer code in v1 versions.
  • Use Case: When a fillet or chamfer operation produces unexpected results like free edges or an open shell, this skill helps pinpoint the issue and propose solutions.

Quick Start

Run the 'fillet-blend' skill to debug a fillet operation in your CAD model that is leaving free edges.

Frequently Asked Questions about fillet-blend

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

FAQPage Schema
Why does my CAD fillet operation leave free edges or an open shell?

Fillet operations can produce free edges or open shells due to topology issues or problematic CAD engine implementations. This skill diagnoses these failures by analyzing the model's topology and pinpointing the specific engine causing the unexpected fillet results.

How do I debug a CAD chamfer or fillet operation that silently fails without changing the model?

Silent fillet or chamfer failures, known as no-ops, occur when the operation appears successful but alters nothing. This skill detects no-op conditions by evaluating the walking blend process and verifying engine execution against the model topology.

How does the walking blend process work when applying fillets in CAD engines?

The walking blend process generates fillet geometry by traversing model edges sequentially. This skill troubleshoots the v2 walking blend engine, ensuring accurate topology traversal and reliable fillet generation across complex CAD model boundaries.

Can I safely modify deprecated fillet and chamfer code in v1 CAD engines?

Modifying deprecated v1 fillet and chamfer code carries risks of breaking existing model topology. This skill evaluates the safety of altering deprecated engine implementations, identifying potential pitfalls before you change legacy CAD operations.

How do I identify which CAD engine is causing fillet and chamfer bugs?

Identifying the buggy CAD engine requires analyzing the model's topology and tracing the fillet execution path. This skill isolates the problematic engine implementation by debugging the operation workflow and evaluating its output consistency.

What are the limitations of using automated debugging for CAD fillet operations?

Automated fillet debugging depends on accurate model topology analysis and clear engine implementation paths. This skill may face limitations diagnosing highly degraded geometry or undocumented custom engine behaviors that obscure the walking blend process.