hamzaabduljabbar

AutoConst Cutsheet To Family — AI skill for Claude Code

AI community

Claude Code skill: manufacturer PDF cut sheet -> working Revit MEP family.

How to install AutoConst Cutsheet To Family

This entry records only its repository, not the path inside it, so there is no exact command to give. Open hamzaabduljabbar/autoConst-cutsheet-to-family and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What AutoConst Cutsheet To Family does

Claude Code skill: manufacturer PDF cut sheet -> working Revit MEP family. Real size, pipe/duct/electrical connectors, one type per model, every value traced to its page and verified in Revit

Alternatives in AI

Open Dots — Open-source, self-hosted AI agent workspace and alternative to OpenAI Dots, Meta Muse, Grok Bot, Instinct, Man 5.5k ★
Jcodemunch MCP — Cut AI token costs 95%+ on code exploration 2.6k ★
Cartographer — Claude Code plugin that maps and documents codebases of any size using parallel AI subagents 518 ★

README

Cut sheet → Revit family (Claude Code skill)

Give Claude a manufacturer cut sheet / submittal PDF. It builds a working Revit MEP family from it: the body at the real size, real pipe / duct / electrical connectors where the sheet puts them (with system and size), one family type per model in the sheet's table, and the sheet's data (capacity, flow, weight, electrical) as parameters. Every value is traced to its page and quote, and the family is checked inside Revit against the sheet.

![Titus fan coil: cut sheet in, Revit family out](docs/cutsheet-side-by-side.png)

Why

Manufacturers ship PDFs, not Revit families. A modeller rebuilds each one by hand in the Family Editor (template, reference planes, body, parameters, connectors, one type per model), usually 1-3 hours per family, or drops in a generic box that can't connect to pipes, ducts or circuits.

What it does

Step	What happens
1. Read	`read_pdf.py` writes the text and an image of every page. Claude reads both: the text gives the numbers, the drawing shows which face each connection comes out of
2. Spec	Claude writes `spec.json`: body, connectors, types and data, each value with page, quote and HIGH / MEDIUM / LOW confidence
3. Check	`check_spec.py` catches impossible specs (connector inside the body, side flipping between models, missing sizes) and any HIGH value whose numbers aren't on the page. It lists the LOW values and questions; Claude asks you before building
3b. Second reading	A separate Claude reads the same sheet without seeing the first spec. `cross_check.py` compares them value by value. Every disagreement is settled from the drawing (or asked) before anything is built
4. Build	`build_family.py` builds the family through the Revit API (parametric body, connectors, types) and loads it into the open project
5. Verify	`verify.py` places every type, measures what Revit built and compares it with the spec, then rolls back. The model is left unch