<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow Automation on Top AI Skills</title><link>https://topaiskills.com/tags/workflow-automation/</link><description>Recent content in Workflow Automation on Top AI Skills</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 17 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://topaiskills.com/tags/workflow-automation/index.xml" rel="self" type="application/rss+xml"/><item><title>I Let AI Handle My Team's Approval Workflow for a Week — Here's What Happened</title><link>https://topaiskills.com/tutorials/guides/ai-approval-workflow-experiment/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/guides/ai-approval-workflow-experiment/</guid><description>&lt;p&gt;I handed my AI agent control over our team&amp;rsquo;s approval workflow for five days. Expense reports, leave requests, purchase orders — all processed through an AI skill. Here is what went right, what broke, and whether I would do it again.&lt;/p&gt;
&lt;h2 id="why-i-decided-to-try-this"&gt;Why I Decided to Try This&lt;/h2&gt;
&lt;p&gt;Our team runs on Lark. I manage a group of fifteen engineers, a couple of product managers, and a rotating cast of interns. Every week brings a steady stream of approval requests. Leave applications, hardware purchase requests, conference travel approvals, expense reports from team lunches — the kind of administrative overhead that is simple but constant.&lt;/p&gt;</description></item><item><title>Lark Approval - AI-Powered Approval Management for Feishu/Lark</title><link>https://topaiskills.com/skills/coding/lark-approval/</link><pubDate>Fri, 17 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/skills/coding/lark-approval/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;Lark Approval is an AI-powered skill for managing approval workflows inside Lark (Feishu). It lets your AI agent interact with approval requests directly — viewing pending approvals, checking approval details, taking action on requests, and tracking the full history of approval instances. Instead of switching to the Lark mobile app or web interface every time a pending approval notification pops up, you can handle it right from your terminal through your AI coding assistant.&lt;/p&gt;</description></item><item><title>AI Workflow Automation Skills Compared: Microsoft Foundry vs Azure AI vs Lark Tools</title><link>https://topaiskills.com/tutorials/comparison/ai-workflow-automation-skills-comparison/</link><pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate><guid>https://topaiskills.com/tutorials/comparison/ai-workflow-automation-skills-comparison/</guid><description>&lt;h2 id="the-short-version"&gt;The Short Version&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Install Microsoft Foundry if your team is all-in on Azure and you need to orchestrate multi-step AI workflows that touch Azure services. Install Azure AI if you want a general-purpose AI assistant that integrates with your codebase and Azure resources. Install Lark Doc if your team lives in Lark and needs AI-powered document workflows. Install Lark Base if you need AI-driven database management inside Lark.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;These four skills occupy different corners of the workflow automation space, but they share a common DNA: each lets you describe a process in natural language and have an AI agent execute it across one or more tools. The question is which ecosystem you&amp;rsquo;re already in and what kind of automation you need most.&lt;/p&gt;</description></item></channel></rss>