timescale

Use this skill when writing analytical SQL over time-series data with the TimescaleDB Toolkit (timescaledb_toolkit extension) hyperfunctions: approximate percentiles, statistical summaries, time-weighted averages, counter/gauge rates, uptime/heartbeat…

Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. **Trigger when user asks to:** - Explore an existing PostgreSQL database to understand its…

Explore an existing PostgreSQL database before answering questions about its data or writing SQL. Use this skill whenever a user asks for a query or a data-backed answer against an unfamiliar schema (counts, missing or failed records, recent changes), asks…

Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. **Trigger when user asks to:** - Test a schema migration before applying it to production - Add,…

Comprehensive PostGIS spatial table design reference covering geometry types, coordinate systems, spatial indexing, and performance patterns for location-based applications

Use this skill for general PostgreSQL table design. **Trigger when user asks to:** - Design PostgreSQL tables, schemas, or data models when creating new tables and when modifying existing ones. - Choose data types, constraints, or indexes for PostgreSQL -…

Use this skill to analyze an existing PostgreSQL database and identify which tables should be converted to Timescale/TimescaleDB hypertables. **Trigger when user asks to:** - Analyze database tables for hypertable conversion potential - Identify time-series…

Use this skill to migrate identified PostgreSQL tables to Timescale/TimescaleDB hypertables with optimal configuration and validation. **Trigger when user asks to:** - Migrate or convert PostgreSQL tables to hypertables - Execute hypertable migration with…

This repo's general git conventions — starting a branch or worktree, committing as you go, hooks, addressing review feedback, and cleaning up after merge. Trigger when the user wants to start new work, begin a feature/bugfix/refactor, or clean up after a PR…

Prepare and open a pull request end to end — pre-commit checks, a Conventional Commits commit, rebase, push, and a `gh pr create` body matching this repo's style. Trigger when the user asks to commit and open a PR, ship a branch, or "create a PR".

Drive a release from cut to finished: cut the PR with scripts/prepare-release.sh, fill the changelog, open the PR with the script that run wrote, then after a human merges it, watch release.yml publish, check the tag and assets, and see the development-cycle…

How to profile this repo with perf and flame graphs — release builds only, scripts/profile.sh and scripts/profile-bench.sh, where output lands, and how to read it. Trigger when asked to profile, find a hot path, check a performance regression, or validate…

This repo's review checklist — reviewing a plan before implementation, and adversarially reviewing a finished branch's diff before opening a PR. Used by `build-feature`. Trigger when asked to review a plan, or to adversarially review a branch/diff for…

Which of this repo's four test kinds to use for a change, where new tests belong, coverage expectations, and gotchas that produce false-positive passes. Trigger when writing tests for new or changed code, or judging whether coverage of a change is adequate.

Adversarial security review of the extensions: the install script, the pgvector compat path, the event trigger, casts, and SQL-callable functions, and the C-code side. Carries the search_path / privilege-escalation threat model, a per-object checklist, pgspot…

End-to-end workflow for a new feature: branch, plan, review the plan, implement, adversarially review the finished branch, then open a PR. Trigger when the user asks to build, implement, or ship a new feature end to end rather than make a small isolated…

Draft or update the <TestPlan> block on a docs page for the doc-testing tool. Use when a page needs a test plan, when a page's procedure changed and its plan is stale, or when asked to "write a test plan" or "make this page testable".

Write a tutorial for the Tiger Data Docs site following established conventions. Use when creating a new tutorial, cookbook, or step-by-step guide for the /learn/tutorials section — especially for database, search, AI, or data engineering topics.

Run this repo's checks (build, prose lint) and open a draft PR using the repo's PR template. Use when the user says "create a PR", "open a PR", "let's PR this", "submit this", or any variation of wanting to submit doc changes for review.

