beaker-setup

Configures Python repositories with Beaker integration contracts and validates hosted optimization setup.

5|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/rilixai/beaker-skill --skill beaker-setup-rilixai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beaker-setup
Source: https://github.com/rilixai/beaker-skill/tree/main/skills/beaker-setup
Command: npx skills add https://github.com/rilixai/beaker-skill --skill beaker-setup-rilixai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires beaker-sdk, and includes references (resource) components.

What problem does it solve? Connecting a Python repository to Beaker's hosted optimization platform requires wiring an Integration contract, real labeled data, model routing, credentials, and GitHub App access, and mistakes in any step cause failed hosted runs. This Skill guides an agent through the full onboarding loop so the integration validates with a strict smoke check before launch. ## Core Features & Use Cases - Guided onboarding loop: Uses beaker onboarding status as loop control, following its returned next action and relaying developer-owned steps such as GitHub App installation. - Integration contract wiring: Implements Integration, run_setup, run_case, and score_case under .beaker/ while preserving production behavior and adding no tests or CI/CD. - Dataset and credential preflight: Uploads labeled datasets, retains immutable name@revision selectors, declares required_env, and validates with beaker run smoke --strict. - Use Case: A developer asks the agent to set up Beaker in a monorepo service; the Skill discovers the project root, runs beaker init, wires the real model call, pushes a beaker/<timestamp>-<agent> branch, and triggers the first hosted run. ## Quick Start Ask your agent to set up Beaker in this repository and connect it to the real labeled dataset for optimization.

Frequently Asked Questions about beaker-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up Beaker in a Python repository?

Run beaker auth status, then beaker init in the project root, install the printed beaker-sdk dependency, and replace every TODO(beaker) in the generated integration. Finish with beaker agent setup, dataset selection, and beaker run smoke --strict before triggering a hosted run.

How do I configure Beaker in a monorepo?

Identify the package holding its own pyproject.toml rather than the Git root, then set integrations.<id>.source_dir to the Git-root-relative project path such as services/invoices. Keep package_import_root relative to that source directory, typically .beaker.

Does beaker run smoke validate application execution?

No, smoke validates typed rows, case loading, input files, and document materialization but never calls run_case or score_case. A passing smoke check does not prove hosted credentials work or that the application path executes.

Why does my hosted Beaker run fail with a source_dir error?

The source_dir was written relative to the YAML or working directory instead of the Git checkout root. Set it to the exact repository-relative project path, commit, push, and launch a new run since existing runs are immutable snapshots.

Can Beaker onboarding add tests or CI pipelines?

No, the integration is validated by beaker run smoke --strict and hosted runs, so onboarding never creates test files, fixtures, CI workflows, or pre-commit hooks. Existing tests may be read as evidence but never modified.