From altertable
Analyzes web analytics traffic patterns and user behavior using the Altertable MCP server. Queries pageviews, sessions, traffic sources, and segments data to surface trends and anomalies.
How this skill is triggered — by the user, by Claude, or both
Slash command
/altertable:analyzing-web-trafficThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
To analyze web traffic:
To analyze web traffic:
Ask the user (or infer from context):
Use Altertable MCP tools to fetch web analytics data:
get_catalog to confirm the Product Analytics tables and columns available in this environmentquery_lakehouse for custom web traffic analysisrender_insight when the user wants a chart previewCommon Product Analytics tables include product_analytics.analytics.web_sessions and product_analytics.analytics.web_pageviews. Query them to compute:
Always pull both the current period and the comparison period so you can compute deltas.
Break down by at least one dimension to find where changes originate:
When a top-level metric moves, drill into segments to isolate which segment drove the change.
Look for:
Quantify every observation with absolute numbers and percentage change.
Present findings with:
| Comparison | When to Use |
|---|---|
| WoW (week-over-week) | Short-term monitoring, recent changes |
| MoM (month-over-month) | Growth tracking, campaign evaluation |
| YoY (year-over-year) | Seasonal businesses, long-term trends |
Always compare equal-length periods. When comparing WoW, align on the same day of week. When comparing MoM, account for differing month lengths.
When the user does not specify a segment, default to this order:
Only add geography or other dimensions if the first pass does not explain the change.
npx claudepluginhub altertable-ai/skills --plugin altertableMines projects and conversations into a searchable memory palace. Activates on queries about MemPalace, memory palace, mining, searching, palace setup, wings, rooms, drawers, or recalling past work.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.