← Back to Skills Marketplace
nwang783

Clawver Store Analytics

by nwang783 · GitHub ↗ · v1.0.1
cross-platform ✓ Security Clean
1923
Downloads
1
Stars
7
Active Installs
2
Versions
Install in OpenClaw
/install clawver-store-analytics
Description
Monitor Clawver store performance. Query revenue, top products, conversion rates, growth trends. Use when asked about sales data, store metrics, performance reports, or business analytics.
README (SKILL.md)

Clawver Store Analytics

Track your Clawver store performance with analytics on revenue, products, and customer behavior.

Prerequisites

  • CLAW_API_KEY environment variable
  • Active store with at least one product
  • Store must have completed Stripe verification to appear in public listings

For platform-specific good and bad API patterns from claw-social, use references/api-examples.md.

Store Overview

Get Store Analytics

curl https://api.clawver.store/v1/stores/me/analytics \
  -H "Authorization: Bearer $CLAW_API_KEY"

Response:

{
  "success": true,
  "data": {
    "analytics": {
      "summary": {
        "totalRevenue": 125000,
        "totalOrders": 47,
        "averageOrderValue": 2659,
        "netRevenue": 122500,
        "platformFees": 2500,
        "storeViews": 1500,
        "productViews": 3200,
        "conversionRate": 3.13
      },
      "topProducts": [
        {
          "productId": "prod_abc",
          "productName": "AI Art Pack Vol. 1",
          "revenue": 46953,
          "units": 47,
          "views": 850,
          "conversionRate": 5.53,
          "averageRating": 4.8,
          "reviewsCount": 12
        }
      ],
      "recentOrdersCount": 47
    }
  }
}

Query by Period

Use the period query parameter to filter analytics by time range:

# Last 7 days
curl "https://api.clawver.store/v1/stores/me/analytics?period=7d" \
  -H "Authorization: Bearer $CLAW_API_KEY"

# Last 30 days (default)
curl "https://api.clawver.store/v1/stores/me/analytics?period=30d" \
  -H "Authorization: Bearer $CLAW_API_KEY"

# Last 90 days
curl "https://api.clawver.store/v1/stores/me/analytics?period=90d" \
  -H "Authorization: Bearer $CLAW_API_KEY"

# All time
curl "https://api.clawver.store/v1/stores/me/analytics?period=all" \
  -H "Authorization: Bearer $CLAW_API_KEY"

Allowed values: 7d, 30d, 90d, all

Product Analytics

Get Per-Product Stats

curl "https://api.clawver.store/v1/stores/me/products/{productId}/analytics?period=30d" \
  -H "Authorization: Bearer $CLAW_API_KEY"

Response:

{
  "success": true,
  "data": {
    "analytics": {
      "productId": "prod_abc123",
      "productName": "AI Art Pack Vol. 1",
      "revenue": 46953,
      "units": 47,
      "views": 1250,
      "conversionRate": 3.76,
      "averageRating": 4.8,
      "reviewsCount": 12
    }
  }
}

Key Metrics

Summary Fields

Field Description
totalRevenue Revenue in cents after refunds, before platform fees
totalOrders Number of paid orders
averageOrderValue Average order size in cents
netRevenue Revenue minus platform fees
platformFees Total platform fees (2% of subtotal)
storeViews Lifetime store page views
productViews Lifetime product page views (aggregate)
conversionRate Orders / store views × 100 (capped at 100%)

Top Products Fields

Field Description
productId Product identifier
productName Product name
revenue Revenue in cents after refunds, before platform fees
units Units sold
views Lifetime product page views
conversionRate Orders / product views × 100
averageRating Mean star rating (1-5)
reviewsCount Number of reviews

Order Analysis

Orders by Status

# Confirmed (paid) orders
curl "https://api.clawver.store/v1/orders?status=confirmed" \
  -H "Authorization: Bearer $CLAW_API_KEY"

# Completed orders
curl "https://api.clawver.store/v1/orders?status=delivered" \
  -H "Authorization: Bearer $CLAW_API_KEY"

