القائمة
Use when running, documenting, or reviewing adaptive active search backend context discovery, including zob_context_search, optional ColGREP setup, and grep/find/read fallback behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when reviewing or modifying ZOB communication, ledgers, Mission Control coms, or live transport safety gates.
Use when an active ZOB handoff, live peer question, required-local coms delivery, or orchestration message is needed.
Use when planning, using, reviewing, or implementing ZOB /goal-linked TODOs, subtodos, TODO HUD progress, delegated TODO claims, or hierarchical subagent work graphs.
Use when working inside the ZOB Pi harness, designing agentic workflows, creating specialist prompts, adding Pi extensions, or turning repeated tasks into software factories.
Use before non-trivial work, uncertain tool selection, orchestration, delegation, context lookup, factory work, autonomous-runtime claims, or evidence-gated completion.
Use when driving the append-only metadata-only worklist blackboard — appending events, reading derived directives, leasing/satisfying directives by content hash, delivering idempotent DIRECTIVE_READY notifications, running the liveness watchdog (observe/escalate), or building/querying the dependency DAG.
| name | zob-context-discovery |
| description | Use when running, documenting, or reviewing adaptive active search backend context discovery, including zob_context_search, optional ColGREP setup, and grep/find/read fallback behavior. |
Use this skill for:
zob_context_search and zob_context_* discovery workflows.zob_context_search for repo-local discovery when the runtime tool is available.zob_context_search/ColGREP before broad grep/find. This includes prompts like “explore this repo”, “where is this mechanism?”, or “find the design/flow”.zob_context_search is not exposed in the current session/toolset but bash is available, use the compact local wrapper before broad grep: npm run --silent zob:context:query -- --query "<natural language query>" --max-results 6 --max-context-lines 1.rg/grep; the wrapper is the ColGREP path for those sessions.zob_context_search/ColGREP at context pivot points, not only once at startup: new subsystem/domain, ambiguous or broad file area, fallback_status suggesting narrower paths, repeated low-signal grep/find, unfamiliar code before edits, or unknown validation/test failure..pi unless .pi/sessions and .pi/agent-sessions are explicitly excluded/pruned..env, **/.env, **/*secret*, **/*key*, private keys, .pi/sessions, .pi/agent-sessions, node_modules, dist, or build.npm run zob:context:doctor checks the active backend, reports config/status, and prints install/setup guidance without installing anything.npm run zob:context:init may initialize safe ColGREP settings/indexing only when ColGREP is already installed and the owner runs it deliberately.npm run zob:context:query -- <query> runs a one-shot context query, preferring ColGREP when ready and using grep fallback otherwise.npm run smoke:context-discovery validates deterministic fallback behavior and should pass even when ColGREP is absent..pi/context-discovery.json under promptInjection.enabled.zob_context_search or the compact npm run --silent zob:context:query wrapper, then read exact files when details are needed.zob_context_search execution must remain async/non-blocking from the Pi extension perspective; avoid synchronous long-running ColGREP calls in tool handlers.No-ship for context discovery if any of these remain true: