granite.build: Skill for Claude Code

Granite.build docs lookup

Granite.build's docs ship as Markdown in references/ next to this skill. Read the relevant file(s) with the file tools, then answer grounded in their content, citing the doc path.

Pick a file from the topic index below and read it directly with the file tools.

Important caveat: the docs are k8s/LSF-centric

This environment runs the standalone bash backend by default, but most docs are written for the Kubernetes/LSF backends. Several documented conveniences do not apply to bash, e.g.:

• config.workload.commands (inline command list) — k8s/LSF only.
• config.gb.files_to_create / additional_files — k8s/LSF only.
• The generic gbstep step — has no bash launcher; using it on bash fails with KeyError: 'helm'.

So: use the docs for the schema and concepts (URIs, inputs/outputs, the field reference), but for how a bash step actually launches and behaves, prefer these over the doc prose:

• The create-build skill's references/steps.md — tested contracts (inputs/outputs/env, the artifact monitor) for the shipped bash steps (inference, lora-finetune, inference-lora, hello, command).
• A prior successful build's job.log, via build_job_log — the real stdout of a working build. Reverse-engineering a working build beats guessing from docs.

When the docs and actual bash behavior disagree, trust the observed behavior and say so.

Where the docs are

Everything is in references/ next to this SKILL.md (the index below lists references/<x> paths). If a file is ever missing locally, the same docs are online in the ibm-granite/granite.build repository.

Index — pick by topic

Authoring builds

• references/builds/build-yaml-reference.md — authoritative build.yaml schema (targets, steps, inputs/outputs, URIs, all fields/options).
• references/builds/README.md — build features overview; references/builds/hf-push.md — push artifacts to HuggingFace; references/builds/event-notifications.md.
• references/steps/bring-your-own-step.md, references/steps/custom-code-steps.md, references/steps/bring-your-own-image.md — author/use custom steps (examples lean k8s/docker; the commands/files_to_create features are k8s/LSF only). references/steps/README.md — steps overview.