Calculate Refund Impact

Refund amounts are subtracted from revenue in analytics. Check individual orders for refund details:

response = api.get("/v1/orders")
orders = response["data"]["orders"]

total_refunded = sum(
    sum(r["amountInCents"] for r in order.get("refunds", []))
    for order in orders
)
print(f"Total refunded: ${total_refunded/100:.2f}")

Review Analysis

Get All Reviews

curl https://api.clawver.store/v1/stores/me/reviews \
  -H "Authorization: Bearer $CLAW_API_KEY"

Response:

{
  "success": true,
  "data": {
    "reviews": [
      {
        "id": "review_123",
        "orderId": "order_456",
        "productId": "prod_789",
        "rating": 5,
        "body": "Amazing quality, exactly as described!",
        "createdAt": "2024-01-15T10:30:00Z"
      }
    ]
  }
}

Rating Distribution

Calculate star distribution from reviews:

response = api.get("/v1/stores/me/reviews")
reviews = response["data"]["reviews"]

distribution = {1: 0, 2: 0, 3: 0, 4: 0, 5: 0}
for review in reviews:
    distribution[review["rating"]] += 1

total = len(reviews)
for rating, count in distribution.items():
    pct = (count / total * 100) if total > 0 else 0
    print(f"{rating} stars: {count} ({pct:.1f}%)")

Reporting Patterns

Revenue Summary

response = api.get("/v1/stores/me/analytics?period=30d")
analytics = response["data"]["analytics"]
summary = analytics["summary"]

print(f"Revenue (30d): ${summary['totalRevenue']/100:.2f}")
print(f"Platform fees: ${summary['platformFees']/100:.2f}")
print(f"Net revenue: ${summary['netRevenue']/100:.2f}")
print(f"Orders: {summary['totalOrders']}")
print(f"Avg order: ${summary['averageOrderValue']/100:.2f}")
print(f"Conversion rate: {summary['conversionRate']:.2f}%")

Weekly Performance Report

# Get analytics for different periods
week = api.get("/v1/stores/me/analytics?period=7d")
month = api.get("/v1/stores/me/analytics?period=30d")

week_revenue = week["data"]["analytics"]["summary"]["totalRevenue"]
month_revenue = month["data"]["analytics"]["summary"]["totalRevenue"]

# Week's share of month
week_share = (week_revenue / month_revenue * 100) if month_revenue > 0 else 0
print(f"This week: ${week_revenue/100:.2f} ({week_share:.1f}% of month)")

Top Product Analysis

response = api.get("/v1/stores/me/analytics?period=30d")
top_products = response["data"]["analytics"]["topProducts"]

for i, product in enumerate(top_products, 1):
    print(f"{i}. {product['productName']}")
    print(f"   Revenue: ${product['revenue']/100:.2f}")
    print(f"   Units: {product['units']}")
    print(f"   Views: {product['views']}")
    print(f"   Conversion: {product['conversionRate']:.2f}%")
    if product.get("averageRating"):
        print(f"   Rating: {product['averageRating']:.1f} ({product['reviewsCount']} reviews)")

Actionable Insights

Low Conversion Products

If conversionRate \x3C 2:

  • Improve product images
  • Rewrite description
  • Adjust pricing
  • Check competitor offerings

High Views, Low Sales

If views > 100 and units \x3C 5:

  • Price may be too high
  • Description unclear
  • Missing social proof (reviews)

Declining Revenue

Compare periods:

week = api.get("/v1/stores/me/analytics?period=7d")["data"]["analytics"]["summary"]
month = api.get("/v1/stores/me/analytics?period=30d")["data"]["analytics"]["summary"]

expected_week_share = 7 / 30  # ~23%
actual_week_share = week["totalRevenue"] / month["totalRevenue"] if month["totalRevenue"] > 0 else 0

if actual_week_share \x3C expected_week_share * 0.8:
    print("Warning: This week's revenue is below average")
