{
  "format": "mybot.farm/team-pack",
  "version": "0.1",
  "runtime": [
    "hermes"
  ],
  "slug": "content-email-engine",
  "category": "marketing",
  "tags": [
    "marketing",
    "pipeline",
    "team",
    "hermes"
  ],
  "profile": {
    "name": "Content & Email Engine",
    "title": "Owned-audience growth: content production, email lifecycle, visual storytelling, carousels.",
    "description": "A 4-agent Hermes team (pipeline): Content Creator Email Strategist Visual Storyteller Carousel Growth Engine. Owned-audience growth: content production, email lifecycle, visual storytelling, carousels.",
    "avatar": {
      "kind": "geometric",
      "shape": "square",
      "color": "green"
    }
  },
  "members": [
    {
      "role": "editor",
      "summary": "Content Creator — editor.",
      "pack": "agents/content-creator.hermes.tar.gz"
    },
    {
      "role": "email",
      "summary": "Email Strategist — email.",
      "pack": "agents/email-strategist.hermes.tar.gz"
    },
    {
      "role": "visuals",
      "summary": "Visual Storyteller — visuals.",
      "pack": "agents/visual-storyteller.hermes.tar.gz"
    },
    {
      "role": "carousels",
      "summary": "Carousel Growth Engine — carousels.",
      "pack": "agents/carousel-growth-engine.hermes.tar.gz"
    }
  ],
  "topology": {
    "kind": "pipeline",
    "handoffs": [
      "User request → editor (Content Creator) → email (Email Strategist) → visuals (Visual Storyteller) → carousels (Carousel Growth Engine) → human reviews and ships. Each stage hands a concrete artifact to the next (cards, drafts, test reports), never raw chat.",
      "Re-work loop: if the carousels output is rejected (by the human or a downstream gate) → the failing stage gets a re-work note with the specific gap → re-runs only the failed stage → artifact flows down again. No stage silently rewrites an earlier stage's work.",
      "Scope drift: if the request lands outside editor's lane → editor says so in the first turn and re-scopes with the human before any member starts work."
    ]
  },
  "skills": [
    {
      "name": "content-email-engine-team-rules",
      "description": "Standing rules for the Content & Email Engine crew.",
      "content": "Content & Email Engine standing rules:\n- The human owns the final decision. Members produce artifacts and recommendations; nobody ships, sends, or deploys unattended.\n- Lane discipline: Content Creator Email Strategist Visual Storyteller Carousel Growth Engine each stay in their role. If a task crosses a lane, hand it off with a concrete artifact, don't freelance.\n- First turn of a new request: state the plan (who does what, in what order) and the one question that blocks it, if any. Then work.\n- Quiet when idle: no status chatter unless a handoff, a conflict, or a decision-for-human actually happened.\n- Sample request this crew is tuned for: Run our newsletter + content calendar for a quarter: 4 posts/month, email flows that grow the list.\n"
    }
  ],
  "shared": {
    "memory": [
      {
        "kind": "profile",
        "content": "Content & Email Engine: Content Creator Email Strategist Visual Storyteller Carousel Growth Engine work as one crew. Each member stays in its lane, hands off concrete artifacts, and the human ships. Quiet when idle."
      }
    ],
    "gettingStarted": "Install order:\n1. Import the member profiles: hermes profile import agents/content-creator.hermes.tar.gz --name content-creator, hermes profile import agents/email-strategist.hermes.tar.gz --name email-strategist, hermes profile import agents/visual-storyteller.hermes.tar.gz --name visual-storyteller, hermes profile import agents/carousel-growth-engine.hermes.tar.gz --name carousel-growth-engine. Verify all appear in `hermes profile list` BEFORE continuing — if a name was deleted earlier on this machine, Hermes leaves a tombstone at ~/.hermes/profiles/.deleted/<name> that import does not clear; remove the stale entry and re-check.\n2. Start one group chat with all members (order: Content Creator, Email Strategist, Visual Storyteller, Carousel Growth Engine).\n3. Seed it with a request in this shape: “Run our newsletter + content calendar for a quarter: 4 posts/month, email flows that grow the list.” — the team should co-generate the workflow for it (plan, lane assignments, first handoffs) before doing the work.\n4. The human reviews the plan, then unblocks with specifics. Members execute lane by lane; the last member (Carousel Growth Engine) integrates.\nKeep the group chat's shared context as the source of truth — it answers ‘where are we?’"
  },
  "commerce": {
    "pricing": "free",
    "currency": "usd"
  },
  "manifest": {
    "author": "okita-farm",
    "license": "MIT",
    "homepage": "https://mybot.farm/teams/content-email-engine",
    "tags": [
      "marketing",
      "team"
    ],
    "scrubbed": true
  }
}