What problem does it solve?
Adding a new built-in plugin to Golem requires coordinating a standalone WASM component, build tooling, and registry-service provisioning code, and missing any step breaks compilation or deployment. This Skill provides the exact workflow to create, build, embed, and register a built-in plugin that ships with Golem and is granted to every environment.
Core Features & Use Cases
- Plugin scaffolding: Guides creation of a standalone Golem application under
plugins/<plugin>/ following the OTLP exporter layout, with the current async golem-rust oplog processor SDK interface.
- Build and embedding: Extends the
build-plugins duckscript task in Makefile.toml, validates output with wasm-tools, and wires the committed WASM into the registry service via include_bytes! and a BuiltinPluginDescriptor entry.
- Provisioning and verification: Explains the descriptor-driven provisioner, transactional environment grants, and the authoritative verification commands including
cargo make integration-tests-group7.
- Use Case: You want to add a new metrics-exporter plugin that every Golem environment receives automatically; follow the workflow to implement the oplog processor, build the WASM, register the descriptor, and verify provisioning end to end.
Quick Start
Ask the AI to create a new built-in Golem plugin named metrics-exporter following the OTLP exporter pattern and register it in the registry service.