Pull recent content from Tiger Den (Tiger Data's marketing content hub), match it to docs pages, and draft learnMore right-rail cards on a review branch. Use for the recurring "add new external links to the docs" task, or when asked to refresh learnMore cards…

Write an integration guide for the Tiger Data Docs site following established conventions. Use when documenting how to connect a third-party tool (database client, BI tool, streaming platform, observability stack, ETL connector, etc.) to Tiger Cloud or…

Apply the constants from src/constants.ts to a docs page — scan the page, swap every literal that matches a constant value (PostgreSQL, Tiger Cloud, TimescaleDB, hypertable, chunk, columnstore, service, and so on) for its {C.X} constant in the correct MDX/JSX…

Update workflow implementation from its embedded description. Use this after modifying workflow or node descriptions.

Collaborative workflow design - guides users through creating well-structured crayon workflows with embedded descriptions.

Generate integration nodes for external APIs (Salesforce, HubSpot, etc.). Creates typed function nodes with authentication and error handling.

Refine node definitions - determines HOW each node is implemented (SDKs, libraries, input/output structures, tools, guidelines).

How to trigger workflows and nodes. Covers MCP tools (run_workflow, run_node), HTTP webhooks (async/sync), authentication, and cron scheduling.

This skill lives in a dot-prefixed directory and must never be loaded by the local_collection loader.

First collection skill

Second collection skill

First test skill

Second test skill

End-to-end workflow for a new feature: branch, plan, review the plan, implement, adversarially review the finished branch, then open a PR. Trigger when the user asks to build, implement, or ship a new feature end to end rather than make a small isolated…

This repo's review checklist — reviewing a plan before implementation, and adversarially reviewing a finished branch's diff before opening a PR. Used by `build-feature`. Trigger when asked to review a plan, or to adversarially review a branch/diff for…

Prepare and open a pull request end to end — pre-commit checks, a Conventional Commits commit, rebase, push, and a `gh pr create` body matching this repo's style. Trigger when the user asks to commit and open a PR, ship a branch, or "create a PR".

This repo's general git conventions — starting a branch, committing as you go, hooks, commit messages, addressing review feedback, and cleaning up after merge. Trigger when the user wants to start new work, begin a feature/bugfix/refactor, or clean up after a…

Which of this repo's test kinds to use for a change, where new tests belong, what needs a live PostgreSQL, and the gotchas that produce false-positive passes. Trigger when writing tests for new or changed code, or judging whether coverage of a change is…

Run unit tests for one or all collection clients and report results

Static review of collection-client code against the UNS data contract in CLAUDE.md

Run end-to-end pipeline validation — query TimescaleDB after collection and report

Validate that a tutorial follows the write-tutorial format and that all code runs correctly. Use when reviewing, finalizing, or QA-ing a cookbook/tutorial before shipping. Checks README structure, file completeness, code runnability, and consistency.

Write a consistent, step-by-step technical tutorial. Use when creating a new cookbook, guide, or walkthrough — especially for database, search, or data engineering topics. Produces a README, supporting scripts, and a setup file following a proven structure.

Design a forecast store schema on Postgres/TimescaleDB — the tables, keys, defaults, and queries for storing forecasts with leakage-free backtesting, reproducible evaluation, and vintage history. Use when asked to store forecasts/predictions, backtest without…

Provision and operate a forecast store (the forecast-store convention) on Postgres/TimescaleDB — generate/apply the schema, register series, and run the canonical as-of and evaluation queries. Use for any work against a forecast store in this repo, including…

How to discover, read, write, and search data in a TigerFS-mounted PostgreSQL database using file tools.

Use the rsigma CLI and MCP server: engine eval, engine daemon, rule lint, rule draft, rule tune, rule backtest, backend convert, mcp serve. Prefer MCP tools when rsigma mcp serve is connected. For authoring Sigma YAML (detection, correlation, filters,…

Prepare, tag, publish, and verify stable releases of the searchgres core npm package. Use when asked to bump the searchgres version, create a release PR, continue a release after merge, push a vX.Y.Z tag, monitor the npm trusted-publishing workflow,…