Skip to content

altertable-ai/skills / plugins/altertable/skills/ingest-data

ingest-data

Unverified

Loads data into Altertable through the CLI, HTTP API, DataFrame tooling, object storage, or generated pipelines. Use for file upload, append, upsert, overwrite, bucket synchronization, or deciding between ingestion and an external catalog.

Ingest Data

Choose the ingestion path based on where the data lives, whether it must be copied, and how the workflow will run. Read current instructions with search_docs when the Altertable MCP server is available; otherwise use Ingest data.

Choose the Path

SituationPreferred path
Local CSV, JSON, or Parquet fileCLI upload
Event-style JSON object or batchCLI or HTTP append
File matched to existing rows by primary keyCLI or HTTP upsert
Pandas, Polars, or Ibis data already in memoryDataFrame integration through DuckDB
Files continuously arriving in object storageBucket synchronizer
Repeatable extraction and loading from a sourceGenerated or maintained dlt pipeline
Existing database, warehouse, or object catalog should stay in placeExternal catalog; query it without copying

Prefer the Altertable CLI for terminal scripts and CI because profiles handle authentication and --agent provides structured output. If the CLI is missing, follow the conditional setup in use-altertable. See the CLI guide for installation and authentication, and the CLI repository for releases and the complete command contract.

Prefer the HTTP API for application-controlled ingestion. Use an SDK when it already handles retries, batching, and the relevant data structure.

Write Semantics

  • append adds records and can create or evolve an event-style destination according to the current API behavior.
  • upload --mode create creates a destination from a file.
  • upload --mode append adds file rows to an existing table.
  • upload --mode overwrite replaces table contents; use it only when replacement is explicit.
  • upsert matches existing rows by the supplied primary key and requires a stable, unique key.

Inspect the current CLI help or API schema before constructing a request. Do not guess flags, payload limits, supported formats, or asynchronous behavior from an old example.

Workflow

  1. Confirm the organization, environment, destination catalog.schema.table, source format, expected row count, and desired write semantics.
  2. Inspect the existing destination schema when it exists. Check names, types, nullability, primary-key suitability, and column ordering behavior.
  3. Decide whether federation through an external catalog is preferable to copying the data.
  4. Execute the smallest bounded write. Never expose credentials in commands, logs, or chat.
  5. For asynchronous append, upload, upsert, synchronization, or pipeline work, poll the returned job or task identifier until terminal state.
  6. Verify row counts, schema, representative non-sensitive values, and duplicate behavior with a bounded query.

When generating a dlt workflow, use the documented generate_dlt_pipeline tool if available, inspect its output, request secrets through the platform's secret flow, and test against a non-production destination first.

Guardrails

  • Do not infer overwrite intent from “refresh,” “reload,” or a filename collision.
  • Do not use mutable business attributes as an upsert key.
  • Do not load sensitive fields merely because they exist in the source.
  • Keep large writes in batches that fit current transaction and memory limits.
  • Preserve source timestamps and stable identifiers needed for idempotency.
  • Report partial or rejected rows rather than treating an accepted job as verified data.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall