[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FAEVQ3DP5EYSE85JSRCAVN":3,"skill-same:01M7FAEVQ3DP5EYSE85JSRCAVN":62},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7FAEVQ3DP5EYSE85JSRCAVN","ifcos-syntax-api",null,"Use when writing IfcOpenShell Python code that creates, modifies, or deletes IFC entities. Prevents the #1 AI mistake: using create_entity() or direct attribute assignment instead of ifcopenshell.api.run(). Covers all 30+ API modules, invocation patterns, parameter conventions, and the difference between api.run() and direct module calls. Keywords: ifcopenshell.api, api.run, create_entity, IFC, BIM, IfcWall, IfcSlab, API modules, ifcopenshell Python, how to use api.run, ifcopenshell tutorial.","lagzgabrielmuller-dot\u002Fkit-ingenieria-3d","lagzgabrielmuller-dot","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F333339260?v=4","01M7F985KYC0XB2XZ97B5YWH4C","01M7F985MHK8N2NVE4VAR5WBWS",0,"MIT","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: ifcos-syntax-api\ndescription: >\n  Use when writing IfcOpenShell Python code that creates, modifies, or deletes IFC entities.\n  Prevents the #1 AI mistake: using create_entity() or direct attribute assignment instead\n  of ifcopenshell.api.run(). Covers all 30+ API modules, invocation patterns, parameter\n  conventions, and the difference between api.run() and direct module calls.\n  Keywords: ifcopenshell.api, api.run, create_entity, IFC, BIM, IfcWall, IfcSlab, API modules, ifcopenshell Python, how to use api.run, ifcopenshell tutorial.\nlicense: MIT\ncompatibility: \"Designed for Claude Code. Requires IfcOpenShell Python library.\"\nmetadata:\n  author: OpenAEC-Foundation\n  version: \"1.0\"\n---\n\n# IfcOpenShell API Module System\n\n## Quick Reference\n\n### Critical Warnings\n\n- **ALWAYS** use `ifcopenshell.api.run()` or direct module calls for IFC mutations. NEVER modify entity attributes directly (e.g., `wall.Name = \"X\"`) — use `api.run(\"attribute.edit_attributes\", ...)` instead.\n- **ALWAYS** import `ifcopenshell.api` before calling any API function. The module uses lazy loading; functions are NOT available without this import.\n- **ALWAYS** pass the `file` (model) object as the first positional argument after the function name in `api.run()`.\n- **NEVER** invent API module or function names. There are exactly 35 modules — see the module table below. Hallucinated calls like `api.run(\"element.create\", ...)` or `api.run(\"wall.add\", ...)` do NOT exist.\n- **ALWAYS** use keyword arguments for all parameters after the model. Positional arguments beyond the model are NOT supported.\n- **NEVER** use `model.create_entity()` for production code. Use `api.run(\"root.create_entity\", ...)` — it generates GlobalIds, sets ownership, and validates predefined types automatically.\n- **ALWAYS** set up a complete project before creating elements: IfcProject → units → contexts → spatial hierarchy. See the bootstrap pattern below.\n- **NEVER** assume `products` parameters accept single elements. Since IfcOpenShell v0.8+, most relationship functions expect `products` as a **list**, not a single entity.\n\n### Decision Tree: Which API Module to Use\n\n```\nWhat do you need to do?\n├── Create\u002Fremove\u002Fcopy IFC entities?\n│   └── root (create_entity, remove_product, copy_class, reassign_class)\n│\n├── Build spatial hierarchy?\n│   ├── Project → Site → Building → Storey → Space?\n│   │   └── aggregate (assign_object, unassign_object)\n│   ├── Place elements in a storey\u002Fspace?\n│   │   └── spatial (assign_container, unassign_container)\n│   └── Reference element in multiple spaces?\n│       └── spatial (reference_structure, dereference_structure)\n│\n├── Add geometry to elements?\n│   ├── Set up representation contexts first?\n│   │   └── context (add_context — root context, then subcontexts)\n│   ├── Parametric wall\u002Fslab\u002Fbeam geometry?\n│   │   └── geometry (add_wall_representation, add_slab_representation,\n│   │       add_profile_representation)\n│   ├── Custom mesh geometry?\n│   │   └── geometry (add_mesh_representation)\n│   ├── Position element in 3D space?\n│   │   └── geometry (edit_object_placement)\n│   └── Connect geometry to element?\n│       └── geometry (assign_representation)\n│\n├── Set properties on elements?\n│   ├── Key-value metadata (name, fire rating, etc.)?\n│   │   └── pset (add_pset, edit_pset)\n│   └── Measurable quantities (length, area, volume)?\n│       └── pset (add_qto, edit_qto)\n│\n├── Assign materials?\n│   ├── Simple single material?\n│   │   └── material (add_material, assign_material)\n│   ├── Layered construction (walls, slabs)?\n│   │   └── material (add_material_set with IfcMaterialLayerSet, add_layer)\n│   ├── Profiled sections (beams, columns)?\n│   │   └── material (add_material_set with IfcMaterialProfileSet, add_profile)\n│   └── Composite (windows, doors)?\n│       └── material (add_material_set with IfcMaterialConstituentSet)\n│\n├── Assign\u002Fmanage types?\n│   └── type (assign_type, unassign_type, map_type_representations)\n│\n├── Edit entity attributes directly?\n│   └── attribute (edit_attributes)\n│\n├── Create openings\u002Fvoids?\n│   └── void (add_opening, add_filling)\n│\n├── Set up units?\n│   └── unit (assign_unit — defaults to SI)\n│\n├── Manage project file?\n│   └── project (create_file)\n│\n└── Other domains?\n    ├── Classification → classification\n    ├── Groups → group\n    ├── Layers (CAD) → layer\n    ├── Visual styles → style\n    ├── Cost management → cost\n    ├── Scheduling (4D) → sequence\n    ├── MEP systems → system\n    ├── Structural analysis → structural\n    ├── Documents → document\n    ├── Constraints → constraint\n    ├── Resources → resource\n    ├── Owner\u002Factors → owner\n    ├── Profiles → profile\n    ├── Nesting → nest\n    ├── Boundaries → boundary\n    ├── Libraries → library\n    ├── Drawing\u002Fannotations → drawing\n    ├── Georeference → georeference\n    ├── Grid → grid\n    ├── Infrastructure alignment → alignment\n    ├── Coordinate geometry → cogo\n    ├── Features → feature\n    └── Property set templates → pset_template\n```\n\n---\n\n## Essential Patterns\n\n### Pattern 1: Two Equivalent Invocation Styles\n\n```python\n# IfcOpenShell v0.8+: both styles produce identical results\n\nimport ifcopenshell\nimport ifcopenshell.api\n\nmodel = ifcopenshell.file(schema=\"IFC4\")\n\n# Style A: api.run() with dot-notation string (original, most documented)\nwall = ifcopenshell.api.run(\"root.create_entity\", model, ifc_class=\"IfcWall\", name=\"Wall 1\")\n\n# Style B: Direct module call (shorter, IDE-friendly)\nwall = ifcopenshell.api.root.create_entity(model, ifc_class=\"IfcWall\", name=\"Wall 1\")\n```\n\n**ALWAYS** use one style consistently within a project. Both are correct. `api.run()` is more common in documentation and tutorials.\n\n### Pattern 2: Complete Project Bootstrap\n\n```python\n# IfcOpenShell: IFC4 (change version\u002Fschema for IFC2X3 or IFC4X3)\nimport ifcopenshell\nimport ifcopenshell.api\n\n# Step 1: Create file with proper headers (production use)\nmodel = ifcopenshell.api.run(\"project.create_file\", version=\"IFC4\")\n\n# Step 2: Create project entity\nproject = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcProject\", name=\"My Project\")\n\n# Step 3: Assign units (defaults to SI metric)\nifcopenshell.api.run(\"unit.assign_unit\", model)\n\n# Step 4: Create representation contexts\nmodel3d = ifcopenshell.api.run(\"context.add_context\", model, context_type=\"Model\")\nbody = ifcopenshell.api.run(\"context.add_context\", model,\n    context_type=\"Model\", context_identifier=\"Body\",\n    target_view=\"MODEL_VIEW\", parent=model3d)\n\n# Step 5: Build spatial hierarchy\nsite = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcSite\", name=\"Default Site\")\nbuilding = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcBuilding\", name=\"Building A\")\nstorey = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcBuildingStorey\", name=\"Ground Floor\")\n\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[site], relating_object=project)\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[building], relating_object=site)\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[storey], relating_object=building)\n```\n\n**ALWAYS** follow this sequence: file → project → units → contexts → spatial hierarchy. Skipping steps produces invalid IFC files.\n\n### Pattern 3: Create Element with Full Data\n\n```python\n# IfcOpenShell: IFC4 (requires completed bootstrap above)\n\n# Create wall type\nwall_type = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcWallType\", name=\"Standard Wall 200mm\")\n\n# Add material to type (best practice: assign to types, not occurrences)\nconcrete = ifcopenshell.api.run(\"material.add_material\", model,\n    name=\"Concrete C30\u002F37\", category=\"concrete\")\nifcopenshell.api.run(\"material.assign_material\", model,\n    products=[wall_type], material=concrete)\n\n# Create wall occurrence\nwall = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcWall\", name=\"Wall 001\")\n\n# Assign type\nifcopenshell.api.run(\"type.assign_type\", model,\n    related_objects=[wall], relating_type=wall_type)\n\n# Add geometry\nrepresentation = ifcopenshell.api.run(\"geometry.add_wall_representation\", model,\n    context=body, length=5.0, height=3.0, thickness=0.2)\nifcopenshell.api.run(\"geometry.assign_representation\", model,\n    product=wall, representation=representation)\nifcopenshell.api.run(\"geometry.edit_object_placement\", model, product=wall)\n\n# Place in spatial structure\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    products=[wall], relating_structure=storey)\n\n# Add properties\npset = ifcopenshell.api.run(\"pset.add_pset\", model,\n    product=wall, name=\"Pset_WallCommon\")\nifcopenshell.api.run(\"pset.edit_pset\", model, pset=pset, properties={\n    \"IsExternal\": True,\n    \"LoadBearing\": True,\n    \"FireRating\": \"REI90\",\n    \"ThermalTransmittance\": 0.24,\n})\n```\n\n---\n\n## Complete API Module Table (35 Modules)\n\n| Module | Category | Purpose | Key Functions |\n|--------|----------|---------|---------------|\n| `root` | Core | Create\u002Fremove\u002Fcopy entities | `create_entity`, `remove_product`, `copy_class`, `reassign_class` |\n| `spatial` | Spatial | Containment and referencing | `assign_container`, `unassign_container`, `reference_structure` |\n| `aggregate` | Spatial | Hierarchical decomposition | `assign_object`, `unassign_object` |\n| `geometry` | Geometry | Representations and placement | `add_wall_representation`, `add_mesh_representation`, `add_profile_representation`, `assign_representation`, `edit_object_placement` |\n| `context` | Geometry | Representation contexts | `add_context`, `edit_context`, `remove_context` |\n| `pset` | Properties | Property and quantity sets | `add_pset`, `edit_pset`, `add_qto`, `edit_qto` |\n| `material` | Materials | Material definitions and sets | `add_material`, `assign_material`, `add_material_set`, `add_layer` |\n| `type` | Types | Type definitions | `assign_type`, `unassign_type`, `map_type_representations` |\n| `attribute` | Data | Direct attribute editing | `edit_attributes` |\n| `unit` | Setup | Measurement units | `assign_unit`, `add_si_unit`, `add_conversion_based_unit` |\n| `project` | Setup | Project file creation | `create_file`, `append_asset` |\n| `owner` | Organization | Actors and roles | `add_person`, `add_organisation`, `set_user` |\n| `classification` | Organization | Classification systems | `add_classification`, `add_reference` |\n| `group` | Organization | Element grouping | `add_group`, `assign_group`, `unassign_group` |\n| `void` | Geometry | Openings and voids | `add_opening`, `add_filling` |\n| `style` | Visualization | Visual styles | `add_style`, `add_surface_style`, `assign_representation_styles` |\n| `layer` | Visualization | CAD layers | `add_layer`, `assign_layer` |\n| `profile` | Geometry | Cross-section profiles | `add_parameterised_profile`, `add_arbitrary_profile` |\n| `cost` | Management | Cost scheduling | `add_cost_schedule`, `add_cost_item` |\n| `sequence` | Management | Task scheduling (4D) | `add_work_schedule`, `add_task`, `edit_task_time` |\n| `resource` | Management | Resource allocation | `add_resource`, `assign_resource` |\n| `system` | MEP | Building systems | `add_system`, `assign_system` |\n| `structural` | Engineering | Structural analysis | `add_structural_analysis_model`, `add_structural_member` |\n| `document` | References | Document management | `add_information`, `assign_document` |\n| `constraint` | Design | Design constraints | `add_objective`, `add_metric`, `assign_constraint` |\n| `nest` | Organization | Nesting relationships | `assign_object`, `unassign_object` |\n| `boundary` | Spatial | Space boundaries | `assign_connection_geometry` |\n| `library` | References | Library references | `add_library`, `add_reference`, `assign_reference` |\n| `drawing` | Visualization | Drawings\u002Fannotations | `add_drawing`, `add_annotation` |\n| `georeference` | Location | Map coordinates | set coordinates, define projections |\n| `grid` | Planning | Architectural grids | create, add axis |\n| `feature` | Geometry | Geometric features | `add_feature` |\n| `alignment` | Infrastructure | Road\u002Frail alignment | `add_alignment` |\n| `cogo` | Geometry | Coordinate geometry | calculate, transform |\n| `pset_template` | Standards | Property set templates | create, assign |\n| `control` | Relations | Control relationships | assign, establish |\n\n---\n\n## Common Operations\n\n### Edit Attributes Directly\n\n```python\n# IfcOpenShell: all schema versions\nifcopenshell.api.run(\"attribute.edit_attributes\", model,\n    product=wall, attributes={\"Name\": \"Wall 001\", \"Description\": \"External bearing wall\"})\n```\n\n### Create and Assign Opening\n\n```python\n# IfcOpenShell: all schema versions\nopening = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcOpeningElement\", name=\"Door Opening\")\nifcopenshell.api.run(\"void.add_opening\", model, opening=opening, element=wall)\n\n# Optionally fill with door\ndoor = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcDoor\", name=\"Door 001\")\nifcopenshell.api.run(\"void.add_filling\", model, opening=opening, element=door)\n```\n\n### Assign Classification\n\n```python\n# IfcOpenShell: all schema versions\nclassification = ifcopenshell.api.run(\"classification.add_classification\", model,\n    classification=\"Uniclass 2015\")\nifcopenshell.api.run(\"classification.add_reference\", model,\n    products=[wall], identification=\"Ss_20_10_30\",\n    name=\"Walls\", classification=classification)\n```\n\n### Add Visual Style\n\n```python\n# IfcOpenShell: all schema versions\nstyle = ifcopenshell.api.run(\"style.add_style\", model, name=\"Concrete Grey\")\nifcopenshell.api.run(\"style.add_surface_style\", model, style=style,\n    attributes={\"SurfaceColour\": {\"Red\": 0.7, \"Green\": 0.7, \"Blue\": 0.7}})\nifcopenshell.api.run(\"style.assign_representation_styles\", model,\n    shape_representation=representation, styles=[style])\n```\n\n### Safe Element Removal\n\n```python\n# IfcOpenShell: all schema versions\n# ALWAYS use root.remove_product: it cleans up ALL relationships\nifcopenshell.api.run(\"root.remove_product\", model, product=wall)\n# NEVER use model.remove(wall) for products: it leaves dangling references\n```\n\n---\n\n## Parameter Conventions\n\n### List Parameters (v0.8+ Breaking Change)\n\nSince IfcOpenShell v0.8, relationship functions use **list** parameters:\n\n```python\n# CORRECT (v0.8+): products is a list\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    products=[wall], relating_structure=storey)\n\n# WRONG: single element (raises TypeError in v0.8+)\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    product=wall, relating_structure=storey)  # KeyError: 'product'\n```\n\nFunctions affected: `spatial.assign_container`, `aggregate.assign_object`, `type.assign_type`, `material.assign_material`, `group.assign_group`, `classification.add_reference`, `nest.assign_object`, and others.\n\n### Property Type Mapping (pset.edit_pset)\n\nPython types map automatically to IFC property types:\n\n| Python Type | IFC Type | Example |\n|-------------|----------|---------|\n| `str` | IfcLabel | `\"REI60\"` |\n| `float` | IfcReal | `0.24` |\n| `int` | IfcInteger | `3` |\n| `bool` | IfcBoolean | `True` |\n| `None` | (deletes property) | `None` |\n\n### Matrix Convention (geometry.edit_object_placement)\n\nPlacement uses a 4x4 NumPy transformation matrix:\n\n```python\nimport numpy\n# Identity matrix = origin, no rotation\nifcopenshell.api.run(\"geometry.edit_object_placement\", model,\n    product=wall, matrix=numpy.eye(4))\n```\n\n**ALWAYS** set `is_si=True` (default) when providing coordinates in meters. Set `is_si=False` only when coordinates match the file's native unit system.\n\n---\n\n## Version Notes\n\n### Schema-Specific Entities\n\n| Entity | IFC2X3 | IFC4 | IFC4X3 |\n|--------|--------|------|--------|\n| IfcBuildingStorey | Yes | Yes | Yes |\n| IfcSpace | Yes | Yes | Yes |\n| IfcFacility | No | No | Yes |\n| IfcFacilityPart | No | No | Yes |\n| IfcAlignment | No | No | Yes |\n| IfcBridge | No | No | Yes |\n| IfcRoad | No | No | Yes |\n\n`api.run()` handles most schema differences internally. When creating IFC4X3 infrastructure models, use the infrastructure-specific entity classes.\n\n### project.create_file Parameter\n\n```python\n# CORRECT: parameter is \"version\" (not \"schema\")\nmodel = ifcopenshell.api.run(\"project.create_file\", version=\"IFC4\")\n\n# WRONG: \"schema\" is for ifcopenshell.file(), not project.create_file\nmodel = ifcopenshell.api.run(\"project.create_file\", schema=\"IFC4\")  # Unexpected kwarg\n```\n\n---\n\n## Dependency\n\nThis skill depends on **ifcos-syntax-fileio** for file creation, opening, writing, and transaction management patterns. Use ifcos-syntax-fileio for:\n- `ifcopenshell.open()` \u002F `ifcopenshell.file()`\n- `model.write()` \u002F `model.to_string()`\n- Transaction management (`begin_transaction` \u002F `end_transaction` \u002F `undo` \u002F `redo`)\n\n---\n\n## Reference Links\n\n- [API Method Signatures](references\u002Fmethods.md) — Complete signatures for all 35 API modules\n- [Working Code Examples](references\u002Fexamples.md) — End-to-end examples per domain\n- [Anti-Patterns](references\u002Fanti-patterns.md) — Common API mistakes and how to avoid them\n","# IfcOpenShell API Module System\n\n## Quick Reference\n\n### Critical Warnings\n\n- **ALWAYS** use `ifcopenshell.api.run()` or direct module calls for IFC mutations. NEVER modify entity attributes directly (e.g., `wall.Name = \"X\"`) — use `api.run(\"attribute.edit_attributes\", ...)` instead.\n- **ALWAYS** import `ifcopenshell.api` before calling any API function. The module uses lazy loading; functions are NOT available without this import.\n- **ALWAYS** pass the `file` (model) object as the first positional argument after the function name in `api.run()`.\n- **NEVER** invent API module or function names. There are exactly 35 modules — see the module table below. Hallucinated calls like `api.run(\"element.create\", ...)` or `api.run(\"wall.add\", ...)` do NOT exist.\n- **ALWAYS** use keyword arguments for all parameters after the model. Positional arguments beyond the model are NOT supported.\n- **NEVER** use `model.create_entity()` for production code. Use `api.run(\"root.create_entity\", ...)` — it generates GlobalIds, sets ownership, and validates predefined types automatically.\n- **ALWAYS** set up a complete project before creating elements: IfcProject → units → contexts → spatial hierarchy. See the bootstrap pattern below.\n- **NEVER** assume `products` parameters accept single elements. Since IfcOpenShell v0.8+, most relationship functions expect `products` as a **list**, not a single entity.\n\n### Decision Tree: Which API Module to Use\n\n```\nWhat do you need to do?\n├── Create\u002Fremove\u002Fcopy IFC entities?\n│   └── root (create_entity, remove_product, copy_class, reassign_class)\n│\n├── Build spatial hierarchy?\n│   ├── Project → Site → Building → Storey → Space?\n│   │   └── aggregate (assign_object, unassign_object)\n│   ├── Place elements in a storey\u002Fspace?\n│   │   └── spatial (assign_container, unassign_container)\n│   └── Reference element in multiple spaces?\n│       └── spatial (reference_structure, dereference_structure)\n│\n├── Add geometry to elements?\n│   ├── Set up representation contexts first?\n│   │   └── context (add_context — root context, then subcontexts)\n│   ├── Parametric wall\u002Fslab\u002Fbeam geometry?\n│   │   └── geometry (add_wall_representation, add_slab_representation,\n│   │       add_profile_representation)\n│   ├── Custom mesh geometry?\n│   │   └── geometry (add_mesh_representation)\n│   ├── Position element in 3D space?\n│   │   └── geometry (edit_object_placement)\n│   └── Connect geometry to element?\n│       └── geometry (assign_representation)\n│\n├── Set properties on elements?\n│   ├── Key-value metadata (name, fire rating, etc.)?\n│   │   └── pset (add_pset, edit_pset)\n│   └── Measurable quantities (length, area, volume)?\n│       └── pset (add_qto, edit_qto)\n│\n├── Assign materials?\n│   ├── Simple single material?\n│   │   └── material (add_material, assign_material)\n│   ├── Layered construction (walls, slabs)?\n│   │   └── material (add_material_set with IfcMaterialLayerSet, add_layer)\n│   ├── Profiled sections (beams, columns)?\n│   │   └── material (add_material_set with IfcMaterialProfileSet, add_profile)\n│   └── Composite (windows, doors)?\n│       └── material (add_material_set with IfcMaterialConstituentSet)\n│\n├── Assign\u002Fmanage types?\n│   └── type (assign_type, unassign_type, map_type_representations)\n│\n├── Edit entity attributes directly?\n│   └── attribute (edit_attributes)\n│\n├── Create openings\u002Fvoids?\n│   └── void (add_opening, add_filling)\n│\n├── Set up units?\n│   └── unit (assign_unit — defaults to SI)\n│\n├── Manage project file?\n│   └── project (create_file)\n│\n└── Other domains?\n    ├── Classification → classification\n    ├── Groups → group\n    ├── Layers (CAD) → layer\n    ├── Visual styles → style\n    ├── Cost management → cost\n    ├── Scheduling (4D) → sequence\n    ├── MEP systems → system\n    ├── Structural analysis → structural\n    ├── Documents → document\n    ├── Constraints → constraint\n    ├── Resources → resource\n    ├── Owner\u002Factors → owner\n    ├── Profiles → profile\n    ├── Nesting → nest\n    ├── Boundaries → boundary\n    ├── Libraries → library\n    ├── Drawing\u002Fannotations → drawing\n    ├── Georeference → georeference\n    ├── Grid → grid\n    ├── Infrastructure alignment → alignment\n    ├── Coordinate geometry → cogo\n    ├── Features → feature\n    └── Property set templates → pset_template\n```\n\n---\n\n## Essential Patterns\n\n### Pattern 1: Two Equivalent Invocation Styles\n\n```python\n# IfcOpenShell v0.8+: both styles produce identical results\n\nimport ifcopenshell\nimport ifcopenshell.api\n\nmodel = ifcopenshell.file(schema=\"IFC4\")\n\n# Style A: api.run() with dot-notation string (original, most documented)\nwall = ifcopenshell.api.run(\"root.create_entity\", model, ifc_class=\"IfcWall\", name=\"Wall 1\")\n\n# Style B: Direct module call (shorter, IDE-friendly)\nwall = ifcopenshell.api.root.create_entity(model, ifc_class=\"IfcWall\", name=\"Wall 1\")\n```\n\n**ALWAYS** use one style consistently within a project. Both are correct. `api.run()` is more common in documentation and tutorials.\n\n### Pattern 2: Complete Project Bootstrap\n\n```python\n# IfcOpenShell: IFC4 (change version\u002Fschema for IFC2X3 or IFC4X3)\nimport ifcopenshell\nimport ifcopenshell.api\n\n# Step 1: Create file with proper headers (production use)\nmodel = ifcopenshell.api.run(\"project.create_file\", version=\"IFC4\")\n\n# Step 2: Create project entity\nproject = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcProject\", name=\"My Project\")\n\n# Step 3: Assign units (defaults to SI metric)\nifcopenshell.api.run(\"unit.assign_unit\", model)\n\n# Step 4: Create representation contexts\nmodel3d = ifcopenshell.api.run(\"context.add_context\", model, context_type=\"Model\")\nbody = ifcopenshell.api.run(\"context.add_context\", model,\n    context_type=\"Model\", context_identifier=\"Body\",\n    target_view=\"MODEL_VIEW\", parent=model3d)\n\n# Step 5: Build spatial hierarchy\nsite = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcSite\", name=\"Default Site\")\nbuilding = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcBuilding\", name=\"Building A\")\nstorey = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcBuildingStorey\", name=\"Ground Floor\")\n\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[site], relating_object=project)\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[building], relating_object=site)\nifcopenshell.api.run(\"aggregate.assign_object\", model,\n    products=[storey], relating_object=building)\n```\n\n**ALWAYS** follow this sequence: file → project → units → contexts → spatial hierarchy. Skipping steps produces invalid IFC files.\n\n### Pattern 3: Create Element with Full Data\n\n```python\n# IfcOpenShell: IFC4 (requires completed bootstrap above)\n\n# Create wall type\nwall_type = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcWallType\", name=\"Standard Wall 200mm\")\n\n# Add material to type (best practice: assign to types, not occurrences)\nconcrete = ifcopenshell.api.run(\"material.add_material\", model,\n    name=\"Concrete C30\u002F37\", category=\"concrete\")\nifcopenshell.api.run(\"material.assign_material\", model,\n    products=[wall_type], material=concrete)\n\n# Create wall occurrence\nwall = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcWall\", name=\"Wall 001\")\n\n# Assign type\nifcopenshell.api.run(\"type.assign_type\", model,\n    related_objects=[wall], relating_type=wall_type)\n\n# Add geometry\nrepresentation = ifcopenshell.api.run(\"geometry.add_wall_representation\", model,\n    context=body, length=5.0, height=3.0, thickness=0.2)\nifcopenshell.api.run(\"geometry.assign_representation\", model,\n    product=wall, representation=representation)\nifcopenshell.api.run(\"geometry.edit_object_placement\", model, product=wall)\n\n# Place in spatial structure\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    products=[wall], relating_structure=storey)\n\n# Add properties\npset = ifcopenshell.api.run(\"pset.add_pset\", model,\n    product=wall, name=\"Pset_WallCommon\")\nifcopenshell.api.run(\"pset.edit_pset\", model, pset=pset, properties={\n    \"IsExternal\": True,\n    \"LoadBearing\": True,\n    \"FireRating\": \"REI90\",\n    \"ThermalTransmittance\": 0.24,\n})\n```\n\n---\n\n## Complete API Module Table (35 Modules)\n\n| Module | Category | Purpose | Key Functions |\n|--------|----------|---------|---------------|\n| `root` | Core | Create\u002Fremove\u002Fcopy entities | `create_entity`, `remove_product`, `copy_class`, `reassign_class` |\n| `spatial` | Spatial | Containment and referencing | `assign_container`, `unassign_container`, `reference_structure` |\n| `aggregate` | Spatial | Hierarchical decomposition | `assign_object`, `unassign_object` |\n| `geometry` | Geometry | Representations and placement | `add_wall_representation`, `add_mesh_representation`, `add_profile_representation`, `assign_representation`, `edit_object_placement` |\n| `context` | Geometry | Representation contexts | `add_context`, `edit_context`, `remove_context` |\n| `pset` | Properties | Property and quantity sets | `add_pset`, `edit_pset`, `add_qto`, `edit_qto` |\n| `material` | Materials | Material definitions and sets | `add_material`, `assign_material`, `add_material_set`, `add_layer` |\n| `type` | Types | Type definitions | `assign_type`, `unassign_type`, `map_type_representations` |\n| `attribute` | Data | Direct attribute editing | `edit_attributes` |\n| `unit` | Setup | Measurement units | `assign_unit`, `add_si_unit`, `add_conversion_based_unit` |\n| `project` | Setup | Project file creation | `create_file`, `append_asset` |\n| `owner` | Organization | Actors and roles | `add_person`, `add_organisation`, `set_user` |\n| `classification` | Organization | Classification systems | `add_classification`, `add_reference` |\n| `group` | Organization | Element grouping | `add_group`, `assign_group`, `unassign_group` |\n| `void` | Geometry | Openings and voids | `add_opening`, `add_filling` |\n| `style` | Visualization | Visual styles | `add_style`, `add_surface_style`, `assign_representation_styles` |\n| `layer` | Visualization | CAD layers | `add_layer`, `assign_layer` |\n| `profile` | Geometry | Cross-section profiles | `add_parameterised_profile`, `add_arbitrary_profile` |\n| `cost` | Management | Cost scheduling | `add_cost_schedule`, `add_cost_item` |\n| `sequence` | Management | Task scheduling (4D) | `add_work_schedule`, `add_task`, `edit_task_time` |\n| `resource` | Management | Resource allocation | `add_resource`, `assign_resource` |\n| `system` | MEP | Building systems | `add_system`, `assign_system` |\n| `structural` | Engineering | Structural analysis | `add_structural_analysis_model`, `add_structural_member` |\n| `document` | References | Document management | `add_information`, `assign_document` |\n| `constraint` | Design | Design constraints | `add_objective`, `add_metric`, `assign_constraint` |\n| `nest` | Organization | Nesting relationships | `assign_object`, `unassign_object` |\n| `boundary` | Spatial | Space boundaries | `assign_connection_geometry` |\n| `library` | References | Library references | `add_library`, `add_reference`, `assign_reference` |\n| `drawing` | Visualization | Drawings\u002Fannotations | `add_drawing`, `add_annotation` |\n| `georeference` | Location | Map coordinates | set coordinates, define projections |\n| `grid` | Planning | Architectural grids | create, add axis |\n| `feature` | Geometry | Geometric features | `add_feature` |\n| `alignment` | Infrastructure | Road\u002Frail alignment | `add_alignment` |\n| `cogo` | Geometry | Coordinate geometry | calculate, transform |\n| `pset_template` | Standards | Property set templates | create, assign |\n| `control` | Relations | Control relationships | assign, establish |\n\n---\n\n## Common Operations\n\n### Edit Attributes Directly\n\n```python\n# IfcOpenShell: all schema versions\nifcopenshell.api.run(\"attribute.edit_attributes\", model,\n    product=wall, attributes={\"Name\": \"Wall 001\", \"Description\": \"External bearing wall\"})\n```\n\n### Create and Assign Opening\n\n```python\n# IfcOpenShell: all schema versions\nopening = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcOpeningElement\", name=\"Door Opening\")\nifcopenshell.api.run(\"void.add_opening\", model, opening=opening, element=wall)\n\n# Optionally fill with door\ndoor = ifcopenshell.api.run(\"root.create_entity\", model,\n    ifc_class=\"IfcDoor\", name=\"Door 001\")\nifcopenshell.api.run(\"void.add_filling\", model, opening=opening, element=door)\n```\n\n### Assign Classification\n\n```python\n# IfcOpenShell: all schema versions\nclassification = ifcopenshell.api.run(\"classification.add_classification\", model,\n    classification=\"Uniclass 2015\")\nifcopenshell.api.run(\"classification.add_reference\", model,\n    products=[wall], identification=\"Ss_20_10_30\",\n    name=\"Walls\", classification=classification)\n```\n\n### Add Visual Style\n\n```python\n# IfcOpenShell: all schema versions\nstyle = ifcopenshell.api.run(\"style.add_style\", model, name=\"Concrete Grey\")\nifcopenshell.api.run(\"style.add_surface_style\", model, style=style,\n    attributes={\"SurfaceColour\": {\"Red\": 0.7, \"Green\": 0.7, \"Blue\": 0.7}})\nifcopenshell.api.run(\"style.assign_representation_styles\", model,\n    shape_representation=representation, styles=[style])\n```\n\n### Safe Element Removal\n\n```python\n# IfcOpenShell: all schema versions\n# ALWAYS use root.remove_product: it cleans up ALL relationships\nifcopenshell.api.run(\"root.remove_product\", model, product=wall)\n# NEVER use model.remove(wall) for products: it leaves dangling references\n```\n\n---\n\n## Parameter Conventions\n\n### List Parameters (v0.8+ Breaking Change)\n\nSince IfcOpenShell v0.8, relationship functions use **list** parameters:\n\n```python\n# CORRECT (v0.8+): products is a list\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    products=[wall], relating_structure=storey)\n\n# WRONG: single element (raises TypeError in v0.8+)\nifcopenshell.api.run(\"spatial.assign_container\", model,\n    product=wall, relating_structure=storey)  # KeyError: 'product'\n```\n\nFunctions affected: `spatial.assign_container`, `aggregate.assign_object`, `type.assign_type`, `material.assign_material`, `group.assign_group`, `classification.add_reference`, `nest.assign_object`, and others.\n\n### Property Type Mapping (pset.edit_pset)\n\nPython types map automatically to IFC property types:\n\n| Python Type | IFC Type | Example |\n|-------------|----------|---------|\n| `str` | IfcLabel | `\"REI60\"` |\n| `float` | IfcReal | `0.24` |\n| `int` | IfcInteger | `3` |\n| `bool` | IfcBoolean | `True` |\n| `None` | (deletes property) | `None` |\n\n### Matrix Convention (geometry.edit_object_placement)\n\nPlacement uses a 4x4 NumPy transformation matrix:\n\n```python\nimport numpy\n# Identity matrix = origin, no rotation\nifcopenshell.api.run(\"geometry.edit_object_placement\", model,\n    product=wall, matrix=numpy.eye(4))\n```\n\n**ALWAYS** set `is_si=True` (default) when providing coordinates in meters. Set `is_si=False` only when coordinates match the file's native unit system.\n\n---\n\n## Version Notes\n\n### Schema-Specific Entities\n\n| Entity | IFC2X3 | IFC4 | IFC4X3 |\n|--------|--------|------|--------|\n| IfcBuildingStorey | Yes | Yes | Yes |\n| IfcSpace | Yes | Yes | Yes |\n| IfcFacility | No | No | Yes |\n| IfcFacilityPart | No | No | Yes |\n| IfcAlignment | No | No | Yes |\n| IfcBridge | No | No | Yes |\n| IfcRoad | No | No | Yes |\n\n`api.run()` handles most schema differences internally. When creating IFC4X3 infrastructure models, use the infrastructure-specific entity classes.\n\n### project.create_file Parameter\n\n```python\n# CORRECT: parameter is \"version\" (not \"schema\")\nmodel = ifcopenshell.api.run(\"project.create_file\", version=\"IFC4\")\n\n# WRONG: \"schema\" is for ifcopenshell.file(), not project.create_file\nmodel = ifcopenshell.api.run(\"project.create_file\", schema=\"IFC4\")  # Unexpected kwarg\n```\n\n---\n\n## Dependency\n\nThis skill depends on **ifcos-syntax-fileio** for file creation, opening, writing, and transaction management patterns. Use ifcos-syntax-fileio for:\n- `ifcopenshell.open()` \u002F `ifcopenshell.file()`\n- `model.write()` \u002F `model.to_string()`\n- Transaction management (`begin_transaction` \u002F `end_transaction` \u002F `undo` \u002F `redo`)\n\n---\n\n## Reference Links\n\n- [API Method Signatures](references\u002Fmethods.md) — Complete signatures for all 35 API modules\n- [Working Code Examples](references\u002Fexamples.md) — End-to-end examples per domain\n- [Anti-Patterns](references\u002Fanti-patterns.md) — Common API mistakes and how to avoid them\n",{"name":5,"license":14,"metadata":23,"description":26,"compatibility":27},{"author":24,"version":25},"OpenAEC-Foundation","1.0","Use when writing IfcOpenShell Python code that creates, modifies, or deletes IFC entities. Prevents the #1 AI mistake: using create_entity() or direct attribute assignment instead of ifcopenshell.api.run(). Covers all 30+ API modules, invocation patterns, parameter conventions, and the difference between api.run() and direct module calls. Keywords: ifcopenshell.api, api.run, create_entity, IFC, BIM, IfcWall, IfcSlab, API modules, ifcopenshell Python, how to use api.run, ifcopenshell tutorial.\n","Designed for Claude Code. Requires IfcOpenShell Python library.","main","9bb7acf0c2ec4f44373969cb14e55af3c9a8385f","plugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot","2026-11-09 13:26:47",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add lagzgabrielmuller-dot\u002Fkit-ingenieria-3d --skill ifcos-syntax-api",{"tool":40,"command":41},"bunx","bunx skills add lagzgabrielmuller-dot\u002Fkit-ingenieria-3d --skill ifcos-syntax-api",{"tool":43,"command":44},"pnpm","pnpm dlx skills add lagzgabrielmuller-dot\u002Fkit-ingenieria-3d --skill ifcos-syntax-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"references\u002Fanti-patterns.md","REFERENCE","参考文档",14242,"https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api\u002Freferences\u002Fanti-patterns.md",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fexamples.md",22978,"https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api\u002Freferences\u002Fexamples.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fmethods.md",28001,"https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fblender-bim-sverchok\u002Fskills\u002Fifcopenshell\u002Fsyntax\u002Fifcos-syntax-api\u002Freferences\u002Fmethods.md",[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7FBFSZ93YM463CGS91D0TZG","manimce-best-practices","Trigger when: (1) User mentions \"manim\" or \"Manim Community\" or \"ManimCE\", (2) Code contains `from manim import *`, (3) User runs `manim` CLI commands, (4) Working with Scene, MathTex, Create(), or ManimCE-specific classes.\n\nBest practices for Manim Community Edition - the community-maintained Python animation engine. Covers Scene structure, animations, LaTeX\u002FMathTex, 3D with ThreeDScene, camera control, styling, and CLI usage.\n\nNOT for ManimGL\u002F3b1b version (which uses `manimlib` imports and `manimgl` CLI).","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fmanim-animaciones\u002Fskills\u002Fmanimce-best-practices\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fmanim-animaciones\u002Fskills\u002Fmanimce-best-practices\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7FB2K59HNNXS9WKHAMWHC3C","drawio","Create, edit, replicate, import, and export draw.io diagrams with an offline YAML-first workflow: architecture, network topologies, flowcharts, UML\u002FER, org charts, Mermaid\u002FCSV conversion, existing .drawio bundles, style presets, themes, and non-publication formula diagrams. For publication figures (paper, thesis, IEEE, camera-ready) use drawio-academic-skills instead.","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fdiagramas-y-documentos\u002Fskills\u002Fdrawio\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7FB2BWX7GWK9H2X8BGCYDDD","drawio-academic-skills","Publication-figure overlay for draw.io. Use instead of drawio whenever the diagram is for a paper, thesis, dissertation, journal, conference, IEEE\u002FACM submission, manuscript, camera-ready, Word\u002FLaTeX figure, or other publication. Applies venue, figure-type, color, caption\u002Flegend, formula, and paper-readability gates for architecture, workflow, roadmap, network-topology, and replicated paper figures.","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fdiagramas-y-documentos\u002Fskills\u002Fdrawio-academic-skills\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7FB22JESEAV8T15DJT3D444","uncertainty-and-units","Tracks physical units and propagates measurement uncertainty in scientific calculations using pint and uncertainties. Use for unit conversion and dimensional checking, GUM uncertainty budgets, Type A and Type B evaluation, coverage factors and expanded uncertainty, Monte Carlo propagation, significant-figure and plus-minus reporting, error propagation through curve fits, CODATA constants, auditing Python code for stripped units or broken uncertainty propagation, and order-of-magnitude plausibility checks using dimensionless groups (Reynolds, Peclet, Damkohler, Knudsen, Biot, Womersley), characteristic scales such as diffusion time or Debye length, and observed magnitude ranges. Trigger on \"is this number physically reasonable\", \"sanity check these units\", \"what regime is this flow in\", or a result that looks off by orders of magnitude.","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fciencia-y-calculo\u002Fskills\u002Funcertainty-and-units\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7FB1ANRSG28R335FDY9SA3R","statistical-analysis","Guided statistical analysis for research data - test selection, assumption checking, effect sizes, power analysis, Bayesian alternatives, and APA-formatted reporting. Use whenever a user wants to compare groups, test a hypothesis, analyze experimental or survey data, check statistical assumptions, compute required sample sizes, or write up results - even if they never name a specific test. Covers t-tests, ANOVA, chi-square, correlation, regression, non-parametric and Bayesian methods. For low-level model APIs, see the statsmodels and pymc skills.","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fciencia-y-calculo\u002Fskills\u002Fstatistical-analysis\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M7FB15KRA9D7JCPH4P9T6XJY","simpy","Builds, inspects, tests, and analyzes bounded process-based discrete-event simulations with SimPy. Use for event scheduling, resource queues, interrupts, monitoring, independent replications, warm-up, and reproducible output analysis.","https:\u002F\u002Fgithub.com\u002Flagzgabrielmuller-dot\u002Fkit-ingenieria-3d\u002Fblob\u002Fmain\u002Fplugins\u002Fciencia-y-calculo\u002Fskills\u002Fsimpy\u002FSKILL.md",[],[]]