automation-config

Name: automation-config
Availability: InStock
Author: mikeymiami

Standardize SMS automation drip configuration with timing and exit logic.

1|Updated Jun 7, 2026

Search Tags:#automation #templates #marketing #crm #sms #drip

Ready to run

npx skills add https://github.com/MikeyMiami/lovable-web-design --skill automation-config-mikeymiami

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automation-config
Source: https://github.com/MikeyMiami/lovable-web-design/tree/main/skills/automation-config
Command: npx skills add https://github.com/MikeyMiami/lovable-web-design --skill automation-config-mikeymiami

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inconsistency and manual overhead of managing client-specific SMS automation copy, timing, and exit rules across multiple website builds.

Core Features & Use Cases

Canonical Content Management: Provides a single source of truth for SMS drip templates, ensuring consistent branding and messaging across review requests, one-year follow-ups, and lead-form responses.
Logic & Flow Control: Defines precise timing, business-hour branching, and exit triggers (like opt-outs or form submissions) to ensure automated sequences behave predictably.
Use Case: When launching a new client site, use this skill to seed the database with the approved review-request and lead-form SMS sequences, ensuring all merge keys and timing offsets are correctly configured for the platform.

Quick Start

Use the automation-config skill to verify and seed the latest SMS template rows and sequence steps for a new client deployment.

Frequently Asked Questions about automation-config

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

FAQPage Schema

How do I standardize SMS drip copy and timing across multiple client deployments?▼

Standardizing SMS drip copy and timing requires a canonical configuration approach that defines template variables, timing offsets, and exit logic in a central source of truth before seeding client environments. This ensures consistent branding and predictable automated message sequences across all deployments.

What is SMS drip automation exit logic and how does it handle opt-outs?▼

SMS drip automation exit logic defines trigger conditions that halt automated message sequences, including user opt-outs, form submissions, or completed review requests. It ensures sequences behave predictably by stopping communication once the desired action is achieved or consent is legally withdrawn.

How do I configure business-hour constraints for automated marketing SMS sequences?▼

Configuring business-hour constraints for SMS sequences involves setting branching logic that delays message delivery outside specified operating hours. This timing offset configuration ensures client-facing communication respects business-hour boundaries and avoids sending off-hours automated messages.

Can I use dynamic template variables for review request and lead-form SMS responses?▼

Dynamic template variables can be used for review request and lead-form SMS responses by configuring merge keys within the SMS drip templates. This allows automated sequences to resolve client-specific data dynamically, ensuring personalized client-facing communication across diverse deployment environments.

Does this SMS automation approach support multi-step follow-up sequences like one-year reminders?▼

This SMS automation approach supports multi-step follow-up sequences including one-year reminders, review requests, and lead-form responses. It manages complex sequences by defining precise timing offsets and exit triggers for each step across diverse client deployment environments.

What's the best way to seed SMS template rows for a new client site launch?▼

Seeding SMS template rows for a new client site launch is best handled by using a canonical configuration skill to verify and populate approved review-request and lead-form sequences. This ensures all merge keys and timing offsets are correctly configured for the specific deployment platform.