Skip to content

feat: Add meta-router skill for UiPath task dispatch#100

Merged
gabrielavaduva merged 8 commits intomainfrom
feat/meta-router-skill
Apr 7, 2026
Merged

feat: Add meta-router skill for UiPath task dispatch#100
gabrielavaduva merged 8 commits intomainfrom
feat/meta-router-skill

Conversation

@AlvinStanescu
Copy link
Copy Markdown
Collaborator

@AlvinStanescu AlvinStanescu commented Mar 28, 2026

Summary

  • Adds a uipath-planner skill that plans and routes multi-skill UiPath tasks without executing them
  • Provides a skill capability map so the planner knows what each domain skill can/cannot do (auth, deploy)
  • Includes 7 pre-built multi-skill workflow patterns covering the most common cross-skill scenarios

Motivation

Some UiPath tasks span multiple skills — e.g., building an RPA automation AND deploying it to Orchestrator requires both uipath-rpa and uipath-platform. When the user's request is ambiguous or multi-step, the agent needs a way to determine the right execution order and skill combination. The planner fills this gap: it analyzes the request, detects the project type from the filesystem if needed, and emits a numbered plan that the main agent executes.

Design

Plan-only skill — the planner never writes code, runs CLI commands, or modifies state. It produces a plan, then stops. The main agent loads and executes the specialist skills.

4-step decision flow:

  1. Detect multi-skill tasks — match the request against 7 known multi-skill patterns (RPA+deploy, flow+missing resources, UI discovery+build, etc.)
  2. Filesystem detection — if no multi-skill pattern matched, probe the working directory for project signals (.cs, .xaml, .flow, .py, .uipath/) and route to the matching skill
  3. Lightweight discovery — if filesystem produced no match, ask the user up to 2 clarifying questions
  4. Emit the plan — output a numbered Load <skill> → <action> plan with the user's original request as context

Skill capability map — a table in the skill body showing what each domain skill handles:

Skill Handles auth? Handles deploy?
uipath-rpa No No — defers to uipath-platform
uipath-agents Yes Yes — full end-to-end
uipath-coded-apps Yes Yes — full end-to-end
uipath-maestro-flow Yes Partial — Studio Web only
uipath-platform Yes Yes — the deploy destination
uipath-servo No No — local testing only

7 pre-built multi-skill patterns:

Pattern Skills involved
RPA build + deploy uipath-rpauipath-platform
Flow with missing resources uipath-maestro-flowuipath-rpauipath-platformuipath-maestro-flow
Flow deploy to Orchestrator uipath-maestro-flowuipath-platform
UI discovery + build automation uipath-servouipath-rpa
Test live UI + fix automation uipath-servouipath-rpa
Iterative UI automation dev uipath-servouipath-rpa (loop)
Agent that uses RPA tools uipath-rpauipath-platformuipath-agents

Test plan

  • Verify uipath-planner appears in system-reminder skill listing
  • Test multi-skill routing: "build and deploy an automation" → planner emits uipath-rpauipath-platform plan
  • Test filesystem detection: ambiguous request in a directory with .cs + project.json → routes to uipath-rpa
  • Test overlapping signals: directory with both .cs and flow_files/*.flow → planner emits multi-skill plan
  • Test ambiguous request with no project: "automate something" → planner asks up to 2 clarifying questions
  • Test servo+RPA routing: "automate this SAP form" → planner emits uipath-servouipath-rpa plan
  • Verify planner does not execute any commands — plan only, no uip or code generation

🤖 Generated with Claude Code

@AlvinStanescu AlvinStanescu force-pushed the feat/meta-router-skill branch from 307c81b to 13593e5 Compare March 28, 2026 18:33
AlvinStanescu and others added 2 commits March 31, 2026 15:14
Add a thin `uipath` router skill that detects project type from filesystem
context and dispatches to the correct specialist skill. This replaces the
previous approach of relying on verbose inline TRIGGER/DO NOT TRIGGER rules
in each skill's description field, which consumed ~1,300 listing tokens and
was unreliable for weaker models.

Changes:
- New `skills/uipath/SKILL.md` — 5-step decision tree router with
  filesystem probing, explicit signal matching, and progressive loading
  examples for 6 core use cases
- All 7 domain skill descriptions shortened from ~700 avg to ~100 chars
- Added `when_to_use` field to all 8 skills with narrow direct-match
  triggers and explicit NOT-for boundaries
- Total listing token budget reduced from ~1,295 to ~252 tokens (-80%)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Remove non-standard when_to_use frontmatter field from all 8 skills
and merge its content into the description field per agentskills.io
best practices. Improve description quality with better user-intent
phrasing and edge-case triggers (coded-workflows, servo, coded-apps).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@AlvinStanescu AlvinStanescu force-pushed the feat/meta-router-skill branch from 13593e5 to ce2064a Compare March 31, 2026 12:22
@gabrielavaduva gabrielavaduva merged commit b16586c into main Apr 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants