freecad-automation-extract-geometry-properties

Sub-skill of freecad-automation: Extract Geometry Properties (+2).

5 stars

Best use case

freecad-automation-extract-geometry-properties is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Sub-skill of freecad-automation: Extract Geometry Properties (+2).

Teams using freecad-automation-extract-geometry-properties should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/extract-geometry-properties/SKILL.md --create-dirs "https://raw.githubusercontent.com/vamseeachanta/workspace-hub/main/.agents/skills/_archive/engineering/cad/freecad-automation/extract-geometry-properties/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/extract-geometry-properties/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How freecad-automation-extract-geometry-properties Compares

Feature / Agentfreecad-automation-extract-geometry-propertiesStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Sub-skill of freecad-automation: Extract Geometry Properties (+2).

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Extract Geometry Properties (+2)

## Extract Geometry Properties


```python
import FreeCAD
import Part

def extract_geometry_properties(doc_path):
    """Extract geometric properties from FreeCAD document."""
    doc = FreeCAD.openDocument(doc_path)
    results = {}

    for obj in doc.Objects:

*See sub-skills for full details.*

## Export Formats and CLI


```bash
# Export STEP from command line
freecadcmd -c "
import FreeCAD, Part
doc = FreeCAD.openDocument('model.FCStd')
Part.export(doc.Objects, 'output.step')
"

# Export STL
freecadcmd -c "
import FreeCAD, Mesh
doc = FreeCAD.openDocument('model.FCStd')
Mesh.export(doc.Objects, 'output.stl')
"
```

## Parse STEP/IGES Output Metadata


```python
import Part

def parse_export_stats(export_path):
    """Parse exported file and return statistics."""
    shape = Part.read(export_path)
    return {
        "solids": len(shape.Solids),
        "shells": len(shape.Shells),
        "faces": len(shape.Faces),

*See sub-skills for full details.*

Related Skills

llm-wiki-source-extraction-coverage

5
from vamseeachanta/workspace-hub

Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.

sodir-data-extractor

5
from vamseeachanta/workspace-hub

Extract and process Norwegian Petroleum Directorate field and production data from SODIR

bsee-data-extractor

5
from vamseeachanta/workspace-hub

Extract and process BSEE (Bureau of Safety and Environmental Enforcement) data including production, WAR (Well Activity Reports), and APD (Application for Permit to Drill) data. Use for querying production data, well activities, drilling permits, completions, and workovers by API number, block, lease, or field with automatic data normalization and caching.

taxact-browser-automation-patterns

5
from vamseeachanta/workspace-hub

Patterns for automating TaxAct Business online (Ionic SPA) via Chrome browser MCP tools — field interaction, navigation, shadow DOM handling

portable-baseline-pattern-extraction

5
from vamseeachanta/workspace-hub

Extract and separate portable baseline config from machine-specific overrides in multi-environment projects

handle-pdf-download-popups-in-automation

5
from vamseeachanta/workspace-hub

Recover when PDF download buttons open inaccessible popups; fall back to capturing structured data instead

handle-browser-automation-financial-site-blocks

5
from vamseeachanta/workspace-hub

Workflow for working around Chrome extension blocks on financial sites during data collection tasks

extract-skills-from-hermes-sessions

5
from vamseeachanta/workspace-hub

Automatically analyze Codex session transcripts to identify and extract reusable skills using LLM analysis via OpenRouter

extract-skills-from-Codex-sessions

5
from vamseeachanta/workspace-hub

Automatically extract reusable skills from Codex session transcripts using LLM analysis and wire them into a Stop hook

extract-and-archive-tax-summary-data

5
from vamseeachanta/workspace-hub

Capture structured tax return summaries as YAML when PDF downloads are blocked or inaccessible

github-issue-automation-evidence-fields

5
from vamseeachanta/workspace-hub

Use when building GitHub issue classifiers, dashboards, closeout verifiers, or queue/report automation that depends on comments, approval evidence, or linked PR handoff state.

extract-learnings-to-issues

5
from vamseeachanta/workspace-hub

Extract unstructured user reflections and learnings, distill core themes, route insights to existing GitHub issues as contextual comments rather than creating duplicates.