Preview guidance. Review the decisions and proposed changes before applying them to your product.
tensor9-byoc-onboarding skill turns a coding agent into an onboarding assistant for your Terraform. The Claude Code and Codex editions use the same name and workflow. Install the complete preview package below, including its bundled references and catalog.
The skill:
- Finds places in your Terraform that need one of your decisions: the install’s domain, the region, names that must be unique per install, who supplies each secret, endpoints that must stay public, and blocks only your own environments need. It consults its common Terraform mistakes library and shared external-service considerations, then follows relevant application consumers rather than treating a service name as a decision.
- Asks you each decision, one at a time, showing the file, the line, the block and the options. It never guesses an answer and never invents a label, description or reason.
- Writes the annotations you choose. It leaves compiler automation to the compiler. Adding a namespace variable and name prefixes requires your agreement. For a common-mistake finding, it traces the resource’s absence condition and its consumers, then shows a proposed repair for your review before applying it. Feature configuration and source repairs are separate edits.
- Reports annotations, configuration choices, common-mistake findings and accepted or deferred repairs, existing annotations, and open decisions. It identifies the consideration-data source, version and digest used. Source findings and catalog suggestions are separate from compiler diagnostics, your decisions and verified application behavior.
The skill does not upload your Terraform to Tensor9 or run a compile, publish or deployment. Your coding agent processes files according to its own configuration and data handling. Review that configuration before opening private Terraform.
Install
Install the completetensor9-byoc-onboarding folder. The refreshed preview package includes:
tensor9 CLI with your vendor profile for current consideration knowledge. The Python 3 helper retains validated data and supports offline lookup. No private Tensor9 source checkout, Kotlin development environment or internal MCP service is required. Keep the mistake reference as well as the consideration files; installing SKILL.md alone is incomplete.
The commands below expect the supplied preview archives named below in your Downloads directory. These bundles contain skill source revision 098190675f and the unchanged consideration catalog 1.0.0. The filename suffix identifies the skill source revision, not a new catalog version. Earlier preview archives remain separate; verify the exact supplied filename and checksum before installation.
Download the package for your coding agent into your Downloads directory:
Verify the downloaded archive with shasum -a 256 <archive> before extraction:
Inspect the archive contents before extracting. If a skill with this name is already installed, review and preserve your existing copy before replacing it.
- Claude Code
- Codex
Install for yourself, in every project:Or install for everyone working in one repository, by committing it to that repository:Either destination contains
skills/tensor9-byoc-onboarding/SKILL.md. Start a new Claude Code session to load it.Run it
Open your agent at the root of your Terraform repository and invoke the skill, optionally with the path to your Terraform root module. Without a path it uses the current directory.- Claude Code
- Codex
Refresh and look up considerations
Both editions obtain maintained considerations from your vendor controller (VCtrl) through the publictensor9 CLI. Use the controller profile that setting up your control plane
created: tensor9 vendor setup prints its name and makes it your default profile. These examples call it
my-vendor; replace that name with your own. Leave T9_API_KEY unset: your
API key is not a controller credential, and a sandbox-connected profile is
separate exploration access. Do not substitute either for your controller profile or use a profile for a
different development install.
This preview requires a CLI and VCtrl that support consideration lookup. The direct CLI commands above report an error when lookup fails. The Python helper below retains labelled cache/bundle fallback if the CLI is missing, the controller is unavailable, authentication fails or the command is unsupported. That fallback is not a successful VCtrl response or proof of the latest catalog. A generic failure does not establish that a controller is old or authentication failed. The helper never switches profiles, logs in or upgrades automatically.
--refresh to force a refresh and --no-refresh for an offline query. To refresh the retained copy and then query it offline, choose its installation folder. For example, with the personal Codex installation:
SKILL_DIR="$HOME/.claude/skills/tensor9-byoc-onboarding"; project installations use their .claude/skills or .agents/skills folder. Refresh invokes the CLI’s read-only snapshot command and validates its exact versioned bytes before replacing cached data. Queries without either refresh flag may perform the bounded automatic refresh; --no-refresh keeps them offline. After a failed automatic refresh, the loader waits 10 minutes before another automatic attempt; --refresh still tries. Inspect the reported refresh status and cache age, and do not describe a cache or bundle fallback as a successful controller response. Inspect the reported source, original serving vendor/profile, version, digest and any fallback reason. Profile names can be reconfigured and vendor IDs are scoped to a stage; an old cached receipt does not establish the identity of a currently selected controller.
Refreshing knowledge does not reinstall the skill or change its permissions. An incompatible data format may require a newer skill package. Catalog guidance does not authorize edits, deployments or credentials access.
The initial catalog covers 96 service entries across 12 categories. These are consideration prompts and research cues, not a list of verified Tensor9 service adapters or a promise that every application integration has been examined. Read the general external-service guide, Stripe guide and Metronome guide for the corresponding vendor decisions and checks.
What a session looks like
The agent works through the decisions one at a time. A typical exchange:After the agent finishes
- Review the diff. Check annotations separately from accepted name prefixes, feature settings and common-mistake repairs. For external services, review your behavior/ownership decisions and the full application, data, job and callback changes. Review deferred findings before installing.
- Run
terraform validateandterraform planagainst an appropriate environment. Annotations alone leave the plan unchanged; configuration and repair effects need their own review. - Resolve any open decisions, by hand or by running the skill again.
- Continue with compile and install.