report-generator
Use when the user asks to "create a campaign report", "build an executive summary", or "deliver client results"; produces audience-tailored influencer marketing reports (executive, client, internal team) with data tables, narrative, key learnings, and recommendations. Not for raw metric computation — use performance-analyzer. 达人营销报告/结案汇报
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-03
- Stars
- ★ 8
- Forks
- 2
01 前言 Front Matter
- name
- report-generator
- slug
- aaron-report-generator
- license
- Apache-2.0
- summary
- 面向干系人的营销活动报告:叙事结构、图表建议与洞察提炼
- version
- 20.1.0
- homepage
- https://github.com/aaron-he-zhu/aaron-marketing-skills
- metadata
- { "phase": "report", "author": "aaron-he-zhu", "hermes": { "tags": [ "marketing", "influencer", "report" ], "category": "influencer" }, "version": "20.1.0", "openclaw": { "emoji": "📣", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills" }, "discipline": "influencer", "geo-relevance": "low" }
- description
- Use when the user asks to "create a campaign report", "build an executive summary", or "deliver client results"; produces audience-tailored influencer marketing reports (executive, client, internal team) with data tables, narrative, key learnings, and recommendations. Not for raw metric computation — use performance-analyzer. 达人营销报告/结案汇报
- displayName
- Report Generator · 报告生成
- when_to_use
- Activate after a campaign or reporting period ends and the user needs a written report for a specific stakeholder. Triggers include post-campaign wrap-ups, executive or board summaries, client-facing results decks, internal team retrospectives, and monthly or quarterly performance reports. Pick this when the inputs are already-computed metrics that need structure, narrative, and recommendations for a named audience.
- argument-hint
- <campaign name> [audience: executive|client|team|board]
- compatibility
- Claude Code and compatible agent-skill hosts
02 资源文件 1
- 参考文档references/report-templates.md18.0 KB
03 SKILL.md 正文
Report Generator
This skill helps you create professional influencer marketing reports that tell the story of your campaign performance. It adapts content and depth based on the audience.
Cross-discipline (paid ads): this is also the paid-ads reporting surface — build exec/client/channel reports from RQS history (
memory/audits/ad/) and measurement-loop readback verdicts. It presents metrics; it does not compute them (return math stays in roi-calculator). Save paid runs undermemory/ad/report-generator/.
Quick Start
Shortest invocation:
Create a campaign report for [campaign name] for [audience: executive/client/team]
Common scenario:
Generate an executive summary for our Q3 influencer campaigns
Skill Contract
- Reads: campaign name, reporting period, target audience, opaque
client_ref,preparer_ref,contact_ref, andowner_refvalues when those roles appear, plus already-computed metrics with their provenance, window, target/comparator, and source artifact refs. ROI/ROAS/net-return values must come from roi-calculator, and performance deltas/rankings from performance-analyzer; raw spend plus revenue is not a computed ROI handoff. Reuse opaquecreator_refvalues from those artifacts, the optional tracker/stage, and an existing Campaign Retro Card. Raw client/staff/owner names, email addresses, and organization labels are transient resolver inputs only. - Writes: return the finished audience-appropriate report inline by default. Preserve only a current scope-bound Campaign Retro Card from
performance-analyzer; if it is absent or invalid, include anunknownplaceholder rather than deriving a decision. Save the report/card together tomemory/influencer/report-generator/YYYY-MM-DD-<topic>.mdonly with exact WARM-save authorization. Every saved report, template field, appendix, and handoff uses opaqueclient_ref,preparer_ref,contact_ref,owner_ref,creator_ref, and artifact/source refs—never resolved client/staff/owner/creator names, organization labels, contact emails, profile URLs, or provider IDs. Resolve those refs only in-memory for one explicitly named audience's transient render, discard the resolution afterward, and never save the mapping. Any external send/share/export requires a new exact authorization naming the report artifact/version, recipient audience, delivery channel, and identity/asset refs allowed for that audience; report creation or WARM save does not authorize distribution. - Promotes: only with separate exact authorization, promote durable evidence-backed facts (verified final ROI/ROAS, measured performance baselines, and headline learnings) to
memory/hot-cache.md. The Retro Card's qualitativerenew | retest | retire | unknowndecision, rationale, next hypothesis, and limitations remain WARM and are not creator-registry facts. This skill makes no creator-registry proposal: after a creator row is closed, only a separately authorized, evidence-backed actual rate, signed rights window/expiry, or measured performance baseline may be proposed by the owning workflow; creator-registry alone decides whether it becomes canonical. - Done when:
- The report matches the requested audience template (executive, client, team, or board).
- Every metric is paired with compatible source-dated context (target, benchmark, or prior period) or explicitly marked
Unknown/NEEDS_INPUT; the report does not manufacture context or recompute missing performance/return metrics. - The report ends with concrete recommendations and, where relevant, action items.
- When current tracker-state evidence proves
measuredorclosed, the report package preserves the matching performance-analyzer Retro Card with exact campaign/creator/state/measurement/decision-rule refs; a missing or invalid card produces anunknownplaceholder andNEEDS_INPUT, never a newly derived decision. - Saved/copyable output contains only opaque client/preparer/contact/owner/creator refs; any resolved labels/contact details exist only in a transient render for the declared audience, and external distribution is blocked without a fresh audience-scoped exact authorization.
- Primary next skill: content-quality-auditor
Handoff Summary
Emit the standard shape from skill-contract.md §Handoff Summary Format.
Data Sources
This family ships Tier 1: no live integration is required. Give it already-computed, provenance-labeled campaign metrics and it builds the report. If only raw observations are supplied, route metric analysis to performance-analyzer; if only spend/revenue/LTV inputs are supplied, route return math to roi-calculator before reporting.
Optional connectors that can pre-fill data where available:
~~social platform analytics— reach, impressions, engagement, video views per post~~influencer database— creator handles, tiers, fees, audience demographics~~analytics— link clicks, conversions, attributed revenue~~CRM— new-customer counts and downstream revenue
Without any of these, the skill asks for the existing computed artifacts/metrics. It may return a partial report shell, but any missing dependent claim remains Unknown/NEEDS_INPUT; it does not calculate ROI/ROAS, rankings, attribution, or causal drivers here. See CONNECTORS.md for the free/keyless data recipe per category.
Instructions
When a user requests a report:
-
Determine report parameters — set report type (post-campaign/monthly/quarterly/annual), campaign(s), period, one explicit audience, opaque
client_ref/preparer_ref/contact_ref/owner_refvalues where applicable, and supplied tracker stage when present. Match depth to the audience: executive wants ROI and strategy at a high level; client wants results and value; team wants detailed learnings and optimization; board wants business impact. Keep any raw identity/contact locator transient. See the audience-needs matrix in report-templates.md. -
Pick the audience template and fill it in — full executive, client, and internal-team templates live in report-templates.md. Pull performance metrics/deltas only from
performance-analyzeroutput and financial ratios only fromroi-calculatoroutput. If the required computed artifact is absent, return a partial shell plusNEEDS_INPUTand the exact handoff; do not recompute from raw numbers. Pair every metric with compatible source-dated context or mark the comparison pending. -
Apply visualization and writing guidance — choose the right chart per data point and per audience, and follow the lead-with-outcomes narrative arc. See the visualization recommendations and writing best practices in report-templates.md.
-
Close with recommendations and action items — end every report with concrete next steps; add an opaque
owner_ref/deadline action-items table for team and board audiences. -
Represent the measured cycle without re-deciding it — only preserve an existing Campaign Retro Card from
performance-analyzerwhen it explicitly binds the samecampaign_id, opaquecreator_ref, current non-forked measured/closed tracker-state ref, locked measurement contract, and precommitted decision-rule ref. Never derive or change the decision in this reporting skill. If the card is absent, mismatched, or stale, emit a bounddecision: unknownplaceholder plusNEEDS_INPUTfor the performance-analyzer artifact. Keep the card outside a client/board-facing copy unless the user requests it. -
Return, then offer persistence or distribution — return the ref-only report and any Retro Card inline. Offer
memory/influencer/report-generator/YYYY-MM-DD-<topic>.md(ormemory/ad/report-generator/for paid runs) for exact WARM-save authorization; the saved artifact keepsclient_ref,preparer_ref,contact_ref, andowner_refunresolved. If the user requests a human-readable audience copy, resolve only the approved refs in-memory for that one explicit audience and discard the mapping after rendering. Before any external send/share/export, require a new exact authorization naming the exact report artifact/version, recipient audience, delivery channel, and allowed identity/asset refs; never infer distribution authority from report generation, transient rendering, or WARM save. Request a separate authorization before promoting any eligible durable fact tomemory/hot-cache.md. After an authorized save, offer a handoff to campaign-planner to append the saved artifact reference to the relevant tracker row'sevidence_refs; that tracker edit needs a fresh path-and-operation-scoped exact WARM authorization, and this skill neither edits the tracker nor advances itsstage. -
Offer, do not launch, the next-cycle assessment — if the user wants to select the next roster, offer an explicit handoff to fit-scorer with the Retro Card's cited evidence and
next_campaign_hypothesis. Do not invoke it automatically and do not translate, invent, or carry forward a STAR/SQS verdict from the qualitative Retro decision.
Example
User: "Create an executive report for Holiday Campaign 2024. roi-ref-01 already reports $50K spend, $165K attributed revenue, 230% arithmetic ROI and 3.3:1 ROAS on its declared verified basis. performance-ref-01 reports 3.5M reach across 15 opaque creator refs and calculated target deltas. The preregistered targets were $100K attributed revenue, 2:1 ROAS, and 2M reach. No segmented breakdown or reallocation rule is included."
Output (excerpt — full template in report-templates.md):
# Holiday Campaign 2024: Executive Summary
## Bottom Line: Campaign Exceeded the Supplied Targets ✅
**ROI: 230% (`roi-ref-01`)** | **ROAS: 3.3:1 (`roi-ref-01`)** | **Attributed Revenue: $165,000**
Metric status: financial values and their calculation/provenance come from `roi-ref-01`; reach and target deltas come from `performance-ref-01`. This report formats those outputs and performs no return or attribution recomputation. No incremental-revenue claim is made.
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Attributed revenue | $100K | $165K | ✅ +65% |
| ROAS | 2:1 | 3.3:1 | ✅ +65% |
| Reach | 2M | 3.5M | ✅ +75% |
### Recommendation
The supplied overall figures clear the supplied targets. A platform, creator-tier, content-format, or budget-change recommendation is `NEEDS_INPUT` because no segmented results or decision rule was supplied; request that evidence before proposing a Q1 reallocation.
Reference Materials
- report-templates.md — full executive/client/team templates, visualization recs, writing best practices, worked example
- skill-contract.md — shared contract and handoff format
- state-model.md — memory tiers and save-path convention
- CONNECTORS.md — free/keyless data recipes per connector category
- performance-analyzer — generates the metrics this report consumes
- roi-calculator — supplies ROI/ROAS figures
- campaign-planner — original plan to compare results against
- content-amplifier — amplification results to report on
- content-quality-auditor — quality gate for the report itself
Next Best Skill
Primary: content-quality-auditor — run the finished report through the publish-readiness gate before it goes to a stakeholder.
Alternates (same report phase / influencer family):
- performance-analyzer — if the report exposes data gaps, re-analyze before re-reporting.
- roi-calculator — recompute return figures if the financial inputs changed.
Termination note (visited-set): if a recommended skill has already been invoked this session, stop and report the chain as complete instead of re-running it. Honor a max chain depth of 3 hops to avoid loops.
04 同仓库更多 Skills
video
When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'record a product demo,' 'feature demo video,' 'in-app demo,' 'video pipeline,' 'copy this edit,' 'match this video style,' 'reverse-engineer this video,' 'edit like this reference,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.
social
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' 'create a reel,' 'social listening,' 'brand mentions,' 'competitor monitoring,' 'top posts to comment on,' 'find people asking for,' 'carousel,' 'slide-by-slide,' or 'document post.' Use this for social content, repurposing, scheduling, video scripts, and listening. Posts avoid AI tells like 'it's not X, it's Y' reveals and broetry. For broader content strategy, see content-strategy. For paid ads, see ad-creative. For earned media, see public-relations.
sms
When the user wants to plan, build, or optimize SMS, MMS, or WhatsApp marketing — including welcome flows, abandoned cart texts, post-purchase, win-back, promotional sends, or transactional/auth SMS. Also use when the user mentions "SMS marketing," "text message campaigns," "SMS sequence," "SMS automation," "abandoned cart text," "post-purchase SMS," "Klaviyo SMS," "Postscript," "Attentive," "Twilio," "A2P 10DLC," "TCPA," "SMS compliance," "short code," "toll-free SMS," "MMS campaign," "should I do SMS," "SMS vs email," "WhatsApp marketing," "WhatsApp Business API," "WhatsApp templates," or "click-to-WhatsApp." For email sequences, see emails. For SMS copy framing, see copywriting. For opt-in popups that capture phone numbers, see popups.
site-architecture
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," "site navigation," "which website builder should I use," "migrate my website," or "add a blog to my existing site." Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.
signup
When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," "indexing issues," "stuck on page 2," "striking distance keywords," "title tag rewrite," "low CTR," "local SEO," "Google Business Profile," or "map pack." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.