← StructEngineCONTENT HISTORY

Update to StructEngine

Snapshot Nov 16, 2026 · 13:40 UTC · version 0.1.4

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save StructEngine and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use for generating standard STAAD.Pro load combination syntax for Indian Standards (IS 800:2007 steel, IS 456:2000 concrete) from primary load case definitions, with automatic case detection (DL, LL, WL, EQ, CR) and limit-state factor generation.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 245
    }
  ],
  "name": "staad-load-combinations",
  "skill_md_contents": "---\nname: staad-load-combinations\ndescription: Use for generating standard STAAD.Pro load combination syntax for Indian Standards (IS 800:2007 steel, IS 456:2000 concrete) from primary load case definitions, with automatic case detection (DL, LL, WL, EQ, CR) and limit-state factor generation.\n---\n\n# STAAD Load Combinations\n\nUse the registered StructEngine MCP tool `generate_staad_load_combinations` as the calculation and syntax authority for generating STAAD.Pro load combination blocks.\n\n## When to Use\n\nUse this skill whenever a user:\n- Requests STAAD load combinations according to Indian design codes (IS 800:2007 for steel or IS 456:2000 for concrete).\n- Pastes primary load cases (e.g. `LOAD 1 DEAD LOAD`, `LOAD 2 LIVE LOAD`, `LOAD 3 WIND +X`, `LOAD 4 SEISMIC +X`) and asks to create combination load cases.\n- Asks for Serviceability (SLS) and Ultimate / Strength (ULS) combinations formatted for the STAAD.Pro input file editor.\n- Inquires about partial safety factors for load combinations per IS 800:2007 Table 4 or IS 456:2000 Table 18.\n\n## Input & Execution Guidelines\n\n1. **Tool Invocation**: Call `generate_staad_load_combinations` with `load_cases_text` containing the user's primary load case definitions.\n2. **Design Code Selection**:\n   - Default to `code=\"IS800_2007\"` for steel structures, PEB buildings, warehouses, towers, and industrial structures.\n   - Use `code=\"IS456_2000\"` when the user explicitly requests reinforced concrete (RCC) or IS 456 combinations.\n3. **Combination Types & Numbering**:\n   - By default, both SLS (`include_sls=True`) and ULS (`include_uls=True`) combinations are generated.\n   - Default starting ID numbers: SLS starts at `1000`, ULS starts at `2000`. If the user specifies custom starting IDs (e.g., 101 and 201), set `sls_start_id` and `uls_start_id` accordingly.\n4. **Manual Overrides**:\n   - If a load case title is ambiguous or the user specifies a particular category (e.g., \"treat Case 4 as Crane Live Load\"), pass `manual_overrides={\"4\": \"CRL\"}`.\n5. **No Hallucinated Syntax**:\n   - Do not manually construct STAAD combination lines with guessed load factors. Always rely on the deterministic output returned by the `generate_staad_load_combinations` tool.\n\n## Presentation Guidelines\n\n1. **Structured Breakdown**: Present the total count of generated combinations with the breakdown between Serviceability (SLS) and Strength (ULS).\n2. **Primary Case Mapping**: Show a markdown table of recognized primary load cases, their detected categories (DL, LL, WL, EQ, CR, etc.), and detection confidence.\n3. **Executable STAAD Block**: Format the generated STAAD syntax in a clean fenced code block (` ```staad `) so the engineer can directly copy and paste it into the STAAD.Pro editor.\n4. **Engineering Verification**: State clearly that partial safety factors and combination rules follow the specified standard (e.g., IS 800:2007 Table 4), and advise the engineer to verify load factors against specific project design criteria and local code amendments before running analysis.\n"
}

SHA-256 of public snapshot: 9c8f11d3c0bf370abe63b9fc359dc06c11d23f773db44fb6959ff16fdf4c0876