跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

performance-analyzer

Use when the user asks to "analyze influencer campaign performance", "compare influencers", or "find what content worked"; produces metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings. Not for dollar-level return math — use roi-calculator. 达人营销效果分析/投放复盘

aaron-he-zhu · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add aaron-he-zhu/aaron-marketing-skills --skill performance-analyzer

技能说明


name: performance-analyzer slug: performance-analyzer displayName: "Performance Analyzer · 效果分析" summary: "活动效果分析:达成 vs 目标、平台与创作者维度拆解、优化建议" description: 'Use when the user asks to "analyze influencer campaign performance", "compare influencers", or "find what content worked"; produces metric scorecards vs target and benchmark, platform/influencer/content rankings, engagement-quality and sentiment reads, conversion-attribution breakdowns, and ranked learnings. Not for dollar-level return math — use roi-calculator. 达人营销效果分析/投放复盘' version: "20.2.0" license: Apache-2.0 compatibility: "Claude Code and compatible agent-skill hosts" homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills" when_to_use: "Use mid-flight or post-campaign when a user wants to evaluate influencer results, compare creators against each other, find top-performing content or formats, judge engagement quality and comment sentiment, connect influencer activity to conversions, or build performance benchmarks for future planning." argument-hint: " [platform or influencer handles]" metadata: {"author": "aaron-he-zhu", "version": "20.2.0", "discipline": "influencer", "phase": "report", "geo-relevance": "low", "hermes": {"tags": ["marketing", "influencer", "report"], "category": "influencer"}, "openclaw": {"emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}

Performance Analyzer

Analyze influencer campaign performance past surface metrics — score results vs target/benchmark, rank platforms/creators/content, read engagement quality and sentiment, attribute conversions, and write ranked learnings.

Cross-discipline (paid ads): this is also the cross-channel paid-ads scorecard/anomaly lens — account-wide metric rollups vs target/benchmark that feed ad-test-designer (what to test) and paid-measurement-loop (what to read back). Save paid runs under memory/ad/performance-analyzer/.

Quick Start

Analyze performance of [campaign name] influencer campaign

Compare creators within one campaign:

Compare performance of these influencers from [campaign]: @handle1, @handle2, @handle3

Skill Contract

  • Reads: campaign name and date range; native platform analytics (reach, views, engagement); influencer-supplied reports or screenshots; website/GA traffic and conversion data; sales and promo-code redemption data; targets, benchmarks, and the preregistered decision rule/readback window if supplied; the optional lightweight campaign tracker and its evidence_refs; and any ROI/ROAS artifact already computed by roi-calculator. Reuse each explicit upstream opaque creator_ref or a verified creator-registry aggregate ID; a raw handle/name/URL/provider ID is transient lookup input only and never becomes a saved identity. Per-creator baselines come from memory/creators/<aggregate-id>.md only when an authorized artifact or verified registry link resolves that ref. Never derive the path from a raw locator.
  • Writes: return the performance analysis inline by default. When a current non-forked tracker-state artifact proves measured or closed, include the compact Campaign Retro Card from step 8 bound to that campaign, creator, measurement contract, and decision rule. Save the analysis and card together to memory/influencer/performance-analyzer/YYYY-MM-DD-<campaign>.md only with exact WARM-save authorization; saved tables, headings, evidence, and handoffs use creator_ref plus opaque source refs, never raw handles, names, profile URLs, email addresses, or provider IDs.
  • Promotes: only with separate exact authorization, promote durable evidence-backed campaign facts (verified metric results and descriptive format/platform associations) to memory/hot-cache.md; any ROI/ROAS value remains tied to its exact roi-calculator artifact. The Retro Card's qualitative renew | retest | retire | unknown decision, rationale, next hypothesis, and limitations remain WARM and are never promoted as registry truth. This skill makes no creator-registry proposal: after a creator row is closed, the existing boundary still permits only a separately authorized, evidence-backed actual rate, signed rights window/expiry, or measured performance baseline to be proposed by the owning workflow; creator-registry alone decides whether it becomes canonical.
  • Done when:
    • Core metrics are compared against compatible source-dated targets/benchmarks. Missing or incompatible context is Unknown/NOT_SCORED, never an invented /10 score or adjective verdict.
    • Creators/platforms/content are ranked only under a declared metric, compatible window/basis, complete candidate set, and preregistered decision rule; descriptive associations and causal hypotheses stay visibly separate.
    • Conversions use one declared attribution model with deduplicated, mutually exclusive counted buckets; overlapping promo/UTM/direct observations remain reconciliation evidence, and modeled influence stays Estimated outside the counted total.
    • With verified current measured or closed state, each requested next-cycle decision has a scope-bound Campaign Retro Card with campaign/creator/state/measurement/decision-rule refs, evidence-backed rationale, evidence_refs, next-campaign hypothesis, and unresolved limitations; insufficient decision evidence resolves to unknown, while missing/forked state blocks the card.
  • Primary next skill: roi-calculator — turn measured performance into dollar-level return.

Handoff Summary

Emit the standard shape from skill-contract.md §Handoff Summary Format.

Data Sources

This family needs no live integrations (Tier 1). The skill runs entirely on inputs you provide

阅读完整来源 ↗