bundles/infrastructure/skills/workflow-automation/SKILL.md
This skill should be used when users need help designing content workflows, creating process documentation, implementing automation rules, designing approval processes, or optimizing content pipelines. It activates when users ask about workflow design, process documentation, automation, approval workflows, or content pipeline optimization.
npx skillsauth add shipshitdev/library workflow-automationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps design and implement content workflows, create process documentation, suggest automation rules, document approval processes, and optimize content pipelines for efficiency and quality.
This skill activates automatically when users:
To design effective content workflows:
Understand Current Process
Design Optimal Workflow
Document Workflow
Example User Request: "Design a content workflow for my team that includes approval steps"
Integration (discover from project):
To create comprehensive process documentation:
Document Content Processes
Create Visual Flowcharts
Maintain Documentation
Example User Request: "Create a flowchart for my content creation process"
Integration (discover from project):
To suggest and implement automation rules:
Identify Automation Opportunities
Design Automation Rules
Implement Automation
Example User Request: "What parts of my content workflow can be automated?"
Integration (discover from project):
To design content approval workflows:
Define Approval Requirements
Design Approval Workflow
Implement Approval System
Example User Request: "Design an approval workflow where content needs manager approval before publishing"
Integration (discover from project):
To optimize content pipelines for efficiency:
Analyze Current Pipeline
Optimize Pipeline
Monitor and Improve
Example User Request: "Help me optimize my content pipeline to reduce time from ideation to publishing"
Integration (discover from project):
Before designing workflows, discover the project's context:
Scan Project Documentation:
.agents/memory/ for workflow architecture and existing process documentationIdentify Workflow Components:
Common Content Workflow:
Trend Detection (Extension) → Content Generation (Creation Tools) →
Distribution (Publishing Platform) → Analytics (Analytics Platform) → Optimization
Workflow Components:
Automation Opportunities:
workflow-design-guide.md: Best practices for workflow designautomation-patterns.md: Common automation patterns and examplesapproval-workflow-examples.md: Approval workflow templates and examplesworkflow-template.md: Template for documenting workflowsprocess-flowchart-template.md: Template for creating process flowchartsautomation-rule-template.md: Template for defining automation rulesdevelopment
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.