New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Uipath Test

by UiPath in UiPath/skills

UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites.

MITAuto-check: notesProductivity & Automation

Install Uipath Test

skills CLI
$ npx skills add UiPath/skills --skill uipath-test -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install UiPath/skills uipath-test --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/UiPath/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/uipath-test .claude/skills/uipath-test && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
uipath-test
GitHub stars
168
Token cost
~4.8k tokens
SKILL.md length
2,144 words
Files
7 (incl. references)
Skills in repo
28
Repo updated
First seen
Licence
MIT

At a glance

UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites.

  • Works in 10 steps: Always check login first: run uip login… → Always pass --output json to every uip… → Cap retries at 3 for any failing uip… → …
  • Tasks that involve Workflow automation
  • SKILL.md covers Use For, Concepts and CLI, Commands and Critical Rules, plus 4 more sections
  • Needs PROJECT_KEY and TEST_SET_KEY

What it does

Uipath Test is an agent skill from UiPath/skills. UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites. For Orchestrator→uipath-platform. For Studio/RPA test automation authoring→uipath-rpa.

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/custom-fields-guide.md`, `references/failure-triage-guide.md` and `references/object-labels-guide.md`).

It sits in Productivity & Automation, covering Workflow automation. It works with Playwright. The repository describes itself as: This is a repository of skills for interfacing UiPath capabilities to external developers. The licence is MIT.

When your agent uses it

  • Tasks that involve Workflow automation

Example prompts

  • “/uipath-test”

Requirements

  • A credential in NAME_OR_KEY
  • A credential in PROJECT_KEY
  • Pre-approved tools (allowed-tools): Bash, Read, Write, Glob, Grep

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Always check login first: run uip login status --output json before any Test Manager operation. If unauthenticated, run uip login.
  2. Always pass --output json to every uip command, without exception.
  3. Cap retries at 3 for any failing uip command. After three failures, stop and report the error; never use direct REST APIs.
  4. An empty list stops the operation and informs the user rather than proceeding with a null key. Exception: empty tm testcases list --filter…
  5. Confirm before delete: confirm the target resource key unless the user already authorized that exact delete. Every delete requires --yes…
  6. For a required folder key, use uip or folders list -n --all --output json when the user named the folder; when choosing one yourself, omit…
  7. Discover before assuming: never guess automation names, folder keys, project IDs, or testcase keys; run the matching list first, such as…
  8. Narrow named-entity list calls server-side: when given a name, key, label, or tag, inspect uip tm list --help or uip or list --help for…
  9. Default-folder recovery: uip tm testcases run and uip tm testsets run require a project default folder. Attempt the run first. Only when…
  10. Any uip failure or ambiguity stops and asks the user: this includes command errors, malformed output, unclear flags/values, multiple…

What it can do on your machine

Read from SKILL.md and the folder at commit bc2e230. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • PROJECT_KEY
    • TEST_SET_KEY
    • TEST_CASE_KEY
    • FOLDER_KEY
    • NAME_OR_KEY
    • TEST_SET_NAME_OR_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Uipath Test loads about 4.8k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 2,144 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~59
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from UiPath/skills at commit bc2e230, republished under its MIT licence (© UiPath). 2,144 words, ~4,799 tokens.

Download SKILL.mdSave it as .claude/skills/uipath-test/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
uipath-test
description
UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites. For Orchestrator→uipath-platform. For Studio/RPA test automation authoring→uipath-rpa.
allowed-tools
Bash, Read, Write, Glob, Grep
user-invocable
true

UiPath Test Assistant

Manage UiPath Test Manager projects, requirements, test cases, test sets, executions, logs, attachments, results, custom fields, labels, and persona-tailored shareable test reports.

Use For

Test Manager CRUD; execution analysis, coverage, regression trends, failure rates, go/no-go summaries; failed-run triage; flaky-versus-regression analysis; failure evidence; and shareable QA-engineer, developer, or release-manager reports.

Concepts and CLI

Requirements define what must be tested; test cases define scenarios and may contain teststeps; test sets group cases; executions are created when a test set or testcase runs. Testcase logs record a testcase in an execution and provide navigation; test-step logs record steps; testcase-log assertions are assertion steps.

External Playwright packages are suites packaged and uploaded to Orchestrator. Ingestion auto-creates one testcase per Playwright test, without a link step, and labels each PW_Tag_*, PW_Project_*, PW_Suite_*, and PW_File_*. They run on serverless cloud runtimes; see references/playwright-first-mile-guide.md.

Use uip tm; discover syntax with uip tm --help and uip tm <command> <subcommand> --help. Always pass --output json to every uip command; all commands below require it.

Commands

Projects, folders, and requirements
  • Projects: uip tm project list --filter <NAME_OR_KEY> finds by name/key; project create --name <PROJECT_NAME> --project-key <PROJECT_KEY> creates; project update --project-key <PROJECT_KEY> --name <PROJECT_NAME> updates name/description; project delete --project-key <PROJECT_KEY> deletes; project set-default-folder --project-key <PROJECT_KEY> --folder-key <FOLDER_KEY> sets the default Orchestrator folder; project clear-default-folder --project-key <PROJECT_KEY> clears it; project owners list --project-key <PROJECT_KEY> [<PROJECT_KEY> ...] lists owners.
  • Get folder keys with uip or folders list -n <name> --all --output json; it returns all folders visible to the current user.
  • Prefix with uip tm requirements: list --project-key <PROJECT_KEY>; list-by-test-execution --project-key <PROJECT_KEY> --execution-id <uuid>; get --project-key <PROJECT_KEY> (--requirement-id <uuid> | --requirement-key <key>) (mutually exclusive UUID/key); create --project-key <PROJECT_KEY> --name <name>; update --project-key <PROJECT_KEY> --requirement-id <uuid> (updates name/description and requires at least one of --name or --description); delete --project-key <PROJECT_KEY> --requirement-ids <uuid...> (variadic IDs); export --project-key <PROJECT_KEY> --output-file <path> (exports .xlsx); list-testcase-ids --project-key <PROJECT_KEY> --requirement-id <uuid>; testcases --project-key <PROJECT_KEY> --requirement-id <uuid> (--add-testcase-ids <uuid...> | --remove-testcase-ids <uuid...>) (mutually exclusive attach/detach selectors).
Test cases
  • uip tm testcases create --project-key <PROJECT_KEY> --name <TEST_CASE_NAME>; list --project-key <PROJECT_KEY> optionally --filter <text> matching name/key by PREFIX, not substring; update --project-key <PROJECT_KEY> --test-case-key <TEST_CASE_KEY> --name <TEST_CASE_NAME> updates name, description, precondition, or postcondition and requires at least one field; delete --project-key <PROJECT_KEY> --test-case-key <TEST_CASE_KEY> deletes by key.
  • link-automation --project-key <PROJECT_KEY> --test-case-key <TEST_CASE_KEY> --folder-key <FOLDER_KEY> --package-name <PACKAGE_NAME> --test-name <TEST_NAME> links Orchestrator package automation, optionally --entry-point-id <PACKAGE_ENTRY_POINT_ID> (from list-automations) to bind by id, which overrides --test-name; unlink-automation --project-key <PROJECT_KEY> --test-case-key <TEST_CASE_KEY> unlinks; list-automations --project-key <PROJECT_KEY> --folder-key <FOLDER_KEY> lists folder test entry points, optionally --package-name <PACKAGE_NAME>, each row carrying PackageEntryPointId; list-testsets --project-key <PROJECT_KEY> --test-case-key <TEST_CASE_KEY> lists containing sets.
  • Steps: uip tm testcases steps list --project-key <PROJECT_KEY> --test-case-id <TEST_CASE_ID> lists manual steps using --test-case-id <UUID>, not --test-case-key; uip tm testcases list-steps is an alias. steps get --project-key <PROJECT_KEY> --step-id <UUID> gets; steps add --project-key <PROJECT_KEY> --test-case-id <UUID> --description <text> adds flag-mode steps (--description required), or steps add --project-key <PROJECT_KEY> --test-case-id <UUID> --step '<json>' [--step '<json>' ...] adds repeated JSON steps (mutually exclusive with flag mode and not atomic: earlier steps persist if a later one fails); steps update --project-key <PROJECT_KEY> --step-id <UUID> updates passed fields only; steps move --project-key <PROJECT_KEY> --step-id <UUID> --target-position <n> moves to 0-based position; steps delete --project-key <PROJECT_KEY> --step-id <UUID> --yes deletes.
  • list-result-history --project-key <PROJECT_KEY> --test-case-id <TEST_CASE_ID> lists history, optionally --only-failed, --filter, --limit, --offset. run --project-key <PROJECT_KEY> --test-case-id <TEST_CASE_ID> --name <EXECUTION_NAME> --execution-type <manual|automated|none|mixed> starts an execution for one or more space-separated testcase UUIDs; optionally --async, --folder-key, --robot-user-key, --machine-key.
  • uip tm testcases add --test-set-key <TEST_SET_KEY> (--test-case-keys <KEY1> <KEY2> … | --labels <Label1> <Label2> …) adds by explicit keys or every testcase carrying at least one label; selectors are mutually exclusive and variadic space-separated. Keys also accept comma form (DEMO:1,DEMO:2), labels do not (--labels A,B is one label). Label matching is OR, exact, and case-sensitive; quote labels containing spaces. uip tm testcases remove --test-set-key <TEST_SET_KEY> --test-case-keys <KEY1,KEY2,...> removes comma-separated keys.
  • Use --test-case-id <UUID> with run, steps list, steps add, and list-result-history; obtain it from uip tm testcases list --output json (Id). Use singular --test-case-key <PROJECT_KEY:NUMBER> with update, delete, link-automation, unlink-automation, and list-testsets. Use plural --test-case-keys <KEY1,KEY2,...> for comma-separated test-set bulk membership. Use --step-id <UUID> with all steps commands except list and add; obtain it from steps list (Id).
Test sets and executions
  • uip tm testsets create --project-key <PROJECT_KEY> --name <TEST_SET_NAME>; list --project-key <PROJECT_KEY> optionally --filter <text>, --folder-key, --include-last-execution; update --test-set-key <TEST_SET_KEY> --name <TEST_SET_NAME> updates name/description; delete --test-set-key <TEST_SET_KEY>; list-testcases --project-key <PROJECT_KEY> --test-set-key <TEST_SET_KEY> lists assigned cases.
  • uip tm testsets run --test-set-key <TEST_SET_KEY> runs and returns an execution ID; optionally --execution-type <automated|manual|mixed|none> (default automated), --input-path <FILE>, and for Playwright --playwright-project <name>. uip tm testsets playwright-context --test-set-key <TEST_SET_KEY> probes status and returns IsPlaywright, available projects, and selected projects.
  • Keys are PROJECT_KEY:NUMBER. Add/remove membership with uip tm testcases add/uip tm testcases remove, not testsets verbs. For Playwright sets, --playwright-project <name> takes one case-sensitive playwright.config name — at most one project per execution — and persists the selection. Every testcase must come from one Playwright package; an unknown name fails fast listing the valid ones. Probe first with playwright-context and branch on IsPlaywright. Both require Test Manager Playwright support and a CLI carrying external-package commands. See references/playwright-first-mile-guide.md, which begins with the availability check and absent-support action.
  • uip tm executions list --project-key <PROJECT_KEY> lists top n, optionally --test-set-id <UUID>, --filter <text>, --limit, --offset; use for the common one-test-set or single-project query. list-filtered --project-key <PROJECT_KEY> supports --test-set-id, --updated-by, --search, --labels, --test-execution-ids, --sort-by, --limit, --offset; use only for label filtering, multiple execution IDs, custom ordering, or --updated-by.
  • get-stats --execution-id <EXECUTION_ID> --project-key <PROJECT_KEY> returns aggregate statistics; run --execution-id <EXECUTION_ID> --project-key <PROJECT_KEY> --execution-type <TYPE> reruns, optionally --test-case-log-ids <UUID...> (space-separated) and --async; retry --execution-id <EXECUTION_ID> retries only failed cases, optionally --project-key, --test-set-key, --execution-type; testcaselogs list --execution-id <EXECUTION_ID> --project-key <PROJECT_KEY> lists case logs, optionally --only-failed, --filter, --limit, --offset; this nested path is not a top-level executions verb. Use uip tm testcases run for testcase UUIDs, uip tm testsets run for a test-set key, and uip tm executions run to rerun an execution, optionally narrowed by case-log IDs.
Logs, reports, attachments, and results
  • uip tm testcaselog start --project-key <PROJECT_KEY> --execution-id <EXECUTION_ID> --test-case-id <TEST_CASE_ID> starts, optionally --run-id <NUMBER>. finish --project-key <PROJECT_KEY> --execution-id <EXECUTION_ID> --test-case-id <TEST_CASE_ID> --has-error <true|false> --executed-by <USER_ID> finishes, optionally --detail-link <URL>, --run-id, --is-post-condition-met.
  • uip tm testcaselog list-assertions --project-key <PROJECT_KEY> --test-case-log-id <TEST_CASE_LOG_ID> lists assertions; uip tm teststeplog list --project-key <PROJECT_KEY> --test-case-log-id <TEST_CASE_LOG_ID> lists step logs.
  • uip tm report get --execution-id <EXECUTION_ID> (--project-key <KEY> | --test-set-key <KEY>) summarizes a completed execution; exactly one project-identifying option is required. Passing only --execution-id exits with Provide --project-key or --test-set-key.
  • uip tm attachment download --execution-id <EXECUTION_ID> downloads testcase attachments; attachment upload --object-id <UUID> --object-type <type> --file <path> uploads to a Test Manager object, such as --object-type testCaseLog; uip tm result download --execution-id <EXECUTION_ID> downloads JUnit XML, optionally --project-key, --test-set-key, --result-path <DIR>.
Playwright pack

uip tm pack --project-path <dir> --type playwright --project-key <PROJECT_KEY> --name <PackageName> --package-version <ver> -o <out-dir> packs a Playwright suite into a .nupkg; a lockfile and @playwright/test are required. --package-version is NuGet/SemVer-style with three or four numeric parts and an optional prerelease/build suffix (1.0.0, 1.0.0.0, 1.0.1-beta.1); 1.0 and nonnumeric values are rejected. --project-key targets the Test Manager project for automatic testcase ingestion; --no-create-test-cases skips it; --dry-run previews. Upload with uip or packages upload <nupkg>. Packing is offline and needs no auth. The upload → ingestion → label-fill → run pipeline is in references/playwright-first-mile-guide.md.

Wait and user

uip tm wait --execution-id <EXECUTION_ID> waits for terminal state; optionally --project-key, --test-set-key, --timeout <SECONDS>. uip tm user get gets the authenticated user's profile.

Custom fields

Project-scoped custom-field definitions (attach to Requirement/TestCase/TestSet) plus per-object label and value rows, via uip tm customfield …. Full command surface — scopes, --object-type/--data-type enums (case-sensitive: Requirement|TestCase|TestSet, Text|Label), --values JSON semantics, and every label/value verb: references/custom-fields-guide.md.

Show full SKILL.md (869 more words)Show less
Object labels

Tag metadata via uip tm objectlabel … on Requirement, TestCase, TestSet, TestExecution, or TestCaseLog. Full list/get/add/remove surface, --label-types, and authoritative-set (--remove-other-labels) semantics: references/object-labels-guide.md.

Critical Rules

  1. Always check login first: run uip login status --output json before any Test Manager operation. If unauthenticated, run uip login.
  2. Always pass --output json to every uip command, without exception.
  3. Cap retries at 3 for any failing uip command. After three failures, stop and report the error; never use direct REST APIs.
  4. An empty list stops the operation and informs the user rather than proceeding with a null key. Exception: empty tm testcases list --filter may be a prefix miss; use Rule 8's prefix fallback and stop only if it also finds nothing. Empty filtered project or customfield lookups are real empty results and stop normally.
  5. Confirm before delete: confirm the target resource key unless the user already authorized that exact delete. Every delete requires --yes or -y; omission exits without deleting.
  6. For a required folder key, use uip or folders list -n <folder-name> --all --output json when the user named the folder; when choosing one yourself, omit --all to list only member folders. Run /uipath-platform for folder-management details.
  7. Discover before assuming: never guess automation names, folder keys, project IDs, or testcase keys; run the matching list first, such as uip tm testcases list-automations or uip or folders list -n <folder-name> --all.
  8. Narrow named-entity list calls server-side: when given a name, key, label, or tag, inspect uip tm <resource> list --help or uip or <resource> list --help for its narrowing flag and use it. Never list all then filter client-side; this applies to every entity across uip tm and uip or. Exception: tm testcases list --filter is prefix matching. If a mid-name term returns zero, retry with a broader contextual prefix; relist without --filter only if no workable prefix exists, paging through all results with --limit/--offset before concluding absence.
  9. Default-folder recovery: uip tm testcases run and uip tm testsets run require a project default folder. Attempt the run first. Only when failure text exactly includes "Message": "HTTP 400: Please assign folder to project level before executing testcases." and errorCode: itemNotFound, run uip tm project set-default-folder --project-key <PROJECT_KEY> --folder-key <FOLDER_KEY> --output json, then retry once. Get keys with uip or folders list -n <folder-name> --all --output json. Do not interpret other errors as missing folders: an unusable default gives opaque HTTP 5xx; a nonexistent folder key gives "HTTP 400: Internal Server Error." with errorCode: unknown. Both stop under Rule 10. Never overwrite a working default folder; an arbitrary folder may be rejected by Test Manager and break later runs. This is the only named run exception to Rule 10; all other run failures stop.
  10. Any uip failure or ambiguity stops and asks the user: this includes command errors, malformed output, unclear flags/values, multiple matches, missing identifiers, or unexpected schemas. Never fall back to REST. Exceptions are expected outcomes identified exactly: (a) the Rule 9 missing-folder error, handled there; (b) uip tm wait exit code 2 with Timed out after <N>s waiting for execution '<EXECUTION_ID>'. Last status: <status>., which means bounded timeout worked—report non-finish and continue remaining steps. Polling failed/interrupted/aborted ... and exit code 1 are real wait failures; every other failure stops.

Quick Start

  1. Verify auth: run uip login status --output json; if unauthenticated, run uip login. If needed, set the tenant with uip login tenant set <TENANT_NAME> --output json. Run /uipath-platform for more authentication details.
  2. Ask for the project name/key before any Test Manager call; for multiple projects collect all names/keys in one prompt. Resolve each with uip tm project list --filter <NAME_OR_KEY> --output json. Zero matches stop and ask; multiple matches require presenting candidates and asking the user to choose. Reuse the confirmed PROJECT_KEY downstream.
  3. Use as needed: uip tm testsets list --project-key <PROJECT_KEY> --filter <TEST_SET_NAME_OR_KEY> --output json; uip tm testsets list-testcases --project-key <PROJECT_KEY> --test-set-key <TEST_SET_KEY> --output json; uip tm executions list --project-key <PROJECT_KEY> --test-set-id <TEST_SET_ID> --limit 100 --output json; uip tm executions testcaselogs list --execution-id <EXECUTION_ID> --project-key <PROJECT_KEY> --output json; uip tm testcaselog list-assertions --project-key <PROJECT_KEY> --test-case-log-id <TEST_CASE_LOG_ID> --output json; uip tm teststeplog list --project-key <PROJECT_KEY> --test-case-log-id <TEST_CASE_LOG_ID> --output json.

Troubleshooting

For 401 Unauthorized on a REST API, run uip login to re-authenticate. For an unexpected command failure, first verify syntax with uip tm <command> --help, then authentication with uip login status --output json; Critical Rule 10 still governs whether to proceed.

Navigate to a Workflow

Anti-patterns

  • Do not proceed if authentication fails: all Test Manager API calls require a valid bearer token; fail fast rather than causing later 401s.
  • Do not guess command names: verb-noun composites are required; bare verbs do not exist. Confirm with uip tm <resource> --help --output json.
  • Do not link-automation Playwright test cases: ingestion links them automatically; manual linking is only for the Studio/RPA pipeline.

© UiPath, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/uipath-test of UiPath/skills.

  • SKILL.md
  • references/custom-fields-guide.md
  • references/failure-triage-guide.md
  • references/object-labels-guide.md
  • references/playwright-first-mile-guide.md
  • references/publish-and-link-guide.md
  • references/test-result-report-guide.md

Open the folder on GitHubat commit bc2e230

Compare with similar skills

Uipath Test next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Uipath Test compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Uipath Test this skillUiPath/skills168—~4.8kAutomated safety check: NotesMIT
Skyvern Browser AutomationSkyvern-AI/skyvern23k1 repos~2.9kAutomated safety check: PassAGPL-3.0
CUAWright Web Task Automationmicrosoft/CUAWright6k—~2kAutomated safety check: NotesMIT
UiPath Project Generatormarcelocruzrpa/uipath-ai-skills108—~6.9kAutomated safety check: PassMIT
Camoufox CLIBin-Huang/camoufox-cli3501 repos~4.5kAutomated safety check: PassMIT
N8n Docs Assistantn8n-io/n8n207k—~550Automated safety check: PassCustom licence

Similar skills

  • Skyvern Browser Automation

    Skyvern-AI/skyvern

    Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.

    23k GitHub starsUsed in 1 repo~2.9k tokens
    Productivity & AutomationAuto-check passed

  • CUAWright Web Task Automation

    microsoft/CUAWright

    Official

    Solves web tasks by driving a local Playwright browser one bash command at a time, saving a reusable script, screenshots and an action log for each run.

    6k GitHub stars~2k tokensUpdated 3 days ago
    Productivity & AutomationAuto-check: notes

  • UiPath Project Generator

    marcelocruzrpa/uipath-ai-skills

    Generates UiPath Studio projects, REFramework scaffolds, XAML workflows and expressions through 104 deterministic Python generators instead of hand-written XAML.

    108 GitHub stars~6.9k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed

  • Camoufox CLI

    Bin-Huang/camoufox-cli

    Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.

    350 GitHub starsUsed in 1 repo~4.5k tokens
    Productivity & AutomationAuto-check passed

  • N8n Docs Assistant

    n8n-io/n8n

    Official

    Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs.

    207k GitHub stars~550 tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Robocorp Automation

    robocorp/robocorp

    Bootstrap from an empty folder or build, debug, locally run, and validate Python automations built with Robocorp or Sema4.ai tooling, robocorp.tasks, rcc, robocorp-browser, and RPA Framework.

    653 GitHub stars~3.3k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from UiPath/skills

All 28 skills in this repo

  • Uipath Automation Discovery

    UiPath/skills

    UiPath automation discovery — mines Slack/email/wikis/CRM/HRIS/ERP for repetitive work, SPOFs, and replicable models; produces a 4-tier prioritized opportunity report with UiPath implementation…

    168 GitHub stars~3.7k tokensUpdated today
    Auto-check passed

  • Manage Skill Flavors

    UiPath/skills

    Maintain build-time skill flavors in the UiPath skills repository.

    168 GitHub stars~3.5k tokensUpdated today
    Auto-check passed

  • Uipath Functions

    UiPath/skills

    UiPath Coded Functions — deterministic Python or TypeScript/JavaScript units built with the uip function CLI (new -l py|ts|js, init, serve, run, pack, publish); the functions map in uipath.json…

    168 GitHub stars~3.6k tokensUpdated today
    Auto-check: notes

  • Uipath Maestro Bpmn

    UiPath/skills

    TRIGGER for authoring, operating or diagnosing UiPath Maestro BPMN.

    168 GitHub stars~4.2k tokensUpdated today
    Auto-check: notes

  • Uipath Maestro Case

    UiPath/skills

    TRIGGER for authoring UiPath Maestro Case plans as <Name.case.ts with the reference-mode TypeScript builder SDK (@uipath/maestro-builder-sdk/case), compiling to caseplan.json, and running the uip…

    168 GitHub stars~2k tokensUpdated today
    Auto-check: notes

  • Uipath Troubleshoot

    UiPath/skills

    UiPath causal investigation across every product, runtime, and activity package.

    168 GitHub stars~5.3k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Uipath Test

What does Uipath Test do?

UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites. Uipath Test is an agent skill from UiPath/skills. UiPath Test Manager — manage test projects, cases, sets, executions; generate reports; package and run external Playwright test suites.

When should I use Uipath Test?

Uipath Test fits situations like: tasks that involve Workflow automation.

How do I install Uipath Test in Claude Code?

Run `npx skills add UiPath/skills --skill uipath-test -a claude-code`. Or copy the skill folder (skills/uipath-test in UiPath/skills) into .claude/skills/uipath-test in your project. Claude Code loads it when a task matches its description.

How do I install Uipath Test in Codex?

Run `npx skills add UiPath/skills --skill uipath-test -a codex`. Or copy the skill folder (skills/uipath-test in UiPath/skills) into .agents/skills/uipath-test in your project. Codex loads it when a task matches its description.

Can I use Uipath Test in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add UiPath/skills --skill uipath-test -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uipath-test, .gemini/skills/uipath-test, .github/skills/uipath-test and .opencode/skills/uipath-test in your project.

What does Uipath Test need to run?

Going by SKILL.md and its folder, Uipath Test needs credentials named PROJECT_KEY, TEST_SET_KEY, TEST_CASE_KEY and FOLDER_KEY. Our summary lists: A credential in NAME_OR_KEY; A credential in PROJECT_KEY. Its frontmatter pre-approves these tools: Bash, Read, Write, Glob, Grep.

Does Uipath Test access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Uipath Test safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Uipath Test use?

Uipath Test is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Uipath Test use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9.1k tokens, read only when the agent opens those files.

What are the alternatives to Uipath Test?

Skills that share tags, products or a category with Uipath Test: Skyvern Browser Automation (Skyvern-AI/skyvern, 23k stars), CUAWright Web Task Automation (microsoft/CUAWright, 6k stars), UiPath Project Generator (marcelocruzrpa/uipath-ai-skills, 108 stars) and Camoufox CLI (Bin-Huang/camoufox-cli, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Uipath Test?

UiPath (a GitHub organization) maintains it in UiPath/skills, which has 168 GitHub stars. The repository holds 28 skills in this directory. The repository was last updated on October 9, 2026.

Source: UiPath/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.