ClawHub

Spillover Estimator

v1.0.0

Estimate whether one commerce channel is creating measurable spillover into another channel using simple exports, campaign timing, and directional evidence....

⭐ 0· 157·0 current·0 all-time
byLeroyCreates@leooooooow

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for leooooooow/spillover-estimator.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Spillover Estimator" (leooooooow/spillover-estimator) from ClawHub.
Skill page: https://clawhub.ai/leooooooow/spillover-estimator
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install spillover-estimator

ClawHub CLI

Package manager switcher

npx clawhub@latest install spillover-estimator
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description match the instructions: the SKILL.md asks for source and downstream channel exports, timing context, and gives a lightweight workflow for directional spillover estimates. Nothing requested (no env vars, binaries, or installs) is out of scope for a measurement helper.
✓
Instruction Scope
Runtime instructions only ask the agent to collect user-provided exports/screenshots/CSVs or to use common platform exports (Shopify, Amazon, TikTok, ad platforms, Google Sheets). There are no directives to read unrelated system files, access hidden credentials, or call unexpected external endpoints.
✓
Install Mechanism
No install spec and no code files — instruction-only. This minimizes disk writes and arbitrary code execution risk.
✓
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. The data it asks for (exports/CSV/screenshots) is proportional to the task.
✓
Persistence & Privilege
always is false and the skill does not request persistent or elevated platform privileges. It does not modify other skills or system settings.
Assessment
This skill appears coherent and low-risk because it is instruction-only and asks you to provide channel exports or screenshots. Before using it: (1) avoid uploading credentials or API keys — provide exports or sanitized CSVs instead; (2) redact any personally identifiable customer data if you share real exports; (3) remember results are directional, not causal — the SKILL.md explicitly warns about caveats; (4) the package source/homepage is unknown — if you require provenance, verify the author (Razestar) or request a published homepage or repository; (5) note the license: CC BY-NC-SA 4.0 for non-commercial use, and a paid commercial license is required for commercial use.

Like a lobster shell, security has layers — review code before you run it.

latestvk976t87wzv9s72dm6qthwdd3ms834pnb
157downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0
LeroyCreates@leooooooow
latest
Download

Spillover Estimator

Estimate cross-channel spillover without pretending to prove perfect attribution.

Skill Card

  • Category: Measurement
  • Core problem: Did growth in one channel also lift another channel?
  • Best for: Operators comparing TikTok, Amazon, DTC, creator, paid, and marketplace channel effects
  • Expected input: Source channel data + downstream channel data + timing context
  • Expected output: Directional spillover estimate + confidence note + action recommendation
  • Creatop handoff: Feed findings into budget allocation and channel planning

Before you run

Ask the user to clarify:

  • source channel to evaluate
  • downstream channel(s) to check for spillover
  • date range
  • major campaign or promo dates
  • whether they have exports, screenshots, or CSV data

If structured data is missing, say the result will be directional, not causal proof.

Optional tools / APIs

Useful but not required:

  • Shopify / WooCommerce export
  • Amazon sales export
  • TikTok Shop export
  • ad platform export
  • Google Sheets / CSV

If the user does not have APIs connected, ask for manual exports first instead of blocking the workflow.

Workflow

  1. Confirm channel scope and time window.
  2. Collect source-channel change signals.
  3. Collect downstream-channel change signals.
  4. Align timing around campaigns, creator drops, content bursts, or promo windows.
  5. Judge whether the downstream lift looks:
    • likely related
    • weak / mixed
    • insufficient evidence
  6. Explain the estimate with honest caveats.

Output format

Return in this order:

  1. Executive summary
  2. Spillover estimate
  3. Evidence blocks
  4. Confidence and caveats
  5. Recommended next step

Fallback mode

If the user only has weekly snapshots, rough screenshots, or partial exports:

  • use simple directional comparison
  • do not claim causal attribution
  • clearly label missing data and confidence limits

Quality rules

  • Never overclaim causality from timing alone.
  • Prefer directional clarity over fake precision.
  • Separate channel correlation from verified lift.
  • Make the user’s next measurement step obvious.

License

Copyright (c) 2026 Razestar.

This skill is provided under CC BY-NC-SA 4.0 for non-commercial use. You may reuse and adapt it with attribution to Razestar, and share derivatives under the same license.

Commercial use requires a separate paid commercial license from Razestar. No trademark rights are granted.

Comments

Loading comments...