Examples¶
Where to find working capabilities and workflows — not a second copy of every file.
Fresh installs are intentionally empty¶
runtime bootstrap creates an empty compatibility cache but installs no
capability definitions. runtime capability list exits 0 and explains how to
configure a source. This avoids silently choosing executable workflow content
for you.
Company Capability Registry¶
Reusable, version-controlled capabilities:
engineering-runtime-capabilities
git clone https://github.com/engineeringruntime/engineering-runtime-capabilities.git
git -C engineering-runtime-capabilities checkout <reviewed-commit>
runtime capability validate \
engineering-runtime-capabilities/capabilities/files/notes-roundtrip.md
runtime capability execute \
engineering-runtime-capabilities/capabilities/files/notes-roundtrip.md \
--input path=./notes.txt --input message="example"
For name resolution across a team library, declare that checkout under
capabilities.sources: Sharing a Capability Source.
CI samples¶
Live GitHub Actions that install a release and execute capabilities:
| Area | Path |
|---|---|
| Auth-free demo | examples/capabilities/files/notes-roundtrip.md |
| GitHub packs | examples/capabilities/github/*.md |
| Install action | .github/actions/setup-runtime |
| Smoke workflow | .github/workflows/runtime-ci.yaml |
See CI/CD.
Command cheatsheets¶
Every installed binary version refreshes copy-paste examples into:
ls ~/.engineering-runtime/commands/
cat ~/.engineering-runtime/commands/github_commands.txt
cat ~/.engineering-runtime/commands/command_commands.txt
These are validated against the binary in the source repo; prefer them over memorized flags.
Provider pages¶
| Provider | Page |
|---|---|
github |
github |
files |
files |
| Command Engine roster | command-binaries |
Operational examples on this site were verified against Runtime 0.9.8. After bootstrap, the version-exact files in Runtime Home win.