agentsclimarketplace

Techtide alibaba analyticdb realtime

Skill TechTideOhio/techtide-harness-kit/skills/alibaba/techtide-alibaba-analyticdb-realtime

Trust contracts for AI agent skills: JSON Schema risk tiers, tool permissions, deny-by-default egress, approval gates, prompt-injection fixtures, ~28 CI validation gates. Apache-2.0.

Install
npx -y skills add TechTideOhio/techtide-harness-kit --skill techtide-alibaba-analyticdb-realtime

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Operate AnalyticDB for MySQL and PostgreSQL, Hologres real-time OLAP analytics, and DAS real-time diagnostics for sub-second interactive analytics workloads.

SKILL.md

3.6 KB, 654 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it: 3 files

3.2 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most databases sql skills give in 654 tokens

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-07

  • Use parameterized queriesin 37 of 589, across 34 files
  • Use timestamptz for timestampsin 30 of 589, across 14 files
  • Index foreign keysin 29 of 589, across 18 files
  • Create indexes concurrentlyin 29 of 589, across 24 files
  • Use numeric type for moneyin 25 of 589, across 8 files
  • Use cursor pagination instead of offsetin 24 of 589, across 17 files
  • Select only required columnsin 24 of 589, across 20 files
  • Add indexes manually on foreign key columnsin 22 of 589, across 12 files
  • Normalize to third normal formin 19 of 589, across 10 files
  • Configure connection poolingin 19 of 589, across 17 files
  • Put equality columns before range columns in indexesin 18 of 589, across 10 files
  • Read individual rule files for detailed explanationsin 18 of 589, across 4 files

Said here and by no other author read

  • do not conflate analyticdb and hologres billing models
  • keep answers scoped, reversible, and explicit about trade-offs
  • return the safest next actions with validation steps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 327,069. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.