Help us improve
Share bugs, ideas, or general feedback.
From uipath
Discovers automation opportunities across an organization by mining Slack, email, wikis, and business systems. Produces a prioritized 4-tier UiPath-ready report with implementation paths.
npx claudepluginhub uipath/skills --plugin uipathHow this skill is triggered — by the user, by Claude, or both
Slash command
/uipath:uipath-automation-discoveryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate how employees actually work, then identify and prioritize internal
Guides through a 5-question workflow intake then audits Gmail, Calendar, Slack, and task trackers to identify automation opportunities ranked by impact and effort.
Designs UiPath solutions from PDDs, generates SDDs, and derives multi-project task plans with live TaskCreate calls. Detects project types and routes to specialists.
Generates step-by-step automation runbooks (.md files) from workflow patterns by analyzing activity timelines with search and browse tools. Useful for scripting manual processes after /discover-patterns.
Share bugs, ideas, or general feedback.
Investigate how employees actually work, then identify and prioritize internal automation opportunities backed by real behavioral evidence. Produces a UiPath-ready backlog with recommended implementation paths.
/uipath-automation-discoveryPhase 0: INTAKE → Gather context, verify access, agree on scope and privacy
Phase 1: MINE → Gather raw data from all verified sources
Phase 2: ANALYZE → Extract patterns, SPOFs, replicable models, gaps
Phase 3: REFLECT → Layer on business strategy for strategic gaps
Phase 4: REPORT → Produce prioritized report with 4 tiers
Phase 5: HANDOFF → Map opportunities to UiPath implementation skills
Stop conditions: Quick scan caps at 10 findings, Standard at 25, Deep dive at 35. Max 2 retries per failed source. Phase 1 timeboxed at 3 hours for deep dives. See references/intake-guide.md §0G for details.
Build a complete picture before mining. Ask — don't assume.
See references/intake-guide.md for detailed steps covering company context, tool inventory, access verification, org structure, output preferences, user hypotheses, scope control, and privacy authorization.
Key outputs from intake:
Cast a wide net. Prioritize by signal density. Use parallel agents (Agent tool
with subagent_type: general-purpose, one agent per source category).
See references/mining-guide.md for detailed per-source guidance on what to look for and how to search.
Source priority when time is limited:
Note: Web research (priority 7) feeds Phase 3 strategic analysis. Even under time pressure, do a brief web search for the company's public financials and strategy — this takes minutes and enables Tier 4 findings.
Work with whatever access is verified. Even messaging channels alone can yield 15+ opportunities. Each additional source adds depth, not changes the methodology.
Checkpoint: After Phase 1, share a raw signal summary with the user: "I found X help channels, Y existing automation projects, Z departments. Want me to go deeper on anything before I analyze?" If the user requests deeper mining, run at most 1 additional targeted pass, then proceed.
Transform raw data into structured findings.
Per department, answer: What's manual? What questions repeat? What approvals stall? What reports are compiled by hand? What data is swivel-chaired between systems? What handoffs break? What scheduled tasks are done by humans?
Identify roles that are sole responders. If they're out, the process stops. Pseudonymize by default — use role/team labels unless naming is authorized.
| Role/Pseudonym | System/Channel | Function | Risk |
These are the highest-urgency targets.
The most important finding. Look for automation already working in one area that could replicate to others:
| Working Model | Where It's Missing | Addressable Volume |
Greenfield case: If no existing automations are found (nothing to replicate), Tier 1 will be empty. Promote the highest-volume Tier 2 finding to the headline slot and note that the company has no proven models to replicate yet.
| Department | Existing Automations | Key Gap |
Flag ZERO-coverage departments as biggest blind spots.
For promising existing projects, extract: pain point, manual process today, volume/frequency, ROI if documented, systems involved, dev status.
Apply low-confidence handling per Critical Rule 4.
Checkpoint: Share analysis summary with user before reflecting: "Here are the top patterns, SPOFs, and replicable models. Anything surprise you? Anything I should investigate further?" If the user requests deeper analysis, run at most 1 additional targeted pass, then proceed to Phase 3.
Identify gaps behavioral data won't reveal.
Research via web search, investor docs, or internal strategy pages: revenue, growth, strategic priorities, competitive challenges, key metrics.
For each of the company's documented strategic priorities, ask: "Is there an internal automation that accelerates this?" Only include Tier 4 opportunities that map to both a documented strategic priority and an observed Phase 1-2 gap.
Use this table as a starting prompt (covers common enterprise priorities) — adapt to the company's actual strategy and do not include rows where no gap was observed:
| Priority | Potential Automation |
|---|---|
| Revenue growth | Lead scoring, pipeline acceleration, renewal prediction |
| Cost reduction | Self-service portals, report automation, process standardization |
| Customer retention | Health scoring, churn prediction, proactive outreach |
| Market expansion | Localization, compliance automation, partner enablement |
| Compliance | Audit trails, policy enforcement, automated reporting |
| Talent retention | Onboarding, engagement monitoring, career pathing |
Does the company use its own product internally? Is there a coverage metric? What's the narrative gap between what they sell and what they do internally?
Produce a prioritized report in the user's preferred platform. See references/report-template.md for structure, tier definitions, evidence standards, and platform-specific guidance.
Map each Tier 1-2 opportunity to a UiPath implementation path. Add a "Next Step" column to the report's Tier 1-2 tables.
| Opportunity Type | Recommended Skill | Artifact |
|---|---|---|
| Desktop/app automation (UI, data entry) | →uipath-rpa | Coded workflow (.cs) or XAML |
| Multi-step automation or orchestration | →uipath-maestro-flow | Flow (.flow) |
| Scheduled / triggered automation | →uipath-maestro-flow | Flow with trigger |
| Agent-based (conversational, reasoning) | →uipath-agents | Coded agent |
| Approval / human review gate | →uipath-human-in-the-loop | HITL node in Flow |
| Cross-system integration | →uipath-platform | Integration Service connector |
For complex or multi-component opportunities, hand off to →uipath-planner for full solution design.
Parallelize Phases 1-3 (Phase 0 is interactive — do not parallelize intake).
Max 3 concurrent agents using the Agent tool with subagent_type: general-purpose:
Always share interim findings. Don't disappear for hours. Check in after each phase with a brief summary and ask if the user wants to adjust scope.