More screenshots
Works with the AI Agents you already use
ai automation pre deployment risk auditor
An evidence-based risk auditor for AI workflows that identifies failure modes, security gaps, and deployment readiness.
$9.99
ai automation pre deployment risk auditor
Example session with this skill installed
I have an n8n workflow that captures customer leads from a website form. The form collects the customer's name, email, company, budget, and project description.
The workflow sends the project description to an AI model that classifies the lead as QUALIFIED or NOT QUALIFIED and extracts the company, budget, and project type.
If the lead is qualified, the workflow searches HubSpot by email. If no matching contact is found, it creates a new CRM record. It then creates a follow-up task for the sales team and sends the customer a confirmation email.
The HubSpot API retries failed requests up to 3 times.
The AI response is only checked for valid JSON and required fields. There is no documented idempotency key for CRM writes. We have not tested simultaneous duplicate submissions, timeout-after-commit behavior, or malicious customer messages.
A human reviews qualified leads before the sales team contacts them.
Audit this workflow for production readiness. Do not execute anything. Clearly distinguish OBSERVED, INFERRED, POTENTIAL, and UNKNOWN findings.
- Read your context and instructions
- Compiled the ai automation pre
AI AUTOMATION PRE-DEPLOYMENT RISK REPORT
Automation: n8n Lead Qualification → HubSpot → Sales Follow-up
Execution Status: NOT PERFORMED
No live workflow, API, CRM, credentials, or external system was executed or accessed. Findings are based only on the supplied workflow description.
Executive Summary
The workflow has several material reliability and control risks that should be addressed or verified before production deployment.
The strongest concerns are CRM duplication during retries or concurrent submissions, insufficient validation of AI-generated classification decisions, and unverified handling of untrusted customer input.
The supplied evidence is not sufficient to establish that the workflow is production-ready.
Deployment Decision: FIX BEFORE DEPLOYMENT
1. CRM Retry / Idempotency Risk
Status: POTENTIAL
Severity: P1 — HIGH-IMPACT RISK
The workflow retries failed HubSpot API requests up to three times, but no documented idempotency mechanism was supplied.
A timeout can occur after HubSpot successfully commits a CRM write but before the workflow receives the response. The workflow could then retry the operation.
A separate concurrent-submission scenario could also cause two executions to independently determine that a contact does not exist before both attempt to create it.
The evidence does NOT establish that duplicate records currently occur. The exact retry scope and HubSpot operation behavior are also not fully supplied.
Required test:
- Submit a lead.
- Force a timeout immediately after the CRM write commits.
- Allow the workflow retry.
- Verify whether one or multiple CRM records are created.
Also test two identical submissions concurrently.
Recommended fix:
Use an idempotency key or deterministic unique identifier and enforce uniqueness at the CRM/data layer where possible. Do not rely solely on a search-then-create sequence.
2. AI Classification Reliability
Status: UNKNOWN / POTENTIAL
Severity: CRITICAL UNKNOWN
The AI determines whether a lead is QUALIFIED or NOT QUALIFIED, which affects the downstream sales workflow.
The supplied evidence confirms that the response is checked for valid JSON and required fields, but this does not establish that the classification itself is correct.
No evaluation dataset, accuracy measurement, confidence threshold, ambiguity handling, or representative test results were supplied.
Required verification:
Test representative qualified, unqualified, ambiguous, incomplete, adversarial, and edge-case messages.
Measure classification accuracy and identify false-qualified and false-unqualified cases.
Do not treat syntactically valid JSON as evidence that the AI decision is correct.
3. Customer Input / Prompt Injection
Status: POTENTIAL
Severity: P1 — HIGH-IMPACT RISK
The customer's project description is supplied to an AI model.
Because this field is user-controlled, a malicious customer could attempt to manipulate the model's instructions or classification behavior.
The supplied evidence does not show the actual prompt or demonstrate whether prompt-injection defenses exist.
Required verification:
Test messages containing instructions such as attempts to override the classifier, alter the expected output, inject structured data, or manipulate the qualification result.
Review the actual system/developer prompt and enforce strict separation between instructions and untrusted customer content.
4. AI Output Validation
Status: OBSERVED + POTENTIAL
The workflow validates JSON syntax and required fields.
This is useful structural validation, but it does not prove semantic correctness.
For example, a response could contain valid JSON with an incorrect budget, incorrect project type, or incorrect QUALIFIED classification.
Recommended fix:
Add semantic validation for important fields, allowed-value validation for classifications, range/type checks where applicable, and explicit handling for ambiguous or low-confidence results.
5. Human Review Control
Status: OBSERVED
A human reviews qualified leads before the sales team contacts them.
This reduces the risk of an incorrect AI classification directly reaching the sales team.
However, the evidence does not establish whether the human review is technically enforced or whether another automated action occurs before review.
Verify that no consequential downstream sales action bypasses the review gate.
6. Critical Unknowns
The following information should be verified before declaring the workflow production-ready:
- Exact AI system/developer prompt
- AI model and configuration
- AI classification evaluation results
- Exact HubSpot permissions/scopes
- Exact retry behavior and which operations are retried
- Idempotency or duplicate-protection mechanism
- Behavior during timeout-after-commit
- Concurrent duplicate submission behavior
- Confirmation email template and data mapping
- Error-handling and recovery behavior
- Monitoring and alerting configuration
Recommended Priority
P0: None demonstrated from the supplied evidence.
P1: CRM retry/idempotency risk; untrusted customer input requires verification.
Critical Unknown: AI classification reliability and several production controls cannot currently be verified.
Final Recommendation
FIX BEFORE DEPLOYMENT
Do not treat the workflow as unsafe merely because evidence is missing. However, the current evidence is insufficient to establish reliable protection against duplicate CRM writes and incorrect AI-driven decisions.
Resolve the critical unknowns and run the recommended adversarial and failure-mode tests before client handoff.
Audit confidence: LOW–MEDIUM
Execution performed: NO
Connects securely to your tools. The creator never sees your data.
About this skill
AI Automation Pre-Deployment Risk Auditor helps AI automation builders, freelancers, agencies, and consultants find dangerous failure points before handing an automation to a client or deploying it to production. Give the auditor your workflow description, prompts, screenshots, workflow JSON, sample inputs/outputs, logs, test evidence, or other available evidence. It reconstructs the automation, maps trust boundaries, identifies consequential actions, evaluates control effectiveness, and searches for hidden failure modes.
It analyzes
- AI hallucination and unreliable decision-making
- Prompt injection and untrusted input
- API and integration failures
- Invalid or unsafe AI outputs
- Data mapping and integrity problems
- Duplicate actions and idempotency failures
- Retry amplification and timeout-after-commit risks
- Race conditions and concurrency problems
- Authentication and authorization weaknesses
- Sensitive data flow and privacy risks
- Business-logic failures
- Financial and other consequential actions
- Human-in-the-loop weaknesses
- Recovery and rollback gaps
- Monitoring and observability gaps
- Cost and resource risks
- Blast radius and reversibility
The auditor separates OBSERVED, INFERRED, POTENTIAL, and UNKNOWN conditions so it does not present assumptions as facts. It also distinguishes CRITICAL UNKNOWN conditions from demonstrated high-severity failures. Missing evidence is not automatically treated as proof that an automation is unsafe.
For serious findings, it provides
- Severity and business impact
- Evidence supporting the finding
- Failure mechanism
- Recommended remediation
- Adversarial test cases
- Verification requirements
- Priority order
The final audit produces a deployment-readiness decision such as:
Ready
Ready with monitoring
Fix before deployment
Do not deploy
Insufficient evidence
Important: This skill does not pretend to execute workflows, call APIs, inspect live credentials, or verify production behavior when those capabilities or evidence are not actually available. It clearly identifies what is known, what is inferred, and what still needs verification. Designed for automations built with tools such as n8n, Make, Zapier, AI agents, APIs, CRMs, databases, forms, email systems, and other connected business workflows. Use it before the client finds the bug for you.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.
Cannot execute live tests or penetrate systems. Accuracy depends on the quality of provided workflow exports and logs. Does not certify legal compliance.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
No special permissions declared or detected