UiPath Boost

Use only when the user explicitly asks to establish durable delivery governance around an already discovered UiPath repository or solution.

Use only when the user explicitly asks to create a portable, redacted UiPath project handoff for another person, harness, or directory.

Create and maintain a portable linked Markdown knowledge base for a UiPath program or project. Use when design decisions, runbooks, research, glossary terms, operational knowledge, reusable patterns, and lessons are scattered across conversations or folders and need searchable index notes, context pointers, ownership, and freshness signals.

Use only when the user explicitly asks which skill, workflow, or starting point to use; choose the smallest correct official UiPath and UiPath Boost route.

Run evidence-based UiPath discovery in frontier rounds. Use to sharpen an automation idea, stress-test a proposed solution, clarify a process before a PDD or SDD, or resolve business, data, exception, security, volume, SLA, access, and acceptance decisions.

Use only when the user explicitly asks to run UiPath discovery while maintaining durable project documentation.

Build and sharpen the business language used by a UiPath project. Use when process terms are vague, overloaded, inconsistent across business and technical teams, or when discovery, design, testing, and support need one canonical glossary and a small set of durable architectural decisions.

Use only when the user explicitly asks to map the decisions required to make a large, foggy UiPath program plannable.

Research a UiPath technical, product, platform, API, compatibility, or governance question using primary sources and capture the result as a cited Markdown note. Use when a project decision depends on current UiPath documentation, official repositories, release notes, specifications, or first-party APIs.

Use only when the user explicitly asks to create a focused UiPath questionnaire for the person who owns missing information.

Use only when the user explicitly asks to classify, verify, and route incoming UiPath work before it enters an official workflow.

Use only when the user explicitly asks to maintain a durable, planner-ready specification workspace for a recurring business workflow.

Use only when the user explicitly asks to deepen a proven UiPath architecture hotspot into ranked design options and a safe handoff.

Design a deep UiPath component or project contract by exploring several genuinely different shapes before selecting one. Use for reusable libraries, workflow interfaces, coded automation modules, agents, Maestro processes, API workflows, human tasks, queue contracts, and integration adapters that need clear seams and testable behavior.

Define and enforce public entry points and dependency boundaries across a UiPath solution or repository. Use when reusable libraries, coded components, agents, apps, API workflows, tests, and orchestration projects have deep imports, circular dependencies, duplicated contracts, or unclear ownership that makes agent navigation and safe change difficult.

Build a deliberately throwaway UiPath-oriented prototype to answer one design question. Use when a team must validate a selector strategy, extraction result shape, state model, human-review experience, queue contract, API interaction, agent behavior, or orchestration flow before committing to production architecture.

Plan a behavior-preserving UiPath refactor after an architecture direction is selected. Use when a proven hotspot needs small implementation steps, safety nets, compatibility rules, stop conditions, and rollback points across workflows, packages, queues, selectors, or orchestration artifacts.

Plan and execute a bounded, reversible migration from one repeated UiPath project pattern to another. Use for naming changes, configuration key changes, queue field migrations, package references, argument conventions, test fixture updates, documentation conventions, or other mechanically discoverable transformations across many files or projects.

Use only when the user explicitly asks to install and prove local and CI quality gates for a UiPath repository.

Create a fast, deterministic, red-capable reproduction and regression harness for a UiPath defect after the incident, symptom, or cause has been anchored by uipath-troubleshoot or the owning product skill. Use when a confirmed defect needs repeatable evidence before and after a fix. Do not use to perform root-cause diagnosis, investigate live production broadly, or apply the fix.

Build a requirement-to-implementation-to-test-to-evidence traceability matrix from an approved SDD, official uipath-review report, Test Manager evidence, and release artifacts. Use when the user explicitly needs coverage, missing-evidence analysis, auditability, UAT mapping, or release traceability. Do not perform the underlying artifact quality review, invent requirement coverage, or replace Test Manager reporting.

Resolve an in-progress source-control merge or rebase conflict involving UiPath project artifacts by recovering the intent of both sides, using structure-aware edits, and rerunning the owning product validations. Use for conflicts in project files, JSON manifests, coded automation, XAML, Maestro artifacts, solution wrappers, tests, documentation, and generated metadata.

Use only when the user explicitly asks to install and test command guardrails around destructive Git and UiPath release operations.

Use only when the user explicitly asks to refine an approved UiPath plan into session-sized tracer-bullet tasks with blocking edges.

Apply behavior-first red-green development to UiPath automation work. Use when implementing a feature or defect through tests, when critical business rules need durable regression coverage, or when a team must choose the right public seams across workflows, coded components, queues, APIs, agents, Maestro, and human tasks.

Use only when the user explicitly asks to facilitate UiPath UAT and capture reproducible business acceptance evidence.

Design end-to-end observability for a UiPath process, agent, Maestro journey, integration, application, or multi-project solution. Use for correlation, structured events, business and technical metrics, SLOs, alert logic, dashboard requirements, runbook links, retention, and support ownership. This skill designs the model only; live job analytics belong to uipath-insights, Action Center task operations to uipath-tasks, audit events to uipath-admin, platform resources to uipath-platform, and causal diagnosis to uipath-troubleshoot.

Aggregate authoritative build, review, test, security, operational, governance, deployment, and support evidence into a Ready, Conditionally Ready, or Not Ready verdict for a specific UiPath release unit and target. Use after official product validation and review evidence exists. Do not run product review, Test Manager operations, policy changes, deployment, activation, or production mutation.

Create an interactive or document-based wizard for a UiPath setup, access, migration, deployment-preparation, or operational procedure that requires human actions. Use when a repeatable manual process involves portals, approvals, values to capture, environment configuration, credentials, tenant resources, or irreversible checkpoints that should not be re-explained from scratch.

Perform project-level threat modeling and evidence-backed security, privacy, AI, integration, and operational control assessment for a defined UiPath solution design or release. Use when the team needs data-flow threats, trust boundaries, misuse cases, control gaps, residual risks, or security evidence requests. Do not author or deploy UiPath governance policies, manage identities or roles, query audit logs, operate tenant resources, or replace uipath-review.

Use only when the user explicitly asks to create a stateful, practice-led UiPath learning workspace tied to a real mission.

Design, review, and improve reusable AI skills for UiPath work. Use when creating a skill for discovery, architecture, development, testing, operations, governance, training, or project management; when deciding whether a workflow belongs in a custom skill or the official UiPath catalog; or when an existing skill is inconsistent, bloated, poorly triggered, or difficult to evaluate.

Develop clear UiPath solution narratives from raw notes, evidence, design artifacts, demos, and implementation outcomes. Use when preparing executive proposals, architecture explanations, demo scripts, community talks, case studies, articles, release communications, or customer-facing stories that must introduce concepts in a logical order and preserve source truth.

Use only when the user explicitly asks to scaffold and validate a consistent UiPath training lab from an approved curriculum.