automate-workflow

Automate workflow discovery, prototyping, and packaging into a reusable Claude skill.

Updated Feb 27, 2026

Search Tags:#automation #workflow #documentation #collaboration #prototyping #phase-driven

Ready to run

npx skills add https://github.com/glia-intelligence/plugins --skill automate-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automate-workflow
Source: https://github.com/glia-intelligence/plugins/tree/main/plugins/workflow-automation/skills/automate-workflow
Command: npx skills add https://github.com/glia-intelligence/plugins --skill automate-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams capture the end-to-end process of discovering, prototyping, and automating workflows using Claude Cowork. It guides users from initial discovery through connector setup, rapid prototyping, and final packaging into a reusable skill, reducing time-to-automation and preserving tribal knowledge.

Core Features & Use Cases

Interactive discovery and automation planning to surface automation opportunities.
Phase-driven workflow guidance (discovery, connector setup, prototyping, build) and living phase documents.
Artifact generation and living documentation (01-discovery.md, 02-connector-setup.md, 03a-automation-plan.md, 03-workflow-prototype.md) to carry context across phases.
Packaging the tested prototype into a self-contained skill (.skill) with verification criteria and crib notes for future sessions.

Quick Start

Describe the workflow to automate and let Claude guide you through discovery, prototyping, and packaging into a reusable skill.

Frequently Asked Questions about automate-workflow

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

FAQPage Schema

How do I automate a workflow end-to-end from discovery to deployment?▼

End-to-end workflow automation is achieved through phase-driven execution covering discovery, connector setup, prototyping, and final packaging. This process generates living phase documents and artifacts to carry context, ultimately packaging the tested prototype into a reusable skill.

How does phase-driven workflow guidance help preserve tribal knowledge during automation?▼

Phase-driven workflow guidance preserves tribal knowledge by generating living documentation like discovery and automation plan files. These artifacts log context across phases, ensuring process details are captured and accessible for future sessions rather than remaining undocumented.

Can I package a workflow prototype into a reusable skill without manual coding?▼

Yes, you can package a tested workflow prototype into a self-contained skill automatically. The packaging process includes verification criteria and crib notes, creating a reusable artifact that satisfies frontmatter-driven validation for immediate deployment.

What is the best way to document an automation workflow during prototyping?▼

The best way to document an automation workflow is through artifact generation during prototyping. This creates living documents such as discovery files, connector setup logs, and automation plans that maintain context and provide robust verification criteria across all phases.

Do I need specific connectors configured before starting workflow automation?▼

Workflow automation includes a dedicated connector setup phase before prototyping begins. You can start with interactive discovery to surface automation opportunities first, then configure necessary connectors as part of the guided phase-driven execution process.

Why does my workflow automation require living phase documents?▼

Workflow automation requires living phase documents to carry context seamlessly across execution phases. These artifacts ensure that discovery findings, connector configurations, and prototype designs are preserved, satisfying validation criteria and enabling accurate final skill packaging.