Stats
Actions
Available In
Tags
Plugin
component-developer
Develop, test, debug, review, and migrate Keboola Python components for data pipelines—including extractors, writers, apps—with AI skills for config schemas (conditional fields, UI), code quality (Ruff, architecture), local datadir/pytest/VCR testing, uv/pyproject.toml upgrades, Docker builds, and platform context via MCP/Datadog.
What's Inside
Slash Commands3
Generate Vcr Tests
/generate-vcr-tests
Set up VCR functional tests for this Keboola component using the `component-developer:test-component` skill.
Review
/review
Code quality + backward compatibility review for Keboola Python components
Test Configuration Schemas
/schema-test
Launch interactive schema tester for testing component configuration schemas
Agents3
component-builder
/component-builder
Expert Keboola Python component developer for implementing and extending components. Use when building new extractors/writers/applications, implementing features, adding incremental loads, separating API clients, applying self-documenting workflow patterns, or maintaining code quality with Ruff. Delegates UI/schema work to ui-developer.
tester
/tester
Expert agent for writing and maintaining tests for Keboola Python components. Specializes in datadir tests, unit tests, mock-based tests, and VCR functional tests with keboola.datadirtest.
ui-developer
/ui-developer
Expert in Keboola configuration schemas, conditional fields (options.dependencies), UI elements, sync actions, and schema testing. Can launch schema-tester and run Playwright tests. Specialized for configSchema.json and configRowSchema.json development.
Skills9
develop-component
/develop-component
Expert Keboola Python component developer for ongoing development work — implementing features, extending extractors/writers/applications, adding incremental loads, designing configuration schemas, separating API clients, applying self-documenting workflow patterns, and maintaining code quality with Ruff. Use this skill whenever the user is working on component logic, implementation, or architecture — whether building something new or extending existing code. Do NOT use for initial project scaffolding (that's get-started) or UI-only schema work (that's build-component-ui).
get-started
/get-started
Mandatory initialization workflow for new Keboola Python components — use this skill before writing any code. Contains the exact cookiecutter command, Keboola-specific post-template cleanup steps, KBC_DATADIR directory structure, data/config.json format, and first commit format that are easy to get wrong without this reference. Invoke whenever the user is starting from a fresh or empty repository, has never built a Keboola component before, wants to run the cookiecutter template, or says things like "new extractor for X", "build ex-something from scratch", "fresh repo", "empty git repo", "brand new component", "never done this in keboola", "initialize a component", "scaffolding a new component", "just initialized the git repo", "nothing set up yet". Not for existing components that already have src/component.py.
build-component-ui
/build-component-ui
Expert in Keboola configuration schemas, conditional fields (options.dependencies), UI elements, sync actions, and schema testing. Can launch schema-tester and run Playwright tests. Specialized for configSchema.json and configRowSchema.json development.
component-defaults
/component-defaults
Canonical template files for Keboola Python components — Dockerfile, pyproject.toml, push.yml, build_n_test.sh, docker-compose.yml, pre-commit-config.yaml, and config-schema.md. Load this whenever creating or modifying any of these files in a component, or when checking whether non-source files are aligned with the official cookiecutter template. Any deviation from these templates must have an explicit reason. Internal utility — usually invoked via Task from develop-component or migrate-to-uv, but should be consulted any time one of these files is being touched.
debug-component
/debug-component
Expert skill for debugging Keboola Python components. Use when a component is failing, a job returned an error, or behavior is unexpected. Uses whatever tools are available — Keboola MCP for job/config inspection, Datadog for logs, Linear/Jira for issue context, Slack for incident history, and local Bash for reproducing issues. Invoke for "failing job", "exit code 2", "component throwing an error", "why is my component not working".
Stats
Version3.3.0
LanguageASL
Stars11
Forks2
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Uses power tools
Uses Bash, Write, or Edit tools
