← ClaudeAtlas

iblai-vibe-monetization-analyticslisted

Build custom Platform analytics surfaces — revenue dashboards, subscriber lists, paywalls overview, and a self-service subscription cancel helper on top of ibl.ai's item monetization. The in-tab MonetizationTab does NOT render revenue or subscriber data today, so these hooks are the building blocks for custom dashboards, leaderboards, and admin tools. Use when the user mentions analytics, revenue, subscribers, sales volume, sales count, commission, dashboard, paywalls list, cancel subscription, or "monetization metrics". See /iblai-vibe-monetization for the family index, /iblai-vibe-monetization-onboard for Stripe Connect status + commission, /iblai-vibe-monetization-configure for paywall setup, /iblai-vibe-monetization-subscription for the user-side counterpart, /iblai-vibe-auth for token wiring, and /iblai-vibe-rbac for the IsPlatformAdmin gate.
iblai/vibe · ★ 15 · AI & Automation · score 76
Install: claude install-skill iblai/vibe
# /iblai-vibe-monetization-analytics Build custom Platform admin surfaces on top of the four monetization analytics endpoints — revenue, all-Platform subscribers, per-item subscribers, paywalls list — plus the `CancelSubscription` self-service helper that cancels the **caller's own** subscription on a given `(item_type, item_id)`. > **A true admin override (cancel-on-behalf-of-user) does not exist.** > The cancel endpoint is hard-locked to `request.user`; there is no > `user_id` parameter. To force-cancel another user's subscription, an > operator must do so directly in the Stripe Dashboard. > **Important:** `MonetizationTab` (see `/iblai-vibe-monetization-configure`) > does NOT render revenue or subscriber data. The SDK ships the > data-layer hooks and one self-service component, but no out-of-the-box > analytics UI — this skill is the playbook for assembling that yourself. Do NOT add custom styles, colors, or CSS overrides to ibl.ai SDK components. They ship with their own styling. Keep the components as-is. Do NOT implement dark mode unless the user explicitly asks for it. When building custom UI around SDK components, use the ibl.ai brand: - **Primary**: `#0058cc`, **Gradient**: `linear-gradient(135deg, #00b0ef, #0058cc)` - **Button**: `bg-gradient-to-r from-[#2563EB] to-[#93C5FD] text-white` - **Font**: System sans-serif stack, **Style**: shadcn/ui new-york variant - Follow the component hierarchy: use ibl.ai SDK components (`@iblai/iblai-js`) first, then shadcn/u