- Home
- /
- Categories
- /
- Analytics
Analytics
Data analysis and visualization
mcp-server
by hoangsonww
Configure, launch, validate, and troubleshoot CCAM's comprehensive MCP server for Claude Code, Codex, and other MCP hosts. Use when installing dependencies, building the server, selecting stdio, HTTP, or REPL transport, setting mutation/destructive policy, supplying dashboard authentication, or checking complete tool registration.
deepwork-tracker
by adunne09
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
recharts-patterns
by zhongjis
Data visualization patterns using Recharts 3.x - a composable charting library built with React and D3. Use when creating charts, dashboards, or data visualizations in React applications.
we-together
by yellowpeachxgp
"Build and run a small social graph of digital people with scenes, events, memories, relations, and evolving state. 构建并运行一个由人物、关系、场景、事件、记忆与状态组成的小型数字社会图谱。"
session-cleanup
by hoangsonww
Identify stale and empty Claude Code sessions in the Agent Monitor and explain the cleanup endpoint (POST /api/settings/cleanup), always showing the exact list of what WOULD be removed before anything is deleted. Cleanup permanently deletes data, so this skill previews first and requires explicit user confirmation. Use when tidying the monitoring database.
grafana
by kontrolplane
Grafana dashboard JSON configuration and alerting. Use when creating or editing dashboard JSON, configuring panels programmatically, setting up Grafana alerting rules, or troubleshooting visualization issues.
flow-graph
by asgeirf
Generate animated GIF/WebM videos of graph visualizations from natural language descriptions
gingiris-seo-geo-agent
by Gingiris-1031
SEO/GEO Agent Operations SOP v2 — Rebuilt from real-world operations (analook.com 0→launch, GSC incident, DataForSEO monitoring, gingiris.tools post-migration recovery). What's new in v2: • Step-by-step onboarding (Q1→Q6), multiple choice wherever possible — no big forms • Mandatory daily SEO log — first item is always GSC token status check • Data cross-validation rule: any external metric must come from ≥2 sources before use • Backlink progress tracking (6-week wait → check → alert if not indexed) • New vs. established site strategy matrix (new site <6mo: KD≤20; mature: KD up to 35+) Real incidents baked in: GSC token expired silently for 2 weeks (analook.com), P0 keywords dropped out of Top 100 after domain migration (gingiris.tools), traffic data off by 17× from single-source DataForSEO. Triggers: "SEO agent" "SEO daily report" "GSC monitoring" "DataForSEO" "GEO agent" "backlink tracking" "IndexNow" "competitor comparison page" "SEO SOP" "autonomous SEO" "GEO triple combo" 🇨🇳 SEO/GEO Agent 运营 SOP v2 — 基于真实运营经验重写(analook.com 从零建站 + GSC 断档 2 周 + DataForSEO 监控 + gingiris.tools 迁移权重恢复)。 对话式开局、强制日报(GSC token 是第一项)、数据交叉验证铁律、外链进度追踪、新老站区分策略。
geo-knowledge
by yaojingang
Build and query an evidence-lined GEO knowledge graph from approved source bundles. Use for entity normalization, relation lineage, conflicting fact preservation, incremental source-hash updates, local/global knowledge queries, 知识图谱, 知识库, and 知识治理. Exclude unsourced facts, hidden conflict resolution, autonomous crawling, and external database mutation.
progress-report
by lahfir
'Generate polished, stakeholder-ready progress reports as PDF documents. Automatically gathers project metrics (LOC, files, tests, commits, tables), takes live dashboard screenshots via agent-browser, builds a styled HTML report, and converts to PDF. Supports three report scopes: (1) full project report covering all phases and architecture, (2) feature/phase report focused on current branch work, (3) sprint/weekly report summarizing recent activity. Use when the user asks for: "progress report", "stakeholder report", "project status PDF", "engineering summary", "create a report", "generate a PDF report", "feature report", "sprint summary", "what have we built", or any request to document project progress as a deliverable.'
dashboard-builder
by affaan-m
Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.
code-review
by nu1nux
Review code changes for quality, security, and best practices; save report to docs/reviews/
virtu-market-microstructure
by copyleftdev
Build trading systems in the style of Virtu Financial, the leading electronic market maker and execution services firm. Emphasizes market microstructure, optimal execution, order routing, and minimizing market impact. Use when building execution algorithms, smart order routers, or analyzing market microstructure.
openfate-bazi
by openfate-ai
Use this skill for Bazi / Four Pillars, BaZi compatibility, True Solar Time, Ten Gods, Da Yun luck cycles, lunar-to-solar conversion, and Earthly Branch interactions with OpenFate Bazi MCP. 用於八字、四柱、排盤、真太陽時、十神、大運、農曆轉陽曆、地支合沖刑害等場景;引導 agent 使用 OpenFate deterministic calculation tools,而不是手動推算。
business-outcomes-advisor
by gracebotly
Fast opinionated revenue strategy for AI automation agencies building workflow dashboards. Frames proposals through monetization lenses during propose phase. Use when user is selecting entities, choosing outcomes, or evaluating dashboard proposals. Max 1-2 questions, plain language, agency-native vocabulary.
project-understanding
by evil-skills
Use when you need a fast, reliable architecture or impact view in a large unfamiliar repo, especially under time pressure or tight context budgets where manual grep or folder inference would be risky.
omni-autonomous-agent (OAA)
by omnious0o0
Makes an AI agent autonomous and able to work for a long time, or a fixed duration without interruptions. Use this skill when the user asks you to work autonomously (e.g., "Work overnight," "I'll be gone for a few hours, work on this," "keep working on this until it's done," etc.). Basically any task that could take longer than usual. (3+ minutes)
hivemind-graph
by activeloopai
Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of changing this?". The graph is an AST-derived map of the repo, queried as files (no build needed — it rebuilds automatically).
rust-daily
by lywa1998
CRITICAL: Use for Rust news and daily/weekly/monthly reports. Triggers on: rust news, rust daily, rust weekly, TWIR, rust blog, Rust 日报, Rust 周报, Rust 新闻, Rust 动态
event-trace
by hoangsonww
Trace the full event chain for one Claude Code session into an ordered timeline of every event type with tool_name and summary, highlighting gaps, out-of-order events, and failures. Reads /api/events?session_id= and /api/sessions/:id from the Agent Monitor dashboard. Use when debugging what a session actually did, step by step.
slo-check
by hoangsonww
Define and check simple service-level objectives for Claude Code from Agent Monitor data — session completion rate, tool success rate (PostToolUse/PreToolUse), and error rate (APIError/total) — then compare each to its target and report the error budget remaining. Use when reporting reliability or when someone asks "are we meeting our SLOs?".
loop-paper
by youndukn
Use when running substantial work as a hypothesis-first paper loop — initializing a project-local .paper-stack, creating or closing a closed-loop paper, validating before/after gates, combining paper intervals, or ranking reference papers.
helm-chart-scaffolding
by TriNgo0108
Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.
Skill: Pull Funnel Data
by IgorGanapolsky
Purchase count double-counts: verify success-page code does not emit Checkout Pro Purchase Completed; only the webhook should emit that canonical purchase event.