Generate Afterburn cloud provider modules, tests, and documentation.
npx skills add https://github.com/coreos/afterburn --skill add-provider-coreos
Please help me install this Agent Skill. Skill: add-provider Source: https://github.com/coreos/afterburn/tree/main/.opencode/skills/add-provider Command: npx skills add https://github.com/coreos/afterburn --skill add-provider-coreos
Adding a new cloud/platform provider to Afterburn is repetitive and error-prone because it requires creating Rust modules, mock tests, wiring into dispatch tables, and updating multiple docs and service files manually. This Skill automates the repetitive scaffolding work, ensures consistent project structure, and reduces integration mistakes.
Run the add-provider workflow and answer the interactive prompts to scaffold a new provider module and accompanying tests and documentation.
High-intent search queries and answers about installing and using this skill.
Scaffolding a new Afterburn cloud provider involves interactively entering the provider ID, struct name, and metadata type. The workflow then generates Rust modules, mock tests, dispatch wiring, and documentation, finishing with cargo fmt, build, test, and clippy verification.
When adding an IMDS or configdrive platform, you must update src/providers/mod.rs, src/metadata.rs, docs/platforms.md, docs/usage/attributes.md, and docs/release-notes.md. The scaffolding workflow also conditionally modifies systemd and dracut service files based on supported features.
Yes, the scaffolding workflow runs cargo fmt, build, test, and clippy automatically after generating provider modules and wiring. This verifies that the new boilerplate compiles correctly and meets project linting standards before submitting a contribution.
Yes, the scaffolding workflow supports both IMDS and configdrive metadata types. During the interactive prompts, you specify the metadata type, base URLs, and supported features, which dictates how the provider Rust module and dispatch wiring are generated.
To avoid naming conflicts when creating an Afterburn provider module, the scaffolding workflow validates the provider ID and struct name against existing entries during interactive input. This prevents duplicate module generation and dispatch errors before any files are created.
mtaku3Guide Rust project setup with Cargo workspaces, clippy, rustfmt, and cargo-nextest.
coralogixRun cargo test, fmt, and clippy for the cx CLI codebase.
wimbleroboticsAutomate boot-time ROS 2 startup with systemd service files.
augenticGenerate and update Rust WASM test suites from specification artifacts.
