eae-skill-router（EAE 技能路由器）

EAE Skills Router

Router skill for EAE (EcoStruxure Automation Expert) development.

CRITICAL RULE - NEVER BYPASS SKILLS: - ALWAYS use an EAE skill for ANY operation on EAE files (.fbt, .adp, .dt, .cfg, .dfbproj, etc.) - This applies to BOTH creating AND modifying existing blocks - NEVER directly read, edit, or write EAE files outside of a skill context - When modifying an existing block, invoke the appropriate skill with the modification request - The skill will handle reading, validating, and updating all related files correctly

What Are You Doing?

What Are You Creating?

Quick Decision Tree

What are you doing?
│
├── Forking/copying block from SE library to custom library?
│   └── YES → /eae-fork (handles namespace migration)
│
├── Creating a NEW block from scratch?
│   │
│   ├── Full block with HMI visualization, OPC-UA, or persistence?
│   │   └── YES → /eae-cat (most common)
│   │
│   ├── Need algorithms or state logic?
│   │   └── YES → /eae-basic-fb
│   │
│   ├── Composing existing FBs together (no HMI)?
│   │   └── YES → /eae-composite-fb
│   │
│   ├── Custom data type (enum, struct, array)?
│   │   └── YES → /eae-datatype
│   │
│   └── Reusable interface pattern (socket/plug)?
│       └── YES → /eae-adapter
│
└── Looking up existing blocks?
    ├── Runtime.Base library → /eae-runtime-base
    └── SE process blocks → /eae-se-process

Triggers

Block Creation/Modification

• /eae-cat - Create CAT block with HMI (most common)
• /eae-basic-fb - Create Basic FB
• /eae-composite-fb - Create Composite FB
• /eae-datatype - Create DataType
• /eae-adapter - Create Adapter
• /eae-fork - Fork block from SE library to custom library with namespace migration

Library Reference

• /eae-runtime-base - Find/reference Runtime.Base standard library blocks
• /eae-se-process - Find/reference SE.App2Base and SE.App2CommonProcess blocks

Analysis & Validation

• /eae-sln-overview - Project overview, quality score, protocols, libraries
• /eae-naming-validator - Validate SE naming conventions
• /eae-performance-analyzer - Detect event storms, analyze performance

Router

• /eae-skill-router - This router (shows decision tree)

Quick Reference

Common Rules

These rules apply to ALL block types. See common-rules.md for full details.

ID Generation

All Events and VarDeclarations need 16-character hex IDs:

# Generate GUID for FBType
[guid]::NewGuid()

# Generate hex ID for elements (16 chars)
[guid]::NewGuid().ToString("N").Substring(0,16).ToUpper()

dfbproj Registration

Every block must be registered in the library's .dfbproj file:

<ItemGroup>
  <Compile Include="BlockName.fbt">
    <IEC61499Type>Basic</IEC61499Type>
  </Compile>
</ItemGroup>

Critical XML Rules

Troubleshooting

Scripts

Helper scripts for agentic operation are in scripts/. These are shared infrastructure used by all child skills.

Register Block in dfbproj (Universal)

Register any block type in the library's dfbproj file. All child skills should use this script.

# Register with explicit type
python scripts/register_dfbproj.py MyBlock MyLib --type cat
python scripts/register_dfbproj.py MyBlock MyLib --type composite
python scripts/register_dfbproj.py MyBlock MyLib --type basic
python scripts/register_dfbproj.py MyBlock MyLib --type adapter
python scripts/register_dfbproj.py MyBlock MyLib --type datatype

# Auto-detect type from existing files
python scripts/register_dfbproj.py MyBlock MyLib

# Verify registration
python scripts/register_dfbproj.py MyBlock MyLib --verify

# Dry run (show what would happen)
python scripts/register_dfbproj.py MyBlock MyLib --dry-run

# Output as JSON
python scripts/register_dfbproj.py MyBlock MyLib --json

Supported types:

Exit codes:

• 0 - Registration successful
• 1 - General error
• 11 - Registration issue

Generate IDs

Generate GUIDs and hex IDs for blocks:

# Generate 1 GUID + 1 hex ID (default)
python scripts/generate_ids.py

# Generate 5 hex IDs for Events/VarDeclarations
python scripts/generate_ids.py --hex 5

# Generate 2 GUIDs for multiple blocks
python scripts/generate_ids.py --guid 2

# Output as JSON for automation
python scripts/generate_ids.py --hex 4 --guid 1 --json

Validate Block

Validate .fbt, .adp, .dt files against EAE rules:

# Auto-detect block type and validate
python scripts/validate_block.py MyBlock.fbt

# Validate a CAT folder
python scripts/validate_block.py IEC61499/MyCAT/

# Specify block type explicitly
python scripts/validate_block.py --type basic MyBasicFB.fbt

# Output as JSON
python scripts/validate_block.py --json MyBlock.fbt

Exit codes:

• 0 - Validation passed
• 1 - Error running validation
• 10 - Validation failed (errors found)

Cross-Validate Consistency

Verify consistency between files on disk and dfbproj registration:

# Validate a single block
python scripts/validate_consistency.py MyBlock SE.ScadapackWWW

# Validate all blocks in a library
python scripts/validate_consistency.py --all SE.ScadapackWWW

# Show fix commands for issues
python scripts/validate_consistency.py --fix --all SE.ScadapackWWW

# Output as JSON
python scripts/validate_consistency.py --json --all SE.ScadapackWWW

# Specify expected block type
python scripts/validate_consistency.py --type cat MyCAT SE.ScadapackWWW

What it checks:

Exit codes:

• 0 - Validation passed (all consistent)
• 1 - Error running validation
• 10 - Validation failed (inconsistencies found)
• 11 - Registration issues (missing or wrong entries)

Track Blocks (State Management)

Track blocks created/forked during a session for rollback and audit:

# Add a block to tracking
python scripts/track_block.py add MyBlock SE.ScadapackWWW --type cat --operation fork --source SE.App2CommonProcess

# Add a created block
python scripts/track_block.py add MyBlock SE.ScadapackWWW --type basic --operation create

# Check block status
python scripts/track_block.py status MyBlock SE.ScadapackWWW

# Update status (e.g., mark as failed)
python scripts/track_block.py update MyBlock SE.ScadapackWWW --status failed --error "Build failed"

# Remove from tracking
python scripts/track_block.py remove MyBlock SE.ScadapackWWW

List Tracked Blocks

View all tracked blocks with filtering:

# List all tracked blocks
python scripts/list_tracked_blocks.py SE.ScadapackWWW

# Filter by status
python scripts/list_tracked_blocks.py SE.ScadapackWWW --status failed

# Filter by type
python scripts/list_tracked_blocks.py SE.ScadapackWWW --type cat

# Filter by operation
python scripts/list_tracked_blocks.py SE.ScadapackWWW --operation fork

# Show summary only
python scripts/list_tracked_blocks.py SE.ScadapackWWW --summary

# Clear tracking (start fresh)
python scripts/list_tracked_blocks.py SE.ScadapackWWW --clear

# JSON output
python scripts/list_tracked_blocks.py SE.ScadapackWWW --json

Tracking manifest location: {Library}/IEC61499/.eae-tracking/manifest.json

Rollback Operations

Undo failed or unwanted fork/create operations:

# Rollback a single block
python scripts/rollback_operation.py MyBlock SE.ScadapackWWW

# Rollback all failed blocks
python scripts/rollback_operation.py --all-failed SE.ScadapackWWW

# Preview without making changes
python scripts/rollback_operation.py --dry-run MyBlock SE.ScadapackWWW

# Skip confirmation prompt
python scripts/rollback_operation.py --force MyBlock SE.ScadapackWWW

# Specify block type if not tracked
python scripts/rollback_operation.py --type cat MyBlock SE.ScadapackWWW

# JSON output
python scripts/rollback_operation.py --json MyBlock SE.ScadapackWWW

What rollback does:

Exit codes:

• 0 - Rollback successful
• 1 - Error
• 10 - Block not found in tracking
• 11 - Rollback partially failed

Related Skills