E2e To Bazel Agent Skill
>- Converts end-to-end (e2e) test targets or paths to `bazel run` commands for `heir-opt`. Use when you need to convert an e2e test target (where flags are defined in the BUILD file) to a shell command whose flags can be modified for further analysis and debugging.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/google/heir --skill e2e-to-bazelWhat it tells the agent to use
found in the instruction textThe instruction itself
5 sections, as written by the authorE2E To Bazel
Overview
This skill guides the agent in using the e2e_to_bazel tool to convert e2e test
targets or paths to executable commands.
Usage
Converting a Test Target or Path
To convert an e2e test target, directory, or source file to a bazel run
command, use the following command recipes:
bazel run //third_party/heir/scripts:e2e_to_bazel -- {target_or_path}
Replace {target_or_path} with the test target (e.g.,
//tests/Examples/lattigo/ckks/mnist:mnist_test), directory, or source file
path.
Gotchas
- Blaze Query Dependency: The tool relies on
bazel queryto extract
attributes. This requires a working blaze environment and may be slow for
the first run.
- Workspace State: It requires that the workspace is in a state where
bazel query can evaluate the targets.
- Source file mapping: If a source file is provided, it searches for
heir_opt targets that depend on it.
Copy this checklist and track progress:
- [ ] Step 1: Identify the e2e test target, directory, or file to convert.
- [ ] Step 2: Run the `e2e_to_bazel` tool on it.
- [ ] Step 3: Inspect the generated command or run it.
- [ ] Step 4: Verify execution results.
<!-- mdformat global-off -->
Other skills for the same job
different authors, same section of the catalogue
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
How to use it
Take google/e2e-to-bazel from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.