AGENT SKILL
pm-etl
Run bounded ETL syncs from configured connections.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-09-21
- Stars
- ★ 7
- Forks
- 0
01 前言 Front Matter
- name
- pm-etl
- description
- Run bounded ETL syncs from configured connections.
03 SKILL.md 正文
pm-etl
- Use
pm etl run --connection <name> --stream <stream> --json. - Use
--batch-sizefor large streams when the caller requests bounded memory behavior. - Supported sync modes are
full_refresh_append,full_refresh_overwrite,full_refresh_overwrite_deduped,incremental_append, andincremental_append_deduped. - For the closed managed-PostgreSQL route, run
pm etl transport postgres-managed-target plan --connection <name> --stream <stream>, preview the plan, then send its one-time token throughpm etl run ... --approval-token-stdin --confirm destructive; PostgreSQL and declared API sources use sealed catalogs, and callers never supply raw SQL or target identifiers. - For a connector-declared typed destination, run
pm etl transport declarative-typed-destination plan --connection <name> --stream <stream>, preview it, then use the ordinary approved ETL run. The saved stream'sdestination_actionselects the connector-ownedwrites.jsonaction; never accept it, a route, method, body, mapping, connector, or evidence as a run-time flag. - In
pm etl run --jsonandpm etl status --json, inspectrun.destination_resultsfor each provider-successful typed action. A later local receipt or acknowledgement failure leaves the run uncheckpointed but retains ordered sanitized provider evidence. Concrete configured credential material is masked; provider-owned field names and ordinary values remain available. - A terminal
run.status=delivered_reconciliation_requiredmeans the provider effect, read-back, and checkpoint are already durable. Preserve its exactETLRunand categorized nonzero exit; rerun only the same saved connection and stream so pm repairs its declareddelivery_reconciliationlocally before endpoint resolution and never replays source or destination I/O. Never replace it with a normal retry or a raw provider action. - Incremental modes and deduped compatibility names require a cursor. Deduped modes require a primary key; static manifests advertise the full deduped compatibility name only with both fields and incremental modes only with a declared incremental executor. The deduped compatibility names refuse before source I/O until a matching transport is admitted.
- Inspect
batch_countandcheckpointin JSON output after runs.
04 同仓库更多 Skills
recipe-preview-approve-reverse-etl
Preview and approve a reverse ETL plan safely.
★ 7
recipe-github-prs-to-warehouse
Sync GitHub pull requests into the local warehouse.
★ 7
pm-zoom
Zoom connector knowledge and safe action guide.
★ 7
pm-zonka-feedback
Zonka Feedback connector knowledge and safe action guide.
★ 7
pm-zoho-invoice
Zoho Invoice connector knowledge and safe action guide.
★ 7
pm-zoho-inventory
Zoho Inventory connector knowledge and safe action guide.
★ 7