القائمة
Use when spawning, configuring, auditing, or retiring resource VMs that host infrastructure such as databases, services, test environments, or webhook-facing systems.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when doing code work that must be integration-friendly: branches, commits, tests, PR-ready receipts, owned paths, and parent-friendly handoff.
Use when implementing and exposing a product/application service or UI that should run outside Reef root. Choose child/resource VM placement, stand up the app, and report how to reach it.
Use when handling parent commands such as steer, abort, pause, or resume, or when deciding how urgently to react to inbox messages from above.
Use when agents need to coordinate through reef store, peer signals, barriers, rendezvous, or child/peer communication without breaking authority boundaries.
Create a new service module for reef. Use when adding a new capability to the server — a new store, API routes, LLM tools, behaviors, or dashboard widget.
Use when a task has multiple independent subsystems, needs recursive delegation, or requires a parent to split implementation and then integrate the results.
| name | resource-ops |
| description | Use when spawning, configuring, auditing, or retiring resource VMs that host infrastructure such as databases, services, test environments, or webhook-facing systems. |
Use this skill when the task needs infrastructure rather than another disposable worker.
When the task needs a new UI, service, database, webhook sink, or raw environment, first decide whether it belongs:
Default to the separate VM path unless the feature is clearly part of Reef itself.
Do not use root as the default home for product services just because it is already running.
A resource_vm is passive infrastructure:
It is not a token/cost usage entity.
resource_vm is protected-by-default.
Do not tear it down just because:
Teardown should be:
vers_vm_useWhen done setting up infrastructure, report:
If you intentionally tear it down, say that it was explicit teardown, not incidental lifecycle cleanup.