Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From buildbrain
Extract data from IFC building models. Accepts element types (door, wall, window, slab, roof, etc.) and optional property filters. Translates natural language queries into CLI commands. Results saved to output/ for cross-validation.
npx claudepluginhub thebrownproject/buildbrainHow this skill is triggered — by the user, by Claude, or both
Slash command
/buildbrain:ifc-extractThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Extract building element data from IFC models. For full CLI command syntax, flags, type shorthands, and natural language translation tables, see `/cli-tools`.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
Share bugs, ideas, or general feedback.
Extract building element data from IFC models. For full CLI command syntax, flags, type shorthands, and natural language translation tables, see /cli-tools.
If no file path provided:
ls data/*.ifc 2>/dev/null
Multiple files → ask user. No files → tell user to place IFC file in data/.
Scripts are at skills/cli-tools/scripts/ifc_extract.py. Always include --save.
python skills/cli-tools/scripts/ifc_extract.py <file.ifc> <command> [args] --save
Use /cli-tools to look up the correct command for the user's request. Common patterns:
| User says | Command |
|---|---|
| "show me all doors" | list door --save |
| "fire-rated doors" | query door --property Pset_DoorCommon.FireRating --not-null --save |
| "external walls" | query wall --property Pset_WallCommon.IsExternal --value true --save |
| "how many windows per level" | quantities window --group-by storey --save |
| "what's in this model" | summary --save |
| "data quality check" | validate --save |
quantities commandlist door: "Filter for fire-rated doors? Check quantities per level?"summary: "Which element type to explore?"/pdf-extract to find the matching PDF schedule?"quantities for counts, areas, volumes.--save for downstream use by /cross-validate and /report.