メニュー
Adjust a working dlt pipeline for production — remove dev limits, verify pagination, configure incremental loading, expand date ranges. Use when the user wants to remove .add_limit(), load more data, fix pagination, or set up incremental loading.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scan design/ for backlog/todo artifacts, check if work has been merged into the codebase, and auto-rename completed ones to done-. Use for periodic hygiene, after merging branches, or to audit design artifact status.
Use when writing Dagger pipelines in Python, building containerized CI/CD with the Dagger Python SDK, creating Dagger modules/functions/objects, integrating services (PostgreSQL, Redis) in Dagger, using Dagger LLM/agent features, or running Dagger in GitHub Actions.
Use when creating specifications, implementation plans, or tools for a feature - enforces consistent naming across related artifacts
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use this skill when the user wants to run hotdata CLI commands, query the Hotdata API, list workspaces, list connections, create connections, list tables, manage datasets, execute SQL queries, inspect query run history, search tables, manage indexes, manage sandboxes, manage workspace context and the data model via the context API (`hotdata context`), or interact with the hotdata service. Activate when the user says "run hotdata", "query hotdata", "list workspaces", "list connections", "create a connection", "list tables", "list datasets", "create a dataset", "upload a dataset", "execute a query", "search a table", "list indexes", "create an index", "list query runs", "list past queries", "query history", "list sandboxes", "create a sandbox", "run a sandbox", "workspace context", "pull context", "push context", "data model", or asks you to use the hotdata CLI.
Use when building, deploying, or debugging applications on Modal (modal.com) — serverless cloud compute for Python. Covers container images, GPU functions, web endpoints, volumes, secrets, scheduling, distributed training, calling deployed functions, and scaling patterns.
| name | adjust-endpoint |
| description | Adjust a working dlt pipeline for production — remove dev limits, verify pagination, configure incremental loading, expand date ranges. Use when the user wants to remove .add_limit(), load more data, fix pagination, or set up incremental loading. |
| argument-hint | [pipeline-name] [adjustments] |
Parse $ARGUMENTS:
pipeline-name (optional): the dlt pipeline name. If omitted, infer from session context. If ambiguous, ask the user and stop.hints (optional, after --): specific adjustments to make.add_limit() requires verified pagination.add_limit(1) during development masks pagination problems — only one page is fetched, so a broken paginator never loops. Removing it without explicit pagination causes stuck pipelines.
Before removing .add_limit():
"paginator" config. If any rely on auto-detection, add one first.debug-pipeline with INFO logging for the first unlimited run to watch pagination progress and catch loops early.Pipeline worked with .add_limit(1). After removing the limit, it hung forever — dlt's auto-detected paginator looped. Fix: added explicit "paginator": {"type": "cursor", "cursor_path": "next_page", "cursor_param": "page"}. Full load then completed in 5 seconds.
explore-data to chart and analyze the data