Scaffold Forge long-running processes as independently deployed binaries with cobra subcommands.
npx skills add https://github.com/reliant-labs/forge --skill binaries
Please help me install this Agent Skill. Skill: binaries Source: https://github.com/reliant-labs/forge/tree/main/internal/templates/project/skills/forge/binaries Command: npx skills add https://github.com/reliant-labs/forge --skill binaries
Forge users need a clear, repeatable way to decide when a long-running process should be scaffolded as a binary (with its own Deployment) instead of a service, worker, or operator.
Ask the AI: scaffold a long-running Kubernetes-ready reverse-proxy process as a Forge binary named "workspace-proxy" and explain how its lifecycle and deployment should work.
High-intent search queries and answers about installing and using this skill.
Scaffold a binary when a long-running process needs its own blast radius, scaling, and deploy lifecycle. This applies to reverse proxies, sidecars, isolated webhook receivers, or tools daemons that should not register Connect RPC handlers with the canonical server.
To scaffold a Kubernetes-ready binary, define forge.yaml binaries entries to generate Deployments. Implement Deps with validateDeps plus a Runner.Run(ctx) loop that drains on SIGINT/SIGTERM via context cancellation, wiring the cobra subcommand as a thin adapter that loads config and calls New(deps).Run(ctx).
The cobra CLI handles process lifecycle by acting as a thin adapter that loads config and calls New(deps).Run(ctx). The Runner.Run(ctx) loop drains on SIGINT/SIGTERM via context cancellation, ensuring the independently deployed binary shuts down gracefully.
Yes, forge.yaml binaries entries render into Kubernetes Deployments that run the cobra subcommand with the correct deploy story and shared defaults, specifically supporting off-service consumers, sidecars, and isolated webhook receivers that need independent scaling.
A Forge binary is chosen when a process needs its own Deployment and deploy lifecycle without registering Connect RPC handlers. Workers and operators are alternative shapes selected based on lifecycle ownership and specific scaling requirements within the Forge ecosystem.
bbolek-apGenerate and validate Kubernetes manifests and nginx configuration for multi-service projects.
pluginagentmarketplaceBuild Cobra-based Go CLI tools with Viper configuration and subcommands.
resonatehqInvoke and manage Resonate durable workflows from Rust clients.
reliant-labsMigrate network-facing servers into Forge service-shaped projects with scaffolding.
