Skip to content

About

Developer workflow for scaffolding, validating, deploying, and verifying UiPath Coded Web Apps and Action Apps.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

UiPath Coded App Launchpad

Create developer-ready UiPath Coded Web Apps and Coded Action Apps through one guided workflow: shape a small use case, check prerequisites, scaffold a TypeScript interface, display safe demo data, build, authenticate, publish, deploy, open the live URL, and optionally publish the source to GitHub.

Important

This is an independent community skill. It is not an official UiPath product. Current UiPath commands, SDK contracts, OAuth scopes, and platform operations remain owned by the installed official UiPath skills.

What this skill helps you do

  • Turn a simple idea into a focused UI without a lengthy discovery process.
  • Confirm whether the developer machine is ready before creating files.
  • Build an initial React and TypeScript UI with clearly labeled fictional data.
  • Configure @uipath/uipath-typescript only when live UiPath services are needed.
  • Reuse a matching UiPath CLI login or guide the user through interactive authentication.
  • Recommend consistent application, package, Git branch, and Orchestrator folder names.
  • Find or create an Orchestrator folder with explicit approval.
  • Produce a least-privilege access request when deployment access is missing.
  • Build, pack, publish, and deploy through the official uipath-coded-apps owner.
  • Open and visually verify local and deployed Web App URLs.
  • Create a structured application README and safely publish source to GitHub.

Delivery modes

Mode Result
local Scaffold, demo UI, structured README, local browser verification, and successful build
deploy Local result plus UiPath authentication, folder resolution, pack, publish, deploy, and live URL verification
deploy-and-git Deployed result plus intentional Git commit, push, and draft GitHub pull request

Install

1. Install the official UiPath skills

Install the UiPath CLI and official skill catalog according to your organization's approved setup. With the UiPath CLI available, the standard skill installation is:

uip skills install

The official uipath-coded-apps and uipath-platform skills remain the product and tenant-operation owners used by this skill.

2. Install this skill from GitHub

For Codex:

npx skills add 1aifanatic/uipath-coded-app-launchpad `
  --skill create-uipath-coded-app `
  --agent codex `
  --global `
  --yes

Start a new Codex conversation after installation so the skill is discovered.

Quick start

Invoke the skill by name and provide the desired app type and delivery mode:

Use $create-uipath-coded-app.

Create a Coded Web App named claims-review-dashboard.
Build a responsive dashboard for claims reviewers to see pending claims.
Use safe fictional demo data and clearly label it.
Use local delivery mode and open the interface in a browser.
Create the project in C:\projects\claims-review-dashboard.

For complete local, deployment, SDK, Action App, access, and GitHub examples, see the Prompt Cookbook.

How the workflow operates

Use case and app type
  -> delivery authority
  -> machine preflight
  -> UI and demo data
  -> SDK and authentication, when needed
  -> build and local browser verification
  -> Orchestrator folder and access
  -> pack, publish, deploy
  -> live browser verification
  -> optional GitHub publication

The skill coordinates installed owners rather than duplicating their current product behavior:

  • uipath-coded-apps owns Coded App artifacts and lifecycle operations.
  • uipath-platform owns authentication, tenant, folder, user, group, and role operations.
  • github:yeet owns intentional GitHub commit, push, and pull-request publication.
  • Browser control owns visual navigation and verification when available.

Prerequisite checker

The bundled Windows PowerShell checker is read-only. It reports readiness without installing software, authenticating, changing tenant state, deploying, or pushing Git changes.

Check readiness for a Web App that will be published to GitHub:

powershell -NoProfile -ExecutionPolicy Bypass `
  -File .\create-uipath-coded-app\scripts\check-prerequisites.ps1 `
  -Stage Scaffold `
  -AppType Web `
  -SourcePublish GitHub `
  -OutputFormat Json

Check an existing project before build:

powershell -NoProfile -ExecutionPolicy Bypass `
  -File .\create-uipath-coded-app\scripts\check-prerequisites.ps1 `
  -Stage Build `
  -AppType Web `
  -ProjectPath C:\projects\claims-review-dashboard `
  -RequirePlatformSdk `
  -OutputFormat Json

Exit code 0 means all required checks passed. Exit code 1 means at least one required check failed. The JSON report does not print .env values, credentials, access tokens, folder keys, or deployment URLs.

Repository structure

uipath-coded-app-launchpad/
  README.md
  docs/
    PROMPTS.md
  create-uipath-coded-app/
    SKILL.md
    agents/openai.yaml
    references/
    scripts/check-prerequisites.ps1

Safety model

The skill requires or recognizes explicit authority before it performs consequential operations. It does not silently:

  • Install or upgrade global software.
  • Create or change OAuth applications.
  • Create Orchestrator folders or alter access.
  • Overwrite non-empty destinations.
  • Publish or deploy to a tenant.
  • Create GitHub repositories, push branches, or stage unrelated changes.

It never asks for raw access tokens, passwords, or client secrets. Interactive authentication remains in the supported UiPath or GitHub login flow.

Validation status

The current package has been structurally validated. Its prerequisite checker has been exercised on Windows PowerShell 5.1 against:

  • Web and Action App success fixtures.
  • Git and GitHub prerequisites.
  • Explicit app-type enforcement.
  • Missing tools and invalid projects.
  • Missing README and invalid folder-key failures.
  • HTTPS deployment URL validation.
  • Secret-redaction behavior.

The checks do not claim runtime compatibility outside the observed environment, and fixture success does not replace a real application build or tenant deployment.

Skill source

About

Developer workflow for scaffolding, validating, deploying, and verifying UiPath Coded Web Apps and Action Apps.

Topics

Resources

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages