ai-automation

Design AI agent workflows with worthiness checks, step contracts, guardrails, and audited build handoffs.

1|Updated Aug 7, 2026
One-click install
npx skills add https://github.com/Deepak-ai-93/deepak-skill --skill ai-automation-deepak-ai-93
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-automation
Source: https://github.com/Deepak-ai-93/deepak-skill/tree/main/skills/ai-automation
Command: npx skills add https://github.com/Deepak-ai-93/deepak-skill --skill ai-automation-deepak-ai-93

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Teams often build AI automations that should never have been automated, or ship agent workflows without human checkpoints, guardrails, or cost estimates. This Skill forces an honest automation-worthiness verdict first, then produces a complete workflow design document before any code is written. ## Core Features & Use Cases - Automation-worthiness gate: Records an automatable / not automatable verdict with cost-benefit reasoning, and stops honestly when the answer is NO. - Pattern-based workflow design: Selects the minimum-complexity agentic pattern (prompt chaining, routing, parallelization, orchestrator-workers, evaluator-optimizer) and defines trigger, per-step tool/input/output contracts, human checkpoints on irreversible actions, bounded execution limits, 4-layer guardrails, and cost estimates. - Audit harness: Runs audit-automation.mjs for automated checks plus a fresh automation-auditor subagent scoring /50 before anything ships. - Use Case: You spend 3 hours every Friday assembling a newsletter. The Skill verifies the job is worth automating, designs a collect → draft → human review → publish pipeline with checkpoints on the irreversible send step, estimates per-run cost, and hands the build to vibe-code-webapp and prompt-engineering. ## Quick Start Ask the AI to evaluate whether your weekly repetitive task is worth automating and design the agent workflow with human checkpoints and a cost estimate.

Frequently Asked Questions about ai-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide if a task is worth automating with AI?

Run the automation-worthiness check first: the task must be frequent (weekly or more), rule-following rather than judgment-heavy, and the hours saved must exceed setup plus run plus review cost. If it fails those tests, the honest verdict is not automatable and no design proceeds.

How to design an AI agent workflow before building it?

Define the trigger, then write each step as a contract: tool or agent, exact input, exact output, human checkpoint yes or no, error handling, and bounded execution limits. Select the minimum-complexity agentic pattern such as prompt chaining, routing, or evaluator-optimizer that fits the job structure.

Which agentic pattern should I use for my automation?

Use prompt chaining for fixed sequential steps, routing for distinct input types, parallelization for independent subtasks, orchestrator-workers for unpredictable subtasks, and evaluator-optimizer for iterative refinement. Reserve autonomous agents for open-ended problems, always with bounded execution.

When should an AI workflow require human approval?

Any step that sends, publishes, deletes, charges, or deploys must be marked human checkpoint yes, because those actions are irreversible. Judgment-heavy steps like tone or factual review also warrant checkpoints, and every yes-step must be listed with its reason.

What guardrails does an AI agent workflow need?

Document guardrails at four layers: user input validation, tool call restrictions like allowlists and rate limits, tool response schema validation, and final output filtering. Autonomous steps also need max iterations, max tokens, timeouts, and circuit breakers to prevent runaway execution.