القائمة
Use when debugging Reef or fleet behavior through logs, including keyword/date filtering, per-agent inspection, post-mortem analysis, and handoff investigation.
التثبيت باستخدام 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 | logs-debugging |
| description | Use when debugging Reef or fleet behavior through logs, including keyword/date filtering, per-agent inspection, post-mortem analysis, and handoff investigation. |
Use this skill when logs are the fastest way to understand what happened.
The logs surface is a real browser now:
Use it when you need:
Stopped descendants are still valid post-mortem subjects. If the issue happened in the past:
Use reef_log for:
Good logs make later handoff and root supervision cheaper.
