timescaledb

TimescaleDB PostgreSQL for time-series. Use for time-series on Postgres.

7 stars

Best use case

timescaledb is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

TimescaleDB PostgreSQL for time-series. Use for time-series on Postgres.

Teams using timescaledb should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/timescaledb/SKILL.md --create-dirs "https://raw.githubusercontent.com/G1Joshi/Agent-Skills/main/skills/databases/timescaledb/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/timescaledb/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How timescaledb Compares

Feature / AgenttimescaledbStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

TimescaleDB PostgreSQL for time-series. Use for time-series on Postgres.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# TimescaleDB

TimescaleDB is a time-series database built as an extension on top of PostgreSQL. It gives you the scale of NoSQL time-series with the reliability and tooling of Postgres.

## When to Use

- **SQL familiarity**: You want time-series but already know SQL and use Postgres drivers.
- **Relational + Time**: You need to JOIN your sensor data (Time Series) with Device metadata (Relational Tables).
- **Compression**: Highest-in-class compression (90%+) for historical data.

## Quick Start

```sql
-- Convert standard table to hypertable
SELECT create_hypertable('conditions', 'time');

-- Query using standard SQL time-bucket functions
SELECT time_bucket('15 minutes', time) AS bucket,
       avg(temperature)
FROM conditions
GROUP BY bucket
ORDER BY bucket DESC;
```

## Core Concepts

### Hypertables

The abstraction layer. It looks like a single table, but effectively partitions data into chunks by time interval.

### Continuous Aggregates

Real-time materialized views. "Keep a running average of temperature per hour". It updates incrementally.

### Compression

Columnar compression on old chunks. Turns row-based Postgres pages into highly compressed columnar arrays.

## Best Practices (2025)

**Do**:

- **Enable Compression**: It improves query speed (less I/O) and saves massive disk space.
- **Use Tiered Storage**: Keep recent hot data on SSD, move compressed old data to S3 (Bottomless storage in cloud).
- **Join tables**: Use the power of Postgres to join your metrics with your business data.

**Don't**:

- **Don't update compressed chunks**: Updating old, compressed data is slow (Copy-on-write). Design for append-only patterns.

## References

- [TimescaleDB Documentation](https://docs.timescale.com/)