Total 58,115 skills
Showing 12 of 58115 skills
Write tests from a feature spec, treating the spec and its flow contract as the source of truth, stubbing pending tests where implementation is missing and halting when code and spec disagree. Use when the user says "write tests from this spec", "fill the coverage gaps", "prove this wizard works", or after spec-assess-coverage identifies what is untested.
Sweep every spec in the estate for maintenance debt — partial behaviours with no ticket, ageing future behaviours, roll-up statuses that disagree with their behaviours, long-standing open questions, and modules with no specs at all. Use when the user asks "what state are our specs in", "review the spec estate", "which open questions are blocking work", or on a periodic cadence. Reports only.
Complete the incomplete behaviours in current scope — read the scoped specs, build a queue, and keep working across turns until the definition of done is satisfied. Use when the user says "run the implementation plan", "continue the plan", "finish the scoped work", "complete the incomplete behaviours", "ship B4", or names a chunk ID.
Two-model debate review of a GitHub PR or GitLab MR, posted as inline comments. Use for any PR/MR review request.
Use when a user is installing DaVinci Resolve for the first time, switching machines, configuring a media drive for video editing, or asking about backup/proxy settings. Triggering symptoms include phrases like "just installed Resolve", "set up DaVinci Resolve", "drop frames during playback", "where should my media live", "how do I configure backups", or any DaVinci Resolve installation/preferences question.
Use when a user needs branded titles, animated lower-thirds, or a logo intro for their video — uses Resolve's Text+ node and Fusion's animation modifiers to create reusable title templates. Triggering symptoms include phrases like "add a name lower third", "animated logo intro", "title card with gradient", "save title as a template", "introduce a guest", or any DaVinci Resolve title/text question.
Use when a user has podcast, interview, or talking-head audio that needs cleanup — denoise, de-hum, level dialogue, and duck music under voice. Triggering symptoms include phrases like "podcast audio is noisy", "background hum in interview", "music too loud under voice", "level out my voiceover", "fix my podcast", or any DaVinci Resolve Fairlight audio cleanup question.
UiPath bug reports and improvement suggestions via `uip feedback send`. Use for 'report issue', 'send feedback', 'file a bug', or the /uipath-feedback command. For investigating an error rather than reporting one→uipath-troubleshoot.
Skills to interact with your Dataproc clusters and jobs.
UiPath platform ops via the uip CLI — use for ANY task hitting UiPath Cloud / Orchestrator / Studio Web / Integration Service / Data Fabric / LLM Gateway. Load BEFORE writing code that calls a UiPath API. Covers auth, folders, assets, queues, storage buckets, libraries, webhooks, triggers, processes, jobs, machines, users, roles, sessions, calendars, IS connectors/connections/activities, Data Fabric entities/records/files/choice-sets (`uip df`), BYO LLM product configurations, BYO guardrail (BYOG) configurations, context grounding, traces (execution traces and spans + trace feedback / annotation), licensing. For 'why did X fail' / root-cause→uipath-troubleshoot. For org/tenant audit trail / audit logs / login history→uipath-admin. For `uip solution` lifecycle→uipath-solution. For PDD/SDD design→uipath-planner. For workflow code (.xaml/.cs)→uipath-rpa, .flow (incl. Data Fabric connector nodes)→uipath-maestro-flow, .bpmn→uipath-maestro-bpmn, agents (.py/agent.json)→uipath-agents, Test Manager→uipath-test.
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.
Maintain build-time skill flavors in the UiPath skills repository. Use when adding or editing skill-flavor marker blocks, sparse flavor overrides, generic flavor discovery, marker-free default or custom npm packages, package inspection, flavor CI, or composer/package tests. Preserve SKILL.md as the complete default, keep overrides exceptional, and validate finished trees and tarballs.