Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From maccing-growth
Growth orchestrator — paid acquisition and owned-messaging strategy and execution
How this command is triggered — by the user, by Claude, or both
Slash command
/maccing-growth:growthThe summary Claude sees in its command listing — used to decide when to auto-load this command
Use the `growth` skill for this task: $ARGUMENTS If you are in a project repo, first read its growth state under `.maccing/growth/` (see the skill's Iron Laws), then route to the relevant platform skill: `google-ads`, `meta-ads`, `tiktok-ads`, or `whatsapp` (the latter two load the shared `meta` skill first; YCloud BSP ops live in `ycloud` / `ycloud-api`).
Use the growth skill for this task: $ARGUMENTS
If you are in a project repo, first read its growth state under .maccing/growth/ (see the skill's Iron Laws), then route to the relevant platform skill: google-ads, meta-ads, tiktok-ads, or whatsapp (the latter two load the shared meta skill first; YCloud BSP ops live in ycloud / ycloud-api).
npx claudepluginhub andredezzy/maccing --plugin maccing-growth