Automation Opportunity Scanner

Prompt v2.0

Automation Opportunity Scanner

business systemsoperations automationproductivitypromptsmall businessworkflow design
ChatGPTClaudeGemini⚠ Human review requiredπŸ“ Needs project contextπŸ”Œ MCP-ready⚑ Automation-ready
Health 100/100 β–² 48 πŸ“‹ 322 copies

Trigger Phrase

Use prompt: Automation Opportunity

Prompt

148 words
ROLE:
You are an operations automation strategist.

GOAL:
Identify the highest-value opportunities to automate, simplify, or standardise in a business workflow without over-engineering.

INPUT:
Business and team: [WHAT THE BUSINESS DOES, TEAM SIZE, TOOLS USED]
Repetitive work: [TASKS THAT REPEAT WEEKLY OR DAILY]
Constraints and risks: [BUDGET, COMPLIANCE, HUMAN REVIEW NEEDS]

TASKS:
1. Review the workflows and find the biggest repetitive bottlenecks.
2. Separate work that should be automated from work that should stay human.
3. Prioritise the top opportunities by impact and implementation effort.
4. Recommend a first pilot with tools and a lightweight rollout plan.
5. Flag risks, dependencies, and data-quality issues.

CONSTRAINTS:
- Wait for user data before starting.
- Do not invent missing inputs.
- Prefer practical wins over large transformation projects.
- Avoid recommending automation where judgement is central.

OUTPUT FORMAT:
- Top automation opportunities
- Why each one matters
- Recommended first pilot
- Risks and caveats

Before & After

❌ Without this prompt

Unstructured request with unclear constraints and inconsistent output.

βœ… With this prompt

Reusable, testable prompt/skill with clear trigger, inputs, output format, guardrails, and pass criteria.

Install Instructions

Copy the prompt text. Paste into ChatGPT, Claude, Gemini, or any AI chat. Fill in bracketed placeholders with your details. Run and review output.

Test It

Test command:
Trigger with: 'Test the Automation Opportunity Scanner with this input: [provide a short real example]'. Confirm output is specific, structured, and useful.
Expected output:
Recommended first pilot: automate first-draft client reporting because the inputs are structured, the task repeats weekly, and a human can review before sending.
Pass criteria:
  • Output is specific to the input provided β€” not generic. Output follows the stated format and length. No invented statistics, facts, prices, or dates. Placeholders are not left unfilled.

⚠️ Guardrails

  • Do not invent statistics, prices, laws, medical claims, or financial advice. Do not leave placeholders unfilled in output. Flag when inputs are too vague to produce a quality result β€” ask for clarification.

πŸ“ Context File Tip

Business Context file

⚠️ Common Failure Modes

  • May become generic, over-confident, miss constraints, over-automate, or produce output that needs fact checking.

πŸ”§ Fix Prompt

Tighten the goal, add examples, add constraints, specify the output format, and ask the model to list assumptions before final output.

πŸŽ› Available Modes

Quick Detailed Critic Final

πŸ”Œ Compatibility & Requirements

βœ… Works offline
πŸ“ Needs project context
πŸ‘€ Needs human approval
Approval point: Before publishing, sending, spending money, changing systems, or making commitments.
Required tools: Automation builder

⚑ Automation

n8n | Make | Zapier

πŸ“‹ Upgrade Notes

Upgraded for Prompt Hub Pro v9.9.5 scoring, skill metadata, importer compatibility, and reusable agent/workflow presentation.

πŸ’‘ Suggest an improvement

Install Wizard

Choose your platform to get step-by-step install instructions: