cm-growth-hacking

Name: cm-growth-hacking
Availability: InStock
Author: tody-agent

Unify booking, lead capture, promo, and survey workflows into a single engagement engine.

48|23|Updated Mar 17, 2026

Search Tags:#engagement #growth #calendar #tracking #trigger #bottom-sheet

Ready to run

npx skills add https://github.com/tody-agent/codymaster --skill cm-growth-hacking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cm-growth-hacking
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-growth-hacking
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-growth-hacking

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Centralizes and coordinates cross-skill engagement patterns into a single, cohesive system to eliminate fragmentation and inconsistent user experiences.

Core Features & Use Cases

Bottom Sheet Engine for UI engagement
Calendar CTAs and post-submit scheduling with tracking
Trigger management across scroll, time, exit, and interactions
Inherits and wires into existing skills (cm-booking-calendar, cm-ads-tracker, cm-google-form, cm-readit, cm-ux-master)
Works on static or dynamic sites and supports multi-industry engagement patterns

Quick Start

Deploy the engine by wiring the BottomSheetEngine with TriggerManager and the reference patterns, then mount it on a page to orchestrate engagement flows.

Frequently Asked Questions about cm-growth-hacking

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

FAQPage Schema

How do I unify booking, lead capture, and survey workflows into a single engagement system?▼

You can unify booking, lead capture, and survey workflows by deploying a cross-skill engagement orchestration engine that centralizes these patterns into a cohesive system, eliminating fragmented user experiences across static or dynamic sites.

What is the best way to manage scroll, time, and exit-intent triggers for bottom sheet UI?▼

Managing scroll, time, and exit-intent triggers for bottom sheet UI is best handled by an engine that unifies trigger management across multiple interaction types, generating template-driven bottom sheets within a cohesive engagement workflow.

Can I use a template-driven bottom sheet engine on both static and dynamic sites?▼

Yes, a template-driven bottom sheet engine works on both static and dynamic sites by scanning context and selecting engagement patterns, supporting multi-industry engagement workflows without requiring extensive custom integration.

How does calendar routing work for post-submit booking CTAs?▼

Calendar routing for post-submit booking CTAs works through device-aware scheduling that wires calendar calls-to-action directly into the engagement workflow, applying modular inheritance from existing booking skills to ensure production-grade integration.

What problem does cross-skill engagement orchestration solve for lead generation?▼

Cross-skill engagement orchestration solves the problem of fragmented and inconsistent user experiences by centralizing lead capture, promo, and survey workflows into a single reusable engine that coordinates engagement patterns cohesively.