@monoes/monomindcli 2.15.3 → 2.15.4

package/org-skills/marketing-demand-acquisition/references/international-playbooks.md

@@ -0,0 +1,200 @@
+# International Market Playbooks
+
+Market-specific tactics for EU, US, and Canada expansion.
+
+---
+
+## Table of Contents
+
+- [EU Market Entry](#eu-market-entry)
+- [US Market Entry](#us-market-entry)
+- [Canada Market Entry](#canada-market-entry)
+- [Budget Allocation by Region](#budget-allocation-by-region)
+- [Localization Checklist](#localization-checklist)
+
+---
+
+## EU Market Entry
+
+### Compliance Requirements
+
+| Requirement | Implementation |
+|-------------|----------------|
+| GDPR consent | Double opt-in for email |
+| Cookie consent | Explicit consent banner |
+| Data storage | EU data center option |
+| Privacy policy | EU-specific language |
+
+**HubSpot Configuration:**
+- Enable double opt-in in Forms settings
+- Configure consent tracking properties
+- Set up GDPR deletion workflows
+
+### Localization Priority
+
+| Language | Market Priority | Revenue Potential |
+|----------|-----------------|-------------------|
+| German (DE) | High | Largest EU economy |
+| French (FR) | High | Second largest EU |
+| Spanish (ES) | Medium | Growing tech sector |
+| Dutch (NL) | Medium | English proficiency |
+| Italian (IT) | Lower | Later expansion |
+
+### Channel Mix (EU)
+
+| Channel | Budget % | Rationale |
+|---------|----------|-----------|
+| LinkedIn | 40% | Primary B2B channel |
+| Google Ads | 25% | High intent capture |
+| SEO | 20% | Long-term investment |
+| Partnerships | 15% | Local credibility |
+
+### EU Messaging Adjustments
+
+- More formal tone than US
+- Focus on data security and compliance
+- Emphasize local customer references
+- Include EU headquarters or presence
+- Display prices in EUR
+
+**Validation:** Test landing pages with EU VPN. Verify consent flows work correctly.
+
+---
+
+## US Market Entry
+
+### Market Characteristics
+
+| Aspect | US Approach |
+|--------|-------------|
+| Messaging | Direct, ROI-focused |
+| Tone | Less formal than EU |
+| Sales cycle | Faster decision-making |
+| Proof points | Dollar impact, not features |
+
+### Channel Mix (US)
+
+| Channel | Budget % | Rationale |
+|---------|----------|-----------|
+| Google Ads | 35% | High commercial intent |
+| LinkedIn | 30% | B2B targeting |
+| SEO | 20% | Competitive necessity |
+| Partnerships | 15% | Industry associations |
+
+### Partner Ecosystem
+
+| Partner Type | Examples |
+|--------------|----------|
+| Review sites | G2, Capterra, TrustRadius |
+| Industry associations | SaaStr, ProductLed |
+| Integration partners | Salesforce, HubSpot |
+| Channel partners | VARs, consultants |
+
+### Content Adjustments
+
+- Case studies with $ impact metrics
+- Faster, more aggressive CTAs
+- Video testimonials with customers
+- Comparison pages (vs. competitors)
+
+**Validation:** US-based speed test. Payment processing in USD functional.
+
+---
+
+## Canada Market Entry
+
+### Market Characteristics
+
+| Aspect | Canada Approach |
+|--------|-----------------|
+| Language | English + French (Quebec) |
+| Regulation | PIPEDA compliance |
+| Messaging | Mix of US and EU styles |
+| Pricing | CAD display preferred |
+
+### Regional Considerations
+
+| Region | Language | Focus |
+|--------|----------|-------|
+| Ontario | English | Tech hub, Toronto |
+| British Columbia | English | Vancouver tech scene |
+| Quebec | French | Requires localization |
+| Alberta | English | Energy sector |
+
+### Channel Mix (Canada)
+
+| Channel | Budget % | Rationale |
+|---------|----------|-----------|
+| Google Ads | 35% | Primary acquisition |
+| LinkedIn | 30% | Professional targeting |
+| SEO | 20% | Local content |
+| Partnerships | 15% | Local associations |
+
+**Validation:** French Quebec landing page tested. CAD pricing displays correctly.
+
+---
+
+## Budget Allocation by Region
+
+### Series A Recommended Split
+
+| Region | Budget % | Expected CAC |
+|--------|----------|--------------|
+| US | 50% | $150-300 |
+| EU | 35% | $200-400 |
+| Canada | 15% | $175-350 |
+
+### Channel by Region Matrix
+
+| Channel | US | EU | Canada |
+|---------|----|----|--------|
+| LinkedIn | 30% | 40% | 30% |
+| Google | 35% | 25% | 35% |
+| SEO | 20% | 20% | 20% |
+| Partners | 15% | 15% | 15% |
+
+### Scaling Criteria
+
+Expand regional budget when:
+- CAC < 80% of target for 4 consecutive weeks
+- MQL→SQL rate > regional benchmark
+- Sales team has regional capacity
+
+---
+
+## Localization Checklist
+
+### Website Localization
+
+- [ ] Translate navigation and UI elements
+- [ ] Localize pricing (currency, formatting)
+- [ ] Adapt case studies to regional references
+- [ ] Update screenshots with localized UI
+- [ ] Configure hreflang tags correctly
+- [ ] Submit to regional search consoles
+
+### Content Localization
+
+- [ ] Translate (don't just localize) key pages
+- [ ] Adapt idioms and cultural references
+- [ ] Update date formats (DD/MM/YYYY vs MM/DD/YYYY)
+- [ ] Adjust number formatting (1,000 vs 1.000)
+- [ ] Use regional spelling (optimise vs optimize)
+
+### Campaign Localization
+
+- [ ] Translate ad copy (not just translate, adapt)
+- [ ] Create regional landing pages
+- [ ] Set up regional tracking parameters
+- [ ] Configure regional lead routing
+- [ ] Align with regional sales hours
+
+### Legal Localization
+
+- [ ] GDPR compliance (EU)
+- [ ] PIPEDA compliance (Canada)
+- [ ] Cookie consent mechanisms
+- [ ] Privacy policy translations
+- [ ] Terms of service updates
+
+**Validation:** Native speaker review of all localized content before launch.

package/org-skills/marketing-loops/LICENSE.txt

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/org-skills/marketing-loops/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: marketing-loops
+description: "When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task."
+tags: ["marketing","operations"]
+tools: []
+license: MIT
+source: https://github.com/coreyhaines31/marketingskills
+source_path: "skills/marketing-loops"
+source_commit: 5b2c0007766c6a1cf1d53fd8fc73e979e0821022
+---
+# Marketing Loops
+
+You help set up **marketing loops** — repeatable marketing workflows an AI agent runs on a cadence, each with a defined trigger, a bounded set of steps, a self-check, and an explicit stopping condition. A loop turns a marketing task you'd otherwise do manually (and forget) into an always-on system: the weekly SEO opportunity scan, the ad-fatigue refresh, the churn-signal watch.
+
+This is the operational cousin of `marketing-ideas`. Ideas tell you *what to try once*. Loops tell you *what to keep doing on a schedule* — and wire the other marketing skills together to do it.
+
+## How to Use This Skill
+
+**Check for product marketing context first:** if `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md`), read it before asking questions. Use that context and only ask for what's missing.
+
+Then:
+1. **Clarify the job.** What outcome should this loop protect or grow? (rankings, ad efficiency, activation, retention, revenue, referrals)
+2. **Pick a loop** from the catalog in `references/loop-catalog.md` — or adapt the closest one.
+3. **Tune the cadence** to how fast the underlying signal actually changes (see the cadence rule below).
+4. **Confirm the human checkpoint.** Decide what the loop does autonomously vs. what it stages for human approval before publishing or spending — see `references/loop-guardrails.md`.
+5. **Schedule it** (see "Scheduling a loop" below).
+
+Building more than one loop, or a whole marketing operating system? See `references/loop-orchestration.md` for how loops compose and the order to adopt them (start with tracking + a weekly review; don't build 43 at once).
+
+## Anatomy of a Marketing Loop
+
+Every loop in the catalog has these nine parts. When you author or adapt one, fill all of them — a loop missing a stop condition, a self-check, or its state handling is a liability, not an asset.
+
+| Part | What it defines |
+|------|-----------------|
+| **Check cadence** | How often the loop *looks* (weekly / daily / on-trigger). Match it to signal speed. |
+| **Acts when** | The action condition — what must be true to actually *do* something, vs. just check and skip. Most runs of a good loop are "checked, nothing to do." |
+| **Purpose** | The one outcome this loop exists to move. |
+| **Skills used** | Which marketing skills the loop orchestrates each iteration. |
+| **Loop body** | The ordered steps run each iteration. |
+| **Self-check** | The verification done *before* acting — so the loop doesn't act on noise, seasonality, or a tracking bug. |
+| **State / idempotency** | What the loop remembers between runs: last-run marker, dedupe key, cooldown window, "already handled" set. Without this, loops double-act, re-nag the same people, or re-alert the same thing. Non-negotiable for anything scheduled — see `references/loop-state.md` for where state lives and the idempotency patterns. |
+| **Stop / bail-out** | When the loop skips, halts, escalates to a human, or disables itself — plus what it does on error. Every loop needs one, including heartbeat loops (their stop is "manual disable + error-halt," never "n/a"). |
+| **Output** | Where results go: a file, a PR, a staged draft, a notification, a report. |
+
+The **Check cadence / Acts when** split matters: a churn-signal loop might *check* daily but only *act* when an account crosses a risk threshold it hasn't been contacted about inside the cooldown window. Conflating the two produces loops that either miss the window or spam.
+
+## The cadence rule
+
+Match cadence to how fast the signal actually changes — not to how often you'd *like* an update.
+
+| Signal | Realistic cadence | Why |
+|--------|-------------------|-----|
+| Rankings, backlinks, domain authority | Weekly | Move slowly; daily checks are noise |
+| Ad creative fatigue, CPA drift | Every 2–3 days | Meta/Google feedback loops are days, not hours |
+| Activation / onboarding funnel | Weekly | Needs enough signups to be significant |
+| Churn signals | Daily or on-trigger | Early intervention window is short |
+| Content / copy decay | Monthly | Traffic erosion is gradual |
+| Competitor changes | Weekly | Pricing/positioning shifts are infrequent but matter |
+| Social listening / mentions | Daily | Engagement windows close fast |
+
+Over-frequent loops are the most common failure mode: they generate busywork, burn budget, and train you to ignore the output.
+
+## When NOT to loop
+
+Not everything should be automated on a cadence. Skip a loop — or add a mandatory human checkpoint — when:
+
+- **Strategy or creative direction is the real work.** Loops maintain and optimize; they don't set positioning, invent campaigns, or make brand calls.
+- **The action publishes or spends without review.** Auto-*drafting* an ad, email, or post is fine. Auto-*publishing* or auto-*shifting budget* needs a human checkpoint unless the user has explicitly authorized autonomous action and set guardrails (caps, allowlists).
+- **The signal is too sparse to be significant.** A weekly conversion-rate loop on 40 visitors/week is measuring noise.
+- **It's a vanity loop.** If nobody acts on the output, delete the loop. A loop that emails a dashboard nobody reads is worse than nothing.
+
+For any loop that sends, spends, publishes, or touches personal data, apply `references/loop-guardrails.md` — the two-tier action model (autonomous-safe vs. gated), spend/send caps, CAN-SPAM/GDPR/FTC/ToS rules, the always-escalate list, and a required kill switch.
+
+## Scheduling a loop
+
+These loops are agent-agnostic — the *body* works in any agent. The *scheduling* depends on your environment:
+
+- **Claude Code** — native options: `/loop` (self-paced, until a condition), `ScheduleWakeup` (dynamic pacing that reacts to state), and `CronCreate` (fixed cron schedule). If you have a loop-mechanics skill such as `loopify` installed, use it to choose between them and tune delays; otherwise the guidance below is enough.
+- **Any agent + cron** — wrap the loop body as a scheduled prompt/script (`0 9 * * 1` for Mondays 9am, etc.).
+- **Manual cadence** — for high-judgment loops, "run this skill every Monday" is a perfectly good loop. The value is the repeatable *body*, not the automation.
+
+Default to time-of-day cron for review-style loops (weekly review, ranking watch) and dynamic pacing for monitor-until-threshold loops (churn watch, launch-day tracking).
+
+## The Catalog
+
+`references/loop-catalog.md` holds the full library — 43 marketing loops with thorough funnel coverage: SEO & Content, Paid, Earned/Social/Partnerships, Activation, Retention, Revenue, Referral & Advocacy, and Ongoing Ops. Each is a complete, adaptable spec. Start there, pick the closest match, and tune it to the user's product, stage, and tooling.
+
+## Authoring a new loop
+
+When nothing in the catalog fits, author a new loop from `references/loop-template.md` — a copy-paste template with fill-in prompts, a worked before/after example, and a ship checklist. Fill all nine anatomy parts; if you can't answer the self-check, state/idempotency, and stop/bail-out concretely, the loop isn't ready to run.
+
+## Anti-patterns
+
+- Looping without a stop condition → runaway spend or infinite churn.
+- Same cadence for every loop → most run too often and get ignored.
+- No self-check → the loop acts on noise, seasonality, or a tracking bug.
+- No human checkpoint on spend/publish actions.
+- Building 10 loops at once → start with one, prove it earns its keep, then add the next.
+
+## Banned vocabulary
+
+Avoid: "set it and forget it," "fully autonomous marketing," "AI does everything," "10x on autopilot," "growth hacking machine." Loops are disciplined systems with checkpoints, not magic. Describe them honestly.
+
+## Related Skills
+
+- **marketing-ideas** — one-off tactics and inspiration (what to try). Loops operationalize the ones worth repeating.
+- **ab-testing** — the experimentation loop specifically (hypothesis → test → promote winner → repeat).
+- **analytics** — most loops read from analytics to decide whether to act.
+- Individual channel skills (`ads`, `seo-audit`, `emails`, `social`, `churn-prevention`, `pricing`, `referrals`) — the loop bodies orchestrate these.