openclaw 网盘下载
OpenClaw

技能详情(站内镜像,无评论)

首页 > 技能库 > Growth Hub

Top-level orchestration skill that manages ads operations and enterprise growth decisions across Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube A...

开发与 DevOps

作者:danyangliu @danyangliu-sandwichlab

许可证:MIT-0

MIT-0 ·免费使用、修改和重新分发。无需归因。

版本:v1.0.1

统计:⭐ 0 · 123 · 0 current installs · 0 all-time installs

0

安装量(当前) 0

🛡 VirusTotal :良性 · OpenClaw :良性

Package:danyangliu-sandwichlab/growth-hub

安全扫描(ClawHub)

  • VirusTotal :良性
  • OpenClaw :良性

OpenClaw 评估

The skill's instructions, inputs, and outputs are consistent with a top-level orchestration role for ad and growth workflows; it does not request credentials or install code, but because it delegates to channel-specific 'specialist' skills you should verify those downstream skills and review invocation policies before enabling autonomous runs.

目的

Name/description, input/output contracts, workflow, and decision rules all align with a top-level orchestration/orchestrator role for ad channels and growth decisions. The skill does not ask for unrelated binaries, environment variables, or config paths — nothing requested appears out of scope for an orchestration skill.

说明范围

SKILL.md stays at an orchestration level (parse intent, route to specialist skills, build KPI trees, sequence actions). It does not instruct reading local files, secrets, or external endpoints itself. Note: the instructions explicitly route to 'specialist skills' for channel-level execution; that means this skill may cause the agent to invoke other skills which could access credentials or external services. The orchestration role is inherently…

安装机制

No install spec and no code files — instruction-only skill. This is the lowest-risk install surface because nothing is downloaded or written to disk by the skill itself.

证书

The skill declares no required environment variables, credentials, or config paths. This is proportionate for an instruction-only orchestrator. However, because it delegates to channel-specific skills (e.g., Meta, Google Ads, TikTok), those downstream skills may require sensitive credentials — so credential access is an indirect risk to be managed outside this skill.

持久

always is false (normal). disable-model-invocation is false, meaning the model may autonomously invoke the skill — this is the platform default. Because Growth Hub is a top-level orchestrator, autonomous invocation increases blast radius (it could route work automatically to other skills). Consider adding explicit human review gates or limiting autonomous invocation if you do not want unattended orchestration.

综合结论

What to consider before installing: - The skill itself is instruction-only and coherent for orchestration; it does not ask for secrets or install code. - The main risk is indirect: Growth Hub routes to channel-specific 'specialist' skills that may require API keys and external access. Before enabling, review which specialist skills will be invoked, and verify their provenance, required credentials, and permissions. - If you want to limit risk,…

安装(复制给龙虾 AI)

将下方整段复制到龙虾中文库对话中,由龙虾按 SKILL.md 完成安装。

请把本段交给龙虾中文库(龙虾 AI)执行:为本机安装 OpenClaw 技能「Growth Hub」。简介:Top-level orchestration skill that manages ads operations and enterprise growth…。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装:https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/danyangliu-sandwichlab/growth-hub/SKILL.md
(来源:yingzhi8.cn 技能库)

SKILL.md

打开原始 SKILL.md(GitHub raw)

---
name: growth-hub
description: Top-level orchestration skill that manages ads operations and enterprise growth decisions across Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads, and DSP/programmatic.
---

# Growth Hub

## Purpose
Core mission:
- Act as the top-level orchestration layer for the Growth Hub system.
- Parse user intent and route to the right execution or decision path.
- Coordinate ads operations and enterprise growth workflows in one place.
- Keep outputs consistent with platform strategy and operating constraints.

## When To Trigger
Use this skill when the user asks for:
- end-to-end planning that spans ads execution and business growth decisions
- a unified control-plane recommendation instead of a single specialist task
- cross-functional coordination among marketing, finance, and growth teams
- platform-level system behavior and operating rules

High-signal keywords:
- growth hub, growth, strategy, report, dashboard
- ads, advertising, campaign, performance, optimize
- revenue, profit, budget, allocation, forecast

## Input Contract
Required:
- business_goal_bundle: revenue, profit, cashflow, and growth targets
- operating_scope: markets, channels, teams, and timeline
- decision_priority: speed, efficiency, scale, or risk control

Optional:
- platform_constraints
- capital_constraints
- existing_operating_playbook
- governance_policies

## Output Contract
1. Unified Intent Map
2. Orchestration Plan (which helper/skill does what)
3. Cross-functional KPI Tree
4. Execution and Decision Timeline
5. Governance and Escalation Matrix

## Workflow
1. Parse the request into execution and decision components.
2. Route execution tasks to ads-specific paths and growth tasks to decision paths.
3. Build shared KPI tree across teams.
4. Sequence actions and dependencies.
5. Output control-plane instructions and ownership.

## Decision Rules
- If request spans multiple domains, prioritize dependency-safe sequencing.
- If KPI conflict exists, surface trade-off before final recommendation.
- If governance constraints are missing, apply conservative defaults.
- If decision impact is high, require explicit review gates.

## Platform Notes
Primary scope:
- Meta (Facebook/Instagram), Google Ads, TikTok Ads, YouTube Ads, Amazon Ads, Shopify Ads, DSP/programmatic

Platform behavior guidance:
- Use specialist skills for channel-level execution details.
- Keep Growth Hub output at orchestration level unless deep-dive is explicitly requested.

## Constraints And Guardrails
- Do not bypass governance for speed.
- Keep ownership and accountability explicit in every plan.
- Separate policy from recommendation.

## Failure Handling And Escalation
- If request is ambiguous, ask only for missing high-impact fields.
- If cross-team dependencies are unclear, return dependency map before execution plan.
- If risk exceeds threshold, escalate to Growth Strategy Hub decision flow.

## Code Examples
### Orchestration Payload (JSON)

    {
      "orchestrator": "growth-hub",
      "execution_path": ["ads-execution-hub", "shopify-ads-helper"],
      "decision_path": ["growth-strategy-hub"],
      "governance_level": "standard"
    }

### KPI Tree Spec (YAML)

    north_star: contribution_profit
    children:
      - revenue
      - blended_roas
      - cashflow_stability
      - customer_ltv

## Examples
### Example 1: Unified quarterly plan
Input:
- Need one plan for ads + enterprise growth

Output focus:
- orchestration map
- ownership matrix
- phased timeline

### Example 2: Multi-team execution conflict
Input:
- Marketing wants scale, finance wants cash preservation

Output focus:
- conflict resolution logic
- KPI trade-off framework
- staged plan

### Example 3: Platform expansion + governance
Input:
- Add two channels while maintaining controls

Output focus:
- control-plane routing
- governance gates
- escalation paths

## Quality Checklist
- [ ] Required sections are complete and non-empty
- [ ] Trigger keywords include at least 3 registry terms
- [ ] Input and output contracts are operationally testable
- [ ] Workflow and decision rules are capability-specific
- [ ] Platform references are explicit and concrete
- [ ] At least 3 practical examples are included