{
  "schemaVersion": "1.0",
  "item": {
    "slug": "team-builder",
    "name": "Team Builder",
    "source": "tencent",
    "type": "skill",
    "category": "效率提升",
    "sourceUrl": "https://clawhub.ai/beyound87/team-builder",
    "canonicalUrl": "https://clawhub.ai/beyound87/team-builder",
    "targetPlatform": "OpenClaw"
  },
  "install": {
    "downloadMode": "redirect",
    "downloadUrl": "/downloads/team-builder",
    "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=team-builder",
    "sourcePlatform": "tencent",
    "targetPlatform": "OpenClaw",
    "installMethod": "Manual import",
    "extraction": "Extract archive",
    "prerequisites": [
      "OpenClaw"
    ],
    "packageFormat": "ZIP package",
    "includedAssets": [
      "references/agent-refs/chief-of-staff/dashboard-template.md",
      "references/agent-refs/chief-of-staff/strategy-methodology.md",
      "references/agent-refs/content-chief/methodology.md",
      "references/agent-refs/data-analyst/methodology.md",
      "references/agent-refs/fullstack-dev/coding-behavior-fallback.md",
      "references/agent-refs/fullstack-dev/deep-dive-protocol.md"
    ],
    "primaryDoc": "SKILL.md",
    "quickSetup": [
      "Download the package from Yavira.",
      "Extract the archive and review SKILL.md first.",
      "Import or place the package into your OpenClaw setup."
    ],
    "agentAssist": {
      "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
      "steps": [
        "Download the package from Yavira.",
        "Extract it into a folder your agent can access.",
        "Paste one of the prompts below and point your agent at the extracted folder."
      ],
      "prompts": [
        {
          "label": "New install",
          "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
        },
        {
          "label": "Upgrade existing",
          "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
        }
      ]
    },
    "sourceHealth": {
      "source": "tencent",
      "status": "healthy",
      "reason": "direct_download_ok",
      "recommendedAction": "download",
      "checkedAt": "2026-04-30T16:55:25.780Z",
      "expiresAt": "2026-05-07T16:55:25.780Z",
      "httpStatus": 200,
      "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
      "contentType": "application/zip",
      "probeMethod": "head",
      "details": {
        "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=network",
        "contentDisposition": "attachment; filename=\"network-1.0.0.zip\"",
        "redirectLocation": null,
        "bodySnippet": null
      },
      "scope": "source",
      "summary": "Source download looks usable.",
      "detail": "Yavira can redirect you to the upstream package for this source.",
      "primaryActionLabel": "Download for OpenClaw",
      "primaryActionHref": "/downloads/team-builder"
    },
    "validation": {
      "installChecklist": [
        "Use the Yavira download entry.",
        "Review SKILL.md after the package is downloaded.",
        "Confirm the extracted package contains the expected setup assets."
      ],
      "postInstallChecks": [
        "Confirm the extracted package includes the expected docs or setup files.",
        "Validate the skill or prompts are available in your target agent workspace.",
        "Capture any manual follow-up steps the agent could not complete."
      ]
    },
    "downloadPageUrl": "https://openagent3.xyz/downloads/team-builder",
    "agentPageUrl": "https://openagent3.xyz/skills/team-builder/agent",
    "manifestUrl": "https://openagent3.xyz/skills/team-builder/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/team-builder/agent.md"
  },
  "agentAssist": {
    "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.",
    "steps": [
      "Download the package from Yavira.",
      "Extract it into a folder your agent can access.",
      "Paste one of the prompts below and point your agent at the extracted folder."
    ],
    "prompts": [
      {
        "label": "New install",
        "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete."
      },
      {
        "label": "Upgrade existing",
        "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run."
      }
    ]
  },
  "documentation": {
    "source": "clawhub",
    "primaryDoc": "SKILL.md",
    "sections": [
      {
        "title": "Team Builder",
        "body": "Deploy a 7-agent SaaS growth team on OpenClaw in one shot."
      },
      {
        "title": "System Impact & Prerequisites",
        "body": "Read before running. This skill creates files and modifies system config."
      },
      {
        "title": "What it creates",
        "body": "A new workspace directory with ~40 files (agent configs, shared knowledge, inboxes, kanban)\napply-config.js -- script that modifies ~/.openclaw/openclaw.json (adds agents, bindings, agentToAgent config). Auto-backs up before writing.\ncreate-crons.ps1 / create-crons.sh -- scripts that create cron jobs via openclaw cron add\nAfter running these scripts you must restart the gateway (openclaw gateway restart)"
      },
      {
        "title": "What it does NOT do automatically",
        "body": "Does not modify openclaw.json directly -- you run apply-config.js yourself\nDoes not create cron jobs directly -- you run the cron script yourself\nDoes not restart the gateway -- you do that manually"
      },
      {
        "title": "Optional: Telegram",
        "body": "If you provide bot tokens during setup, apply-config.js will also add Telegram account configs and bindings\nRequires: Telegram bot tokens from @BotFather, your Telegram user ID\nRequires: network access to Telegram API (proxy configurable)"
      },
      {
        "title": "Optional: ACP / Claude Code",
        "body": "The fullstack-dev agent is configured to spawn Claude Code via ACP for complex coding tasks\nRequires: ACP-compatible coding agent configured in your OpenClaw environment\nNo extra setup needed if you don't use this feature"
      },
      {
        "title": "Credentials involved",
        "body": "Telegram bot tokens (optional) -- stored in openclaw.json, used for agent-to-Telegram binding\nModel API keys -- must already be configured in your OpenClaw model providers (not handled by this skill)"
      },
      {
        "title": "Recommended",
        "body": "Review generated apply-config.js before running\nCheck the backup of openclaw.json after running\nTest with 2-3 agents before enabling all cron jobs"
      },
      {
        "title": "Team Architecture",
        "body": "Default 7-agent SaaS growth team (customizable to 2-10 agents):\n\nCEO\n |-- Chief of Staff (dispatch + strategy + efficiency)\n |-- Data Analyst (data + user research)\n |-- Growth Lead (GEO + SEO + community + social media)\n |-- Content Chief (strategy + writing + copywriting + i18n)\n |-- Intel Analyst (competitor monitoring + market trends)\n |-- Product Lead (product management + tech architecture)\n |-- Fullstack Dev (full-stack dev + ops, spawns Claude Code with role-based prompts)"
      },
      {
        "title": "Multi-Team Support",
        "body": "One OpenClaw instance can run multiple teams:\n\nnode <skill-dir>/scripts/deploy.js                  # default team\nnode <skill-dir>/scripts/deploy.js --team alpha      # named team \"alpha\"\nnode <skill-dir>/scripts/deploy.js --team beta       # named team \"beta\"\n\nNamed teams use prefixed agent IDs (alpha-chief-of-staff, beta-growth-lead) to avoid conflicts. Each team gets its own workspace subdirectory."
      },
      {
        "title": "Flexible Team Size",
        "body": "The wizard lets you select 2-10 agents from the available roles. Skip roles you don't need. The 7-agent default covers most SaaS scenarios, but you can run leaner (3-4 agents) or expand with custom roles."
      },
      {
        "title": "Model Auto-Detection",
        "body": "The wizard scans your openclaw.json for registered model providers and auto-suggests models by role type:\n\nRole TypeBest ForAuto-detect PatternThinkingStrategic roles (chief, growth, content, product)/glm-5|opus|o1|deepthink/iExecutionOperational roles (data, intel, fullstack)/glm-4|sonnet|gpt-4/iFastLightweight tasks/flash|haiku|mini/i\n\nYou can always override with manual model IDs."
      },
      {
        "title": "Step 1: Collect Configuration",
        "body": "Ask the user for these inputs (use defaults if not provided):\n\nParameterDefaultDescriptionTeam nameAlpha TeamUsed in all docs and configsWorkspace dir~/.openclaw/workspace-teamShared workspace rootTimezoneAsia/ShanghaiFor cron schedulesMorning brief hour8Chief's morning reportEvening brief hour18Chief's evening reportThinking modelzai/glm-5For strategic rolesExecution modelzai/glm-4.7For execution rolesCEO titleBossHow agents address the CEO\n\nOptional: Telegram user ID, proxy, and 7 bot tokens."
      },
      {
        "title": "Step 2: Run Deploy Script",
        "body": "node <skill-dir>/scripts/deploy.js\n\nInteractive -- asks all questions from Step 1, generates the full workspace."
      },
      {
        "title": "Step 3: Apply Config",
        "body": "node <workspace-dir>/apply-config.js\n\nAdds agents to openclaw.json, preserving existing config."
      },
      {
        "title": "Step 4: Create Cron Jobs",
        "body": "# Windows\npowershell <workspace-dir>/create-crons.ps1\n\n# Linux/Mac\nbash <workspace-dir>/create-crons.sh"
      },
      {
        "title": "Step 5: Restart Gateway",
        "body": "openclaw gateway restart"
      },
      {
        "title": "Step 6: Fill Business Info",
        "body": "User must edit:\n\nshared/decisions/active.md -- strategy, priorities\nshared/products/_index.md -- products overview (≤5 lines per product: URL, code path, positioning, tech, status). Detailed info goes in each product's overview.md.\nshared/knowledge/competitor-map.md -- competitor analysis\nshared/knowledge/tech-standards.md -- coding standards"
      },
      {
        "title": "Step 7: Trigger Deep Dive Scans",
        "body": "After filling in products with code directories, tell product-lead to trigger Deep Dive scans:\n\nProduct-lead sends scan requests to fullstack-dev via inbox\nFullstack-dev enters each project directory and generates knowledge files\nProduct-lead reviews the generated files for completeness\nAll agents now have deep project understanding for informed decisions"
      },
      {
        "title": "Cron Schedule",
        "body": "OffsetAgentTaskFrequencyH-1Data AnalystData + user feedbackDailyH-1Intel AnalystCompetitor scanMon/Wed/FriHChief of StaffMorning brief (announced)DailyH+1Growth LeadGEO + SEO + communityDailyH+1Content ChiefWeekly content planMondayH+10Chief of StaffEvening brief (announced)Daily\n\n(H = morning brief hour)"
      },
      {
        "title": "Generated File Structure",
        "body": "<workspace>/\n├── AGENTS.md, SOUL.md, USER.md  (auto-injected)\n├── apply-config.js, create-crons.ps1/.sh, README.md\n├── agents/<7 agent dirs>/       (SOUL.md + MEMORY.md + memory/)\n└── shared/\n    ├── briefings/, decisions/, inbox/ (v2: with status tracking)\n    ├── status/team-dashboard.md     (chief-of-staff maintains, all agents read first)\n    ├── data/                        (public data pool, data-analyst writes, all read)\n    ├── kanban/, knowledge/\n    └── products/\n        ├── _index.md                (product matrix overview)\n        ├── _template/               (knowledge directory template)\n        └── {product}/               (per-product knowledge, up to 20 files)\n            ├── overview.md, architecture.md, database.md, api.md, routes.md\n            ├── models.md, services.md, frontend.md, auth.md, integrations.md\n            ├── jobs-events.md, config-env.md, dependencies.md, devops.md\n            ├── test-coverage.md, tech-debt.md, domain-flows.md, data-flow.md\n            ├── i18n.md, changelog.md, notes.md"
      },
      {
        "title": "Knowledge Governance",
        "body": "Each shared knowledge file has a designated owner. Only the owner agent updates it; others read only.\n\nFileOwnerUpdate Triggergeo-playbook.mdgrowth-leadAfter GEO experiments/discoveriesseo-playbook.mdgrowth-leadAfter SEO experimentscompetitor-map.mdintel-analystAfter each competitor scancontent-guidelines.mdcontent-chiefAfter proven writing patternsuser-personas.mddata-analystAfter new user insightstech-standards.mdproduct-leadAfter architecture decisions"
      },
      {
        "title": "Update Protocol",
        "body": "When updating a knowledge file, the owner must:\n\nAdd a dated entry at the top: ## [YYYY-MM-DD] <what changed>\nInclude the reason and data evidence\nNever delete existing entries without CEO approval (append, don't replace)"
      },
      {
        "title": "Chief of Staff Governance",
        "body": "The chief-of-staff monitors knowledge file health during weekly reviews:\n\nAre files being updated regularly?\nAny conflicting information between files?\nAny stale entries that should be archived?"
      },
      {
        "title": "Self-Evolution Pattern",
        "body": "Agents improve their own strategies over time through a feedback loop:\n\n1. Execute task (cron or inbox triggered)\n2. Collect results (data, metrics, outcomes)\n3. Analyze: what worked vs what didn't\n4. Update knowledge files with proven strategies (with evidence)\n5. Next execution reads updated knowledge → better performance\n\nThis is NOT the agent randomly changing rules. Updates must be:\n\nData-driven: backed by metrics or concrete outcomes\nIncremental: append new findings, don't rewrite everything\nTraceable: dated with evidence so others can verify"
      },
      {
        "title": "What Agents Can Self-Update",
        "body": "Their own knowledge files (per ownership table above)\nTheir own MEMORY.md (lessons learned, decisions)\nshared/data/ outputs (data-analyst only)"
      },
      {
        "title": "What Requires CEO Approval",
        "body": "shared/decisions/active.md (strategy changes)\nAdding/removing agents or changing team architecture\nExternal publishing or spending decisions"
      },
      {
        "title": "Public Data Layer",
        "body": "The shared/data/ directory serves as a read-only data pool for all agents:\n\ndata-analyst writes: daily metrics, user feedback summaries, anomaly alerts\nAll agents read: to inform their own decisions\nFormat: structured markdown or JSON, dated filenames (e.g., metrics-2026-03-01.md)\nRetention: keep 30 days, archive older files"
      },
      {
        "title": "Project Deep Dive — Code Scanning",
        "body": "Agents can deeply understand each SaaS product through automated code scanning. This is critical — without deep project knowledge, all team decisions are surface-level."
      },
      {
        "title": "How It Works",
        "body": "CEO adds a product to shared/products/_index.md (name, URL, code directory, tech stack)\nProduct Lead triggers a Deep Dive scan by messaging Fullstack Dev via inbox\nFullstack Dev enters the project directory (read-only) and scans the codebase\nKnowledge files are generated in shared/products/{product}/\nAll agents consume these files via manifest-based lazy loading (never read all at once)"
      },
      {
        "title": "Manifest-Based Lazy Loading (MANDATORY)",
        "body": "Each product directory includes a manifest.json (~200 tokens) that lists all files with one-line summaries and a taskFileMap mapping task types to relevant files.\n\nAgent workflow:\n\nRead _index.md → identify which product\nRead {product}/manifest.json → see all files + summaries (~200 tokens)\nBased on taskFileMap or summaries, read only 1-3 relevant files\nNever read more than 5 product files per session\n\nWhy: With 15+ products × 20 files each, full loading = 40K+ tokens per product. Manifest loading = 200 tokens + only what's needed.\n\nFullstack Dev MUST regenerate manifest.json after every scan (L0-L4). Template in _template/manifest.json."
      },
      {
        "title": "Manifest Quality Standards",
        "body": "摘要不能为了省 token 丢掉关键信息。每条摘要须满足：\n\n核心文件（database/models/services/routes/integrations）：50-130字，列出关键实体名/数量/域名\n中等文件（auth/frontend/commands/config）：30-80字，点明方案和范围\n轻量文件（changelog/notes/metrics）：可以短（<20字）\ntaskFileMap：必须覆盖该产品的所有核心业务场景（不少于8个映射）\ncodeStats：必须包含文件数、行数、模型数、表数等量化指标"
      },
      {
        "title": "Product Knowledge Directory",
        "body": "Each product gets a knowledge directory with up to 20 files + manifest:\n\nshared/products/{product}/\n├── manifest.json        ← **INDEX** (~200 tokens): file list, summaries, taskFileMap\n├── overview.md          ← Product positioning (from _index.md)\n├── architecture.md      ← System architecture, tech stack, design patterns, layering\n├── database.md          ← Full table schema, relationships, indexes, migrations\n├── api.md               ← API endpoints, params, auth, versioning\n├── routes.md            ← Complete route table (Web + API + Console)\n├── models.md            ← ORM relationships, scopes, accessors, observers\n├── services.md          ← Business logic, state machines, workflows, validation\n├── frontend.md          ← Component tree, page routing, state management\n├── auth.md              ← Auth scheme, roles/permissions matrix, OAuth\n├── integrations.md      ← Third-party: payment/email/SMS/storage/CDN/analytics\n├── jobs-events.md       ← Queue jobs, event listeners, scheduled tasks, notifications\n├── config-env.md        ← Environment variables, feature flags, cache strategy\n├── dependencies.md      ← Key dependencies, custom packages, vulnerabilities\n├── devops.md            ← Deployment, CI/CD, Docker, monitoring, logging\n├── test-coverage.md     ← Test strategy, coverage, weak spots\n├── tech-debt.md         ← TODO/FIXME/HACK inventory, dead code, complexity hotspots\n├── domain-flows.md      ← Core user journeys, domain boundaries, module coupling\n├── data-flow.md         ← Data lifecycle: external → import → process → store → output\n├── i18n.md              ← Internationalization, language coverage\n├── changelog.md         ← Scan diff log (what changed between scans)\n└── notes.md             ← Agent discoveries, gotchas, implicit rules"
      },
      {
        "title": "Scan Levels",
        "body": "LevelScopeWhenOutputL0 SnapshotSurface: directory tree, packages, envFirst onboardarchitecture, dependencies, config-envL1 SkeletonStructure: DB, routes, models, componentsFirst onboarddatabase, routes, api, models, frontendL2 Deep DiveLogic: services, auth, jobs, integrationsOn-demand per moduleservices, auth, jobs-events, integrations, domain-flows, data-flowL3 Health CheckQuality: tech debt, tests, securityPeriodic / pre-releasetech-debt, test-coverage, devopsL4 IncrementalDelta: git diff → update affected filesAfter code changeschangelog + targeted updates"
      },
      {
        "title": "Content Standards",
        "body": "Knowledge files capture not just WHAT exists but WHY:\n\nDesign decisions: Why this approach was chosen\nImplicit business rules: Logic buried in code (e.g., \"orders auto-cancel after 72h\")\nGotchas: What breaks if you touch this module carelessly\nCross-module coupling: Where changing A silently breaks B\nPerformance hotspots: N+1 queries, missing indexes, bottleneck endpoints"
      },
      {
        "title": "Role Responsibilities",
        "body": "RoleResponsibilityProduct LeadGovernance: trigger scans, review quality, track freshness, ensure completenessFullstack DevExecution: enter code directory, scan, generate/update knowledge filesAll AgentsConsumption: read product knowledge before any product-related decision"
      },
      {
        "title": "Per-Stack Auto-Detection",
        "body": "Fullstack Dev auto-detects tech stack and applies stack-specific scan strategies:\n\nLaravel/PHP: migrations, route:list, Models, Services, Middleware, Policies, Jobs, Console/Kernel\nReact/Vue: components, router, stores, API client, i18n\nPython/Django/FastAPI: models.py, urls.py, views.py, middleware, celery\nGeneral: tree, git log, grep TODO/FIXME, .env.example, Docker, CI, tests"
      },
      {
        "title": "Inbox Protocol v2 (status tracking)",
        "body": "Every inbox message now has a status field:\n\npending → received → in-progress → done (or blocked)\nChief-of-staff monitors timeouts: high>4h, normal>24h pending = intervention\nBlocked >8h = escalation to CEO\nRecipients MUST update status immediately upon reading"
      },
      {
        "title": "Team Dashboard (shared/status/team-dashboard.md)",
        "body": "Chief-of-staff maintains a \"live scoreboard\" updated every session:\n\n🔴 Urgent/Blocked items\n📊 Per-agent status table (last active, current task, status icon)\n📬 Unprocessed inbox summary (pending/blocked messages across all inboxes)\n🔗 Cross-agent task chain tracking (A→B→C with per-step status)\n📅 Today/Tomorrow focus\n\nAll agents read this file first when waking up. 5-second situational awareness."
      },
      {
        "title": "Chief-of-Staff as Router",
        "body": "The chief is upgraded from \"briefing writer\" to \"active team router\":\n\nBlocker detection: scans all inboxes for overdue messages\nActive dispatch: writes reminders directly to lagging agents' inboxes\nTask chain tracking: identifies multi-agent workflows and tracks each step\nEscalation: persistent blockers get flagged to CEO\nRuns 4x/day (morning brief, midday patrol, afternoon patrol, evening brief)"
      },
      {
        "title": "Cron Schedule (10 jobs, up from 7)",
        "body": "TimeAgentTypePurpose07:00data-analystdailyData pull + feedback scan08:00chief-of-staffannounceMorning: router scan + brief + quality09:00growth-leaddailyGEO/SEO/community09:00product-leaddaily (NEW)Inbox + knowledge governance + task delegation10:00content-chiefdaily M-F (was weekly)Content creation + collaboration10:00fullstack-devdaily (enhanced)Inbox + Deep Dive + dev tasks + patrol12:00chief-of-staffpatrol (NEW)Router scan only, no brief15:00chief-of-staffpatrol (NEW)Router scan only, no brief18:00chief-of-staffannounceEvening: router scan + summary + next day plan07:00 M/W/Fintel-analyst3x/weekCompetitor scan"
      },
      {
        "title": "Why These Changes Matter",
        "body": "BeforeAfterImpactInbox = blind dropInbox with status trackingMessages are acknowledged and trackableChief 2x/dayChief 4x/day with router roleBlockers caught within hours, not daysContent-chief 1x/weekDaily M-FActually produces contentProduct-lead no cronDailyKnowledge governance happensNo team dashboardDashboard every sessionAll agents know the full pictureNo timeout detectionAutomatic timeout rulesNothing falls through cracks"
      },
      {
        "title": "Key Design Decisions",
        "body": "Shared workspace so qmd indexes everything for all agents\nInbox Protocol v2 with status tracking and timeout rules for reliable async communication\nChief as Router — not just a briefing writer but active coordinator who detects and resolves blockers\nTeam Dashboard — single source of truth for team-wide status, maintained by chief every session\nGEO as #1 priority (AI search = blue ocean)\nFullstack Dev spawns Claude Code via ACP for complex tasks\nProject Deep Dive gives all agents deep codebase understanding, not just surface-level product overviews"
      },
      {
        "title": "Customization",
        "body": "Edit ROLES array in scripts/deploy.js to add/remove agents.\nEdit references/soul-templates.md for SOUL.md templates.\nEdit references/shared-templates.md for shared file templates."
      }
    ],
    "body": "Team Builder\n\nDeploy a 7-agent SaaS growth team on OpenClaw in one shot.\n\nSystem Impact & Prerequisites\n\nRead before running. This skill creates files and modifies system config.\n\nWhat it creates\nA new workspace directory with ~40 files (agent configs, shared knowledge, inboxes, kanban)\napply-config.js -- script that modifies ~/.openclaw/openclaw.json (adds agents, bindings, agentToAgent config). Auto-backs up before writing.\ncreate-crons.ps1 / create-crons.sh -- scripts that create cron jobs via openclaw cron add\nAfter running these scripts you must restart the gateway (openclaw gateway restart)\nWhat it does NOT do automatically\nDoes not modify openclaw.json directly -- you run apply-config.js yourself\nDoes not create cron jobs directly -- you run the cron script yourself\nDoes not restart the gateway -- you do that manually\nOptional: Telegram\nIf you provide bot tokens during setup, apply-config.js will also add Telegram account configs and bindings\nRequires: Telegram bot tokens from @BotFather, your Telegram user ID\nRequires: network access to Telegram API (proxy configurable)\nOptional: ACP / Claude Code\nThe fullstack-dev agent is configured to spawn Claude Code via ACP for complex coding tasks\nRequires: ACP-compatible coding agent configured in your OpenClaw environment\nNo extra setup needed if you don't use this feature\nCredentials involved\nTelegram bot tokens (optional) -- stored in openclaw.json, used for agent-to-Telegram binding\nModel API keys -- must already be configured in your OpenClaw model providers (not handled by this skill)\nRecommended\nReview generated apply-config.js before running\nCheck the backup of openclaw.json after running\nTest with 2-3 agents before enabling all cron jobs\nTeam Architecture\n\nDefault 7-agent SaaS growth team (customizable to 2-10 agents):\n\nCEO\n |-- Chief of Staff (dispatch + strategy + efficiency)\n |-- Data Analyst (data + user research)\n |-- Growth Lead (GEO + SEO + community + social media)\n |-- Content Chief (strategy + writing + copywriting + i18n)\n |-- Intel Analyst (competitor monitoring + market trends)\n |-- Product Lead (product management + tech architecture)\n |-- Fullstack Dev (full-stack dev + ops, spawns Claude Code with role-based prompts)\n\nMulti-Team Support\n\nOne OpenClaw instance can run multiple teams:\n\nnode <skill-dir>/scripts/deploy.js                  # default team\nnode <skill-dir>/scripts/deploy.js --team alpha      # named team \"alpha\"\nnode <skill-dir>/scripts/deploy.js --team beta       # named team \"beta\"\n\n\nNamed teams use prefixed agent IDs (alpha-chief-of-staff, beta-growth-lead) to avoid conflicts. Each team gets its own workspace subdirectory.\n\nFlexible Team Size\n\nThe wizard lets you select 2-10 agents from the available roles. Skip roles you don't need. The 7-agent default covers most SaaS scenarios, but you can run leaner (3-4 agents) or expand with custom roles.\n\nModel Auto-Detection\n\nThe wizard scans your openclaw.json for registered model providers and auto-suggests models by role type:\n\nRole Type\tBest For\tAuto-detect Pattern\nThinking\tStrategic roles (chief, growth, content, product)\t/glm-5|opus|o1|deepthink/i\nExecution\tOperational roles (data, intel, fullstack)\t/glm-4|sonnet|gpt-4/i\nFast\tLightweight tasks\t/flash|haiku|mini/i\n\nYou can always override with manual model IDs.\n\nDeployment Flow\nStep 1: Collect Configuration\n\nAsk the user for these inputs (use defaults if not provided):\n\nParameter\tDefault\tDescription\nTeam name\tAlpha Team\tUsed in all docs and configs\nWorkspace dir\t~/.openclaw/workspace-team\tShared workspace root\nTimezone\tAsia/Shanghai\tFor cron schedules\nMorning brief hour\t8\tChief's morning report\nEvening brief hour\t18\tChief's evening report\nThinking model\tzai/glm-5\tFor strategic roles\nExecution model\tzai/glm-4.7\tFor execution roles\nCEO title\tBoss\tHow agents address the CEO\n\nOptional: Telegram user ID, proxy, and 7 bot tokens.\n\nStep 2: Run Deploy Script\nnode <skill-dir>/scripts/deploy.js\n\n\nInteractive -- asks all questions from Step 1, generates the full workspace.\n\nStep 3: Apply Config\nnode <workspace-dir>/apply-config.js\n\n\nAdds agents to openclaw.json, preserving existing config.\n\nStep 4: Create Cron Jobs\n# Windows\npowershell <workspace-dir>/create-crons.ps1\n\n# Linux/Mac\nbash <workspace-dir>/create-crons.sh\n\nStep 5: Restart Gateway\nopenclaw gateway restart\n\nStep 6: Fill Business Info\n\nUser must edit:\n\nshared/decisions/active.md -- strategy, priorities\nshared/products/_index.md -- products overview (≤5 lines per product: URL, code path, positioning, tech, status). Detailed info goes in each product's overview.md.\nshared/knowledge/competitor-map.md -- competitor analysis\nshared/knowledge/tech-standards.md -- coding standards\nStep 7: Trigger Deep Dive Scans\n\nAfter filling in products with code directories, tell product-lead to trigger Deep Dive scans:\n\nProduct-lead sends scan requests to fullstack-dev via inbox\nFullstack-dev enters each project directory and generates knowledge files\nProduct-lead reviews the generated files for completeness\nAll agents now have deep project understanding for informed decisions\nCron Schedule\nOffset\tAgent\tTask\tFrequency\nH-1\tData Analyst\tData + user feedback\tDaily\nH-1\tIntel Analyst\tCompetitor scan\tMon/Wed/Fri\nH\tChief of Staff\tMorning brief (announced)\tDaily\nH+1\tGrowth Lead\tGEO + SEO + community\tDaily\nH+1\tContent Chief\tWeekly content plan\tMonday\nH+10\tChief of Staff\tEvening brief (announced)\tDaily\n\n(H = morning brief hour)\n\nGenerated File Structure\n<workspace>/\n├── AGENTS.md, SOUL.md, USER.md  (auto-injected)\n├── apply-config.js, create-crons.ps1/.sh, README.md\n├── agents/<7 agent dirs>/       (SOUL.md + MEMORY.md + memory/)\n└── shared/\n    ├── briefings/, decisions/, inbox/ (v2: with status tracking)\n    ├── status/team-dashboard.md     (chief-of-staff maintains, all agents read first)\n    ├── data/                        (public data pool, data-analyst writes, all read)\n    ├── kanban/, knowledge/\n    └── products/\n        ├── _index.md                (product matrix overview)\n        ├── _template/               (knowledge directory template)\n        └── {product}/               (per-product knowledge, up to 20 files)\n            ├── overview.md, architecture.md, database.md, api.md, routes.md\n            ├── models.md, services.md, frontend.md, auth.md, integrations.md\n            ├── jobs-events.md, config-env.md, dependencies.md, devops.md\n            ├── test-coverage.md, tech-debt.md, domain-flows.md, data-flow.md\n            ├── i18n.md, changelog.md, notes.md\n\nKnowledge Governance\n\nEach shared knowledge file has a designated owner. Only the owner agent updates it; others read only.\n\nFile\tOwner\tUpdate Trigger\ngeo-playbook.md\tgrowth-lead\tAfter GEO experiments/discoveries\nseo-playbook.md\tgrowth-lead\tAfter SEO experiments\ncompetitor-map.md\tintel-analyst\tAfter each competitor scan\ncontent-guidelines.md\tcontent-chief\tAfter proven writing patterns\nuser-personas.md\tdata-analyst\tAfter new user insights\ntech-standards.md\tproduct-lead\tAfter architecture decisions\nUpdate Protocol\n\nWhen updating a knowledge file, the owner must:\n\nAdd a dated entry at the top: ## [YYYY-MM-DD] <what changed>\nInclude the reason and data evidence\nNever delete existing entries without CEO approval (append, don't replace)\nChief of Staff Governance\n\nThe chief-of-staff monitors knowledge file health during weekly reviews:\n\nAre files being updated regularly?\nAny conflicting information between files?\nAny stale entries that should be archived?\nSelf-Evolution Pattern\n\nAgents improve their own strategies over time through a feedback loop:\n\n1. Execute task (cron or inbox triggered)\n2. Collect results (data, metrics, outcomes)\n3. Analyze: what worked vs what didn't\n4. Update knowledge files with proven strategies (with evidence)\n5. Next execution reads updated knowledge → better performance\n\n\nThis is NOT the agent randomly changing rules. Updates must be:\n\nData-driven: backed by metrics or concrete outcomes\nIncremental: append new findings, don't rewrite everything\nTraceable: dated with evidence so others can verify\nWhat Agents Can Self-Update\nTheir own knowledge files (per ownership table above)\nTheir own MEMORY.md (lessons learned, decisions)\nshared/data/ outputs (data-analyst only)\nWhat Requires CEO Approval\nshared/decisions/active.md (strategy changes)\nAdding/removing agents or changing team architecture\nExternal publishing or spending decisions\nPublic Data Layer\n\nThe shared/data/ directory serves as a read-only data pool for all agents:\n\ndata-analyst writes: daily metrics, user feedback summaries, anomaly alerts\nAll agents read: to inform their own decisions\nFormat: structured markdown or JSON, dated filenames (e.g., metrics-2026-03-01.md)\nRetention: keep 30 days, archive older files\nProject Deep Dive — Code Scanning\n\nAgents can deeply understand each SaaS product through automated code scanning. This is critical — without deep project knowledge, all team decisions are surface-level.\n\nHow It Works\nCEO adds a product to shared/products/_index.md (name, URL, code directory, tech stack)\nProduct Lead triggers a Deep Dive scan by messaging Fullstack Dev via inbox\nFullstack Dev enters the project directory (read-only) and scans the codebase\nKnowledge files are generated in shared/products/{product}/\nAll agents consume these files via manifest-based lazy loading (never read all at once)\nManifest-Based Lazy Loading (MANDATORY)\n\nEach product directory includes a manifest.json (~200 tokens) that lists all files with one-line summaries and a taskFileMap mapping task types to relevant files.\n\nAgent workflow:\n\nRead _index.md → identify which product\nRead {product}/manifest.json → see all files + summaries (~200 tokens)\nBased on taskFileMap or summaries, read only 1-3 relevant files\nNever read more than 5 product files per session\n\nWhy: With 15+ products × 20 files each, full loading = 40K+ tokens per product. Manifest loading = 200 tokens + only what's needed.\n\nFullstack Dev MUST regenerate manifest.json after every scan (L0-L4). Template in _template/manifest.json.\n\nManifest Quality Standards\n\n摘要不能为了省 token 丢掉关键信息。每条摘要须满足：\n\n核心文件（database/models/services/routes/integrations）：50-130字，列出关键实体名/数量/域名\n中等文件（auth/frontend/commands/config）：30-80字，点明方案和范围\n轻量文件（changelog/notes/metrics）：可以短（<20字）\ntaskFileMap：必须覆盖该产品的所有核心业务场景（不少于8个映射）\ncodeStats：必须包含文件数、行数、模型数、表数等量化指标\nProduct Knowledge Directory\n\nEach product gets a knowledge directory with up to 20 files + manifest:\n\nshared/products/{product}/\n├── manifest.json        ← **INDEX** (~200 tokens): file list, summaries, taskFileMap\n├── overview.md          ← Product positioning (from _index.md)\n├── architecture.md      ← System architecture, tech stack, design patterns, layering\n├── database.md          ← Full table schema, relationships, indexes, migrations\n├── api.md               ← API endpoints, params, auth, versioning\n├── routes.md            ← Complete route table (Web + API + Console)\n├── models.md            ← ORM relationships, scopes, accessors, observers\n├── services.md          ← Business logic, state machines, workflows, validation\n├── frontend.md          ← Component tree, page routing, state management\n├── auth.md              ← Auth scheme, roles/permissions matrix, OAuth\n├── integrations.md      ← Third-party: payment/email/SMS/storage/CDN/analytics\n├── jobs-events.md       ← Queue jobs, event listeners, scheduled tasks, notifications\n├── config-env.md        ← Environment variables, feature flags, cache strategy\n├── dependencies.md      ← Key dependencies, custom packages, vulnerabilities\n├── devops.md            ← Deployment, CI/CD, Docker, monitoring, logging\n├── test-coverage.md     ← Test strategy, coverage, weak spots\n├── tech-debt.md         ← TODO/FIXME/HACK inventory, dead code, complexity hotspots\n├── domain-flows.md      ← Core user journeys, domain boundaries, module coupling\n├── data-flow.md         ← Data lifecycle: external → import → process → store → output\n├── i18n.md              ← Internationalization, language coverage\n├── changelog.md         ← Scan diff log (what changed between scans)\n└── notes.md             ← Agent discoveries, gotchas, implicit rules\n\nScan Levels\nLevel\tScope\tWhen\tOutput\nL0 Snapshot\tSurface: directory tree, packages, env\tFirst onboard\tarchitecture, dependencies, config-env\nL1 Skeleton\tStructure: DB, routes, models, components\tFirst onboard\tdatabase, routes, api, models, frontend\nL2 Deep Dive\tLogic: services, auth, jobs, integrations\tOn-demand per module\tservices, auth, jobs-events, integrations, domain-flows, data-flow\nL3 Health Check\tQuality: tech debt, tests, security\tPeriodic / pre-release\ttech-debt, test-coverage, devops\nL4 Incremental\tDelta: git diff → update affected files\tAfter code changes\tchangelog + targeted updates\nContent Standards\n\nKnowledge files capture not just WHAT exists but WHY:\n\nDesign decisions: Why this approach was chosen\nImplicit business rules: Logic buried in code (e.g., \"orders auto-cancel after 72h\")\nGotchas: What breaks if you touch this module carelessly\nCross-module coupling: Where changing A silently breaks B\nPerformance hotspots: N+1 queries, missing indexes, bottleneck endpoints\nRole Responsibilities\nRole\tResponsibility\nProduct Lead\tGovernance: trigger scans, review quality, track freshness, ensure completeness\nFullstack Dev\tExecution: enter code directory, scan, generate/update knowledge files\nAll Agents\tConsumption: read product knowledge before any product-related decision\nPer-Stack Auto-Detection\n\nFullstack Dev auto-detects tech stack and applies stack-specific scan strategies:\n\nLaravel/PHP: migrations, route:list, Models, Services, Middleware, Policies, Jobs, Console/Kernel\nReact/Vue: components, router, stores, API client, i18n\nPython/Django/FastAPI: models.py, urls.py, views.py, middleware, celery\nGeneral: tree, git log, grep TODO/FIXME, .env.example, Docker, CI, tests\nTeam Coordination v2\nInbox Protocol v2 (status tracking)\n\nEvery inbox message now has a status field:\n\npending → received → in-progress → done (or blocked)\nChief-of-staff monitors timeouts: high>4h, normal>24h pending = intervention\nBlocked >8h = escalation to CEO\nRecipients MUST update status immediately upon reading\nTeam Dashboard (shared/status/team-dashboard.md)\n\nChief-of-staff maintains a \"live scoreboard\" updated every session:\n\n🔴 Urgent/Blocked items\n📊 Per-agent status table (last active, current task, status icon)\n📬 Unprocessed inbox summary (pending/blocked messages across all inboxes)\n🔗 Cross-agent task chain tracking (A→B→C with per-step status)\n📅 Today/Tomorrow focus\n\nAll agents read this file first when waking up. 5-second situational awareness.\n\nChief-of-Staff as Router\n\nThe chief is upgraded from \"briefing writer\" to \"active team router\":\n\nBlocker detection: scans all inboxes for overdue messages\nActive dispatch: writes reminders directly to lagging agents' inboxes\nTask chain tracking: identifies multi-agent workflows and tracks each step\nEscalation: persistent blockers get flagged to CEO\nRuns 4x/day (morning brief, midday patrol, afternoon patrol, evening brief)\nCron Schedule (10 jobs, up from 7)\nTime\tAgent\tType\tPurpose\n07:00\tdata-analyst\tdaily\tData pull + feedback scan\n08:00\tchief-of-staff\tannounce\tMorning: router scan + brief + quality\n09:00\tgrowth-lead\tdaily\tGEO/SEO/community\n09:00\tproduct-lead\tdaily (NEW)\tInbox + knowledge governance + task delegation\n10:00\tcontent-chief\tdaily M-F (was weekly)\tContent creation + collaboration\n10:00\tfullstack-dev\tdaily (enhanced)\tInbox + Deep Dive + dev tasks + patrol\n12:00\tchief-of-staff\tpatrol (NEW)\tRouter scan only, no brief\n15:00\tchief-of-staff\tpatrol (NEW)\tRouter scan only, no brief\n18:00\tchief-of-staff\tannounce\tEvening: router scan + summary + next day plan\n07:00 M/W/F\tintel-analyst\t3x/week\tCompetitor scan\nWhy These Changes Matter\nBefore\tAfter\tImpact\nInbox = blind drop\tInbox with status tracking\tMessages are acknowledged and trackable\nChief 2x/day\tChief 4x/day with router role\tBlockers caught within hours, not days\nContent-chief 1x/week\tDaily M-F\tActually produces content\nProduct-lead no cron\tDaily\tKnowledge governance happens\nNo team dashboard\tDashboard every session\tAll agents know the full picture\nNo timeout detection\tAutomatic timeout rules\tNothing falls through cracks\nKey Design Decisions\nShared workspace so qmd indexes everything for all agents\nInbox Protocol v2 with status tracking and timeout rules for reliable async communication\nChief as Router — not just a briefing writer but active coordinator who detects and resolves blockers\nTeam Dashboard — single source of truth for team-wide status, maintained by chief every session\nGEO as #1 priority (AI search = blue ocean)\nFullstack Dev spawns Claude Code via ACP for complex tasks\nProject Deep Dive gives all agents deep codebase understanding, not just surface-level product overviews\nCustomization\n\nEdit ROLES array in scripts/deploy.js to add/remove agents. Edit references/soul-templates.md for SOUL.md templates. Edit references/shared-templates.md for shared file templates."
  },
  "trust": {
    "sourceLabel": "tencent",
    "provenanceUrl": "https://clawhub.ai/beyound87/team-builder",
    "publisherUrl": "https://clawhub.ai/beyound87/team-builder",
    "owner": "beyound87",
    "version": "1.0.24",
    "license": null,
    "verificationStatus": "Indexed source record"
  },
  "links": {
    "detailUrl": "https://openagent3.xyz/skills/team-builder",
    "downloadUrl": "https://openagent3.xyz/downloads/team-builder",
    "agentUrl": "https://openagent3.xyz/skills/team-builder/agent",
    "manifestUrl": "https://openagent3.xyz/skills/team-builder/agent.json",
    "briefUrl": "https://openagent3.xyz/skills/team-builder/agent.md"
  }
}