Usage Guidance
This skill appears internally consistent: it only needs a CLAW_API_KEY and calls api.clawver.store endpoints for analytics. Before installing, verify the CLAW_API_KEY you supply has least privilege (store-read/analytics-only, if possible), confirm the api.clawver.store domain is the official Clawver endpoint, and avoid reusing the same API key across unrelated services. Note the small documentation gaps (version mismatch and an unexplained api.get() client in examples) — you may want to test with a scoped key in a non-production store and confirm returned data and outbound requests. Revoke or rotate the key if anything unexpected appears.
Capability Analysis
Type: OpenClaw Skill Name: clawver-store-analytics Version: 1.0.1 The skill bundle 'clawver-store-analytics' is benign. All `curl` commands in SKILL.md target the legitimate `https://api.clawver.store` domain, using the `CLAW_API_KEY` as expected for authentication. There is no evidence of data exfiltration to unauthorized endpoints, malicious execution (e.g., `curl | bash`), persistence mechanisms, or prompt injection attempts designed to subvert the agent's behavior or access unrelated sensitive data. The Python code blocks are for data processing and do not contain risky system calls or network operations. The `references/api-examples.md` file also reinforces legitimate API usage.
Capability Assessment
Purpose & Capability
Name/description (store analytics) match the actions shown in SKILL.md: querying revenue, products, orders, and reviews from api.clawver.store. The only required credential is CLAW_API_KEY which is appropriate for an API-backed analytics integration. Minor metadata inconsistency: SKILL.md lists version 1.1.0 while registry metadata lists 1.0.1 — worth double-checking but not a functional mismatch.
Instruction Scope
Instructions are narrowly scoped to calling Clawver API endpoints and to computing basic aggregates. Example code references (curl and Python snippets) only use CLAW_API_KEY. One ambiguity: Python snippets call api.get(...) without shipping an SDK or explaining how 'api' is provided — this is a documentation gap but not malicious. No instructions request reading local files, other env vars, or sending data to third-party endpoints.
Install Mechanism
No install spec and no code files — instruction-only skill. This minimizes disk writes and third-party package installations (low install risk).
Credentials
Only CLAW_API_KEY is required and declared as the primary credential; this is proportionate for an API-based analytics skill. The SKILL.md references Stripe verification as a store-side condition but does not request Stripe secrets (which is appropriate).
Persistence & Privilege
Skill does not request always:true, does not modify other skills or system config, and is user-invocable only. It does not request persistent system privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install clawver-store-analytics
  3. After installation, invoke the skill by name or use /clawver-store-analytics
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
- Added Stripe verification prerequirement for store public listings. - Clarified key metric definitions, especially for revenue and page views. - Updated API status values for orders (use confirmed instead of paid). - Improved review example response schema. - Linked to new API pattern examples in references/api-examples.md.
v1.0.0
Initial release of Clawver Store Analytics. - Provides analytics on revenue, orders, top products, conversion rates, and store growth trends. - Supports querying data by time period (7d, 30d, 90d, all). - Delivers detailed product-level statistics and review analytics. - Outlines actionable insights for sales performance improvement. - Includes example API requests and response structures for easy integration.
Metadata
Slug clawver-store-analytics
Version 1.0.1
License
All-time Installs 7
Active Installs 7
Total Versions 2
Frequently Asked Questions

What is Clawver Store Analytics?

Monitor Clawver store performance. Query revenue, top products, conversion rates, growth trends. Use when asked about sales data, store metrics, performance reports, or business analytics. It is an AI Agent Skill for Claude Code / OpenClaw, with 1923 downloads so far.

How do I install Clawver Store Analytics?

Run "/install clawver-store-analytics" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Clawver Store Analytics free?

Yes, Clawver Store Analytics is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Clawver Store Analytics support?

Clawver Store Analytics is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Clawver Store Analytics?

It is built and maintained by nwang783 (@nwang783); the current version is v1.0.1.

💬 Comments