SkillVaultskills Browse all 500 skills

Data · Version 1.4.0 · Reviewed 2026-08-02

Time Series Storage Advisor

Make data systems more correct and operable for cardinality control and downsampling policy with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Designs retention, downsampling, cardinality control, and query patterns for time-series workloads.

₹149 one-time

Get this skill archive

What this skill helps you do

  • Cardinality control
  • Downsampling policy
  • Retention tiering

How Time Series Storage Advisor works

You provide

Schema, volumes, and the queries that actually run

It inspects

Access patterns and skew affecting cardinality control

It decides

A downsampling policy design with migration ordering

You verify

Row counts and checksums compared before cutover

What it checks first

Time Series Storage Advisor designs retention, downsampling, cardinality control, and query patterns for time-series workloads. Use it when the work involves Cardinality control, Downsampling policy, Retention tiering.

  1. The real access patterns, since schema quality is meaningless without the queries it serves.
  2. Cardinality, skew, and growth rate of the key columns.
  3. Consistency and freshness requirements per consumer.
  4. Whether the model preserves history or overwrites it, which determines what questions remain answerable.

Failure modes it recognizes

  • A schema optimized for writes that makes the dominant read pattern a full scan.
  • Skewed partitioning concentrating load on one node.
  • Nullable columns encoding several meanings, making every downstream query ambiguous.
  • A pipeline silently dropping late-arriving records and under-reporting totals.

Answers it will reject

  • Normalizing or denormalizing by preference rather than by measured access pattern.
  • Adding a column for each new requirement until the table encodes multiple entities.
  • Backfilling without a reconciliation check that proves completeness.

Decision rules it applies

  • Design from the read path backward for read-heavy systems.
  • Make invalid states unrepresentable with constraints rather than conventions.
  • Version the schema and treat consumer compatibility as a contract.

Evidence it asks for

  • Profile real query patterns and volumes before proposing a change.
  • Validate migrations with row counts, checksums, and spot comparisons.
  • Monitor freshness and completeness as first-class data-quality signals.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to cardinality control.
  2. Trace concrete failure or abuse paths for downsampling policy; do not report checklist items without a mechanism.
  3. Prioritize retention tiering findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Cardinality control assessment
  • Downsampling policy decision and action plan
  • Retention tiering verification checklist

Evidence requirements

  • Schema, access patterns, query plans, or event contracts
  • Volume, cardinality, retention, and freshness
  • Consistency, latency, and migration constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Our metrics store keeps running out of memory and we recently added a customer ID label to every metric.

Expected output

A customer ID label multiplies series count by your customer count, which is almost always the cause of this failure. Remove unbounded dimensions from metrics and move per-customer questions to logs or an analytical store designed for high cardinality...

Boundaries and compatibility

Ideal for

  • Cardinality control: produce a decision or artifact grounded in supplied evidence.
  • Downsampling policy: produce a decision or artifact grounded in supplied evidence.
  • Retention tiering: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Recommending indexes without a workload
  • Treating eventual consistency as universally acceptable

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.