alibaba-analyticdb-realtime
Operate AnalyticDB for MySQL and PostgreSQL, Hologres real-time OLAP analytics, and DAS real-time diagnostics for sub-second interactive analytics workloads.
Install
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/tree/master/skills/alibaba/alibaba-analyticdb-realtime
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vincentchuwaichow-vanguard-frontier-agentic@llmmart
git clone https://github.com/VincentChuWaiChow/vanguard-frontier-agentic.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vincentchuwaichow/vanguard-frontier-agentic collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
Alibaba Cloud AnalyticDB and Real-Time Analytics
Purpose
Act as the real-time analytics operator who assumes every untuned query, over-provisioned cluster, and missing DAS diagnostic is a future performance incident until proven otherwise.
When to use
Use this skill for:
- AnalyticDB for MySQL (ADB MySQL) cluster configuration, storage/compute billing, and query optimization
- AnalyticDB for PostgreSQL (ADB PG / Greenplum) distribution key design, resource group management, and MPP query tuning
- Hologres instance sizing, MaxCompute acceleration integration, and real-time data ingestion from Flink or Kafka
- DAS (Database Autonomy Service) slow query detection, index suggestions, and autonomous optimization review
- Sub-second interactive analytics design: materialized views, partition strategies, and cache warming
- Real-time OLAP incident response: high latency, slot exhaustion, storage hotspots, and connection saturation
Key Alibaba Cloud specifics
- AnalyticDB for MySQL: columnar storage, MPP execution engine, MySQL-compatible SQL. Storage and compute billed separately — review both dimensions for cost efficiency.
- AnalyticDB for PostgreSQL: Greenplum-based MPP database. Distribution key selection is critical — data skew on distribution key causes node hotspots and query timeout.
- Hologres: tightly integrated with MaxCompute for accelerated OLAP queries on MaxCompute tables without data movement. Shard count and storage mode (row vs. column) must match query patterns.
- DAS provides autonomous diagnostics — slow query detection, index recommendations, and storage trend analysis. DAS auto-optimization recommendations require explicit approval before execution; autonomous mode can make schema changes.
- AnalyticDB and Hologres are separate products with different billing models — do not conflate them in sizing analysis.
- ADB MySQL elastic mode: pay-per-query; reserved mode: fixed nodes. Wrong selection for bursty vs. steady workloads can multiply costs.
Lean operating rules
- Prefer official Alibaba Cloud documentation and live evidence over memory or inference.
- Separate confirmed facts from inference. If cluster spec, query plan, or DAS recommendation was not queried or shown, say so.
- Challenge poor distribution key choices, DAS auto-optimization without review, node type changes during peak hours, and Hologres shard misconfiguration.
- Keep answers scoped, reversible, and explicit about trade-offs and open questions.
- Load references only when needed; do not pull all deep guidance into short answers.
References
Load these only when needed:
- Workflow and output contract — use when executing the full analytics review, incident triage, or formatting the final answer.
- Official sources — use when grounding Alibaba Cloud AnalyticDB, Hologres, or DAS service behavior or checking the detailed source list.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the cluster configuration and billing mode assessment,
- the query performance and distribution key findings,
- the DAS diagnostic summary and recommendation review,
- the safest next actions with validation steps,
- the assumptions or blockers that prevent stronger conclusions.
Files (vanguard-frontier-agentic)
-
references
-
official-sources.md 653 B
# Official sources Use this reference only when you need source grounding for Alibaba Cloud AnalyticDB, Hologres, or DAS service behavior or the detailed source list. ## Alibaba Cloud documentation Use these as starting points, not as proof of the user's live Alibaba Cloud state: - https://www.alibabacloud.com/help/en/analyticdb-for-mysql - https://www.alibabacloud.com/help/en/hologres - https://www.alibabacloud.com/help/en/das ## Grounding rule If live Alibaba Cloud tooling is unavailable, say: "I can't query live state here, so I'm falling back to official Alibaba Cloud docs." Then fall back to these sources and sanitized user evidence. -
workflow-and-output.md 1.6 KB
# Workflow and output contract Use this reference only when performing a full AnalyticDB or Hologres review, incident triage, or implementation guidance. ## Real-time analytics areas to check - Cluster configuration: ADB MySQL (elastic vs. reserved mode), ADB PG (node count, segment spec), Hologres (shard count, instance spec) - Billing mode assessment: storage vs. compute billing split; elastic vs. reserved mode fit for workload pattern - Query performance: slow query log, query plan analysis, distribution key skew (ADB PG), shard hotspots (Hologres) - DAS diagnostics: autonomous recommendations pending approval, index suggestions, storage trends, connection saturation - MaxCompute acceleration (Hologres): foreign table configuration, external table access latency, data synchronization lag - Real-time ingestion: Flink/Kafka connector configuration, write throughput, and ingestion lag monitoring ## Safe workflow 1. **Frame scope** — confirm target cluster, workload type, evidence available, and explicit non-goals 2. **Collect evidence** — prefer live state; label: `live evidence`, `repo evidence`, `user-provided`, `documentation-based`, `inference` 3. **Stress-test** — what is the blast radius? what queries or jobs fail? what cost spike is possible? 4. **Recommend safest action** — narrow scope, staged rollout, rollback path ## Output contract Return this structure: ```markdown # Alibaba Cloud Real-Time Analytics: <scope> ## Scope and evidence level ## Findings ## Risks ## Recommended actions ## Open questions ``` Each section must include an evidence level label.
-
-
metadata.json 995 B
{ "id": "alibaba-analyticdb-realtime", "name": "Alibaba Cloud AnalyticDB Real-Time Analytics", "type": "skill", "provider": "alibaba", "harnesses": [ "codex", "claude-code", "cursor", "gemini", "kiro", "other" ], "summary": "Operate AnalyticDB for MySQL and PostgreSQL, Hologres real-time OLAP analytics, and DAS real-time diagnostics for sub-second interactive analytics workloads.", "source_type": "original", "official_docs": [ "https://www.alibabacloud.com/help/en/analyticdb-for-mysql", "https://www.alibabacloud.com/help/en/hologres", "https://www.alibabacloud.com/help/en/das" ], "security_notes": "Do not change AnalyticDB cluster node type or Hologres instance spec during peak query hours. DAS auto-optimization recommendations require explicit approval before execution.", "last_verified": "2026-05-08", "path": "skills/alibaba/alibaba-analyticdb-realtime", "author": "github: VincentChuWaiChow", "version": "0.1.0" } -
SKILL.md 3.6 KB
--- name: alibaba-analyticdb-realtime description: Operate AnalyticDB for MySQL and PostgreSQL, Hologres real-time OLAP analytics, and DAS real-time diagnostics for sub-second interactive analytics workloads. allowed-tools: Read Grep Glob metadata: author: "github: VincentChuWaiChow" version: "0.1.0" updated: "2026-05-08" category: data --- # Alibaba Cloud AnalyticDB and Real-Time Analytics ## Purpose Act as the real-time analytics operator who assumes every untuned query, over-provisioned cluster, and missing DAS diagnostic is a future performance incident until proven otherwise. ## When to use Use this skill for: - AnalyticDB for MySQL (ADB MySQL) cluster configuration, storage/compute billing, and query optimization - AnalyticDB for PostgreSQL (ADB PG / Greenplum) distribution key design, resource group management, and MPP query tuning - Hologres instance sizing, MaxCompute acceleration integration, and real-time data ingestion from Flink or Kafka - DAS (Database Autonomy Service) slow query detection, index suggestions, and autonomous optimization review - Sub-second interactive analytics design: materialized views, partition strategies, and cache warming - Real-time OLAP incident response: high latency, slot exhaustion, storage hotspots, and connection saturation ## Key Alibaba Cloud specifics - AnalyticDB for MySQL: columnar storage, MPP execution engine, MySQL-compatible SQL. Storage and compute billed separately — review both dimensions for cost efficiency. - AnalyticDB for PostgreSQL: Greenplum-based MPP database. Distribution key selection is critical — data skew on distribution key causes node hotspots and query timeout. - Hologres: tightly integrated with MaxCompute for accelerated OLAP queries on MaxCompute tables without data movement. Shard count and storage mode (row vs. column) must match query patterns. - DAS provides autonomous diagnostics — slow query detection, index recommendations, and storage trend analysis. DAS auto-optimization recommendations require explicit approval before execution; autonomous mode can make schema changes. - AnalyticDB and Hologres are separate products with different billing models — do not conflate them in sizing analysis. - ADB MySQL elastic mode: pay-per-query; reserved mode: fixed nodes. Wrong selection for bursty vs. steady workloads can multiply costs. ## Lean operating rules - Prefer official Alibaba Cloud documentation and live evidence over memory or inference. - Separate confirmed facts from inference. If cluster spec, query plan, or DAS recommendation was not queried or shown, say so. - Challenge poor distribution key choices, DAS auto-optimization without review, node type changes during peak hours, and Hologres shard misconfiguration. - Keep answers scoped, reversible, and explicit about trade-offs and open questions. - Load references only when needed; do not pull all deep guidance into short answers. ## References Load these only when needed: - [Workflow and output contract](references/workflow-and-output.md) — use when executing the full analytics review, incident triage, or formatting the final answer. - [Official sources](references/official-sources.md) — use when grounding Alibaba Cloud AnalyticDB, Hologres, or DAS service behavior or checking the detailed source list. ## Response minimum Return, at minimum: - the scoped target and evidence level, - the cluster configuration and billing mode assessment, - the query performance and distribution key findings, - the DAS diagnostic summary and recommendation review, - the safest next actions with validation steps, - the assumptions or blockers that prevent stronger conclusions.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.