agentsclimarketplace

Ue5 module router

Skill teixasalone/UnrealEngine5-Skills/skills/ue5-module-router

Provide reusable workflows for Unreal Engine 5.6/5.7 to simplify Blueprint, C++, UI, PCG, replication, debugging, and performance tasks.

Install
npx -y skills add teixasalone/UnrealEngine5-Skills --skill ue5-module-router

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 16 stars16 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route UE5.6/UE5.7 questions to the most precise skill using module names, aliases, intent keywords, and layer context. Works for explicit module prompts (RenderCore, AIModule, AssetRegistry) and natural language requests.

SKILL.md

1.8 KB, as published. Nobody here has run it

Quick Start

  • Extract explicit module names from user prompt first.
  • If module is found, route by exact module mapping before keyword heuristics.
  • If module is not found, use aliases and layer context.

Workflow

  • Parse prompt for module candidates (for example RenderCore, AIModule, AssetRegistry).
  • Lookup module in ue5-module-routing-table-final.csv.
  • If multiple hits, prioritize:
    1. exact module name match
    2. Build.cs path similarity
    3. alias overlap with prompt keywords
  • Return routing payload:
    • primary_skill
    • secondary_skill
    • recommended_mcp_tools[]
    • route_confidence
    • route_reason
  • Use secondary_skill when request spans multiple concerns in one module context.

Constraints

  • Prefer deterministic routing; avoid broad guesses if exact module match exists.
  • Keep one primary target skill unless user explicitly asks cross-module analysis.
  • If module maps to ue5-architecture, answer module-boundary/design first.
  • Prefer dedicated MCP tools before execute_script.

Failure Handling

  • If no module is recognized, fallback to closest capability skill and state reason.
  • If confidence is low, provide top 2 candidates and request module confirmation.
  • Use execute_script only when dedicated MCP tools are insufficient and explain why.
  • If mapping is outdated, regenerate from ue5-architecture/scripts/generate_module_index_v2.py.

Escalation

  • Escalate for large cross-cutting refactors across many modules.
  • Escalate when requested module belongs to plugin source outside indexed scope.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.