메뉴
Universal close skill. Just say "close" and it auto-routes to the right close skill (thread-close, drop-close, or build-close) based on SESSION_STATE context. Works in both native Zo and Claude Code environments.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Automated build orchestration system. Spawns headless Zo workers (Drops) in parallel Waves, monitors health, validates Deposits via LLM judgment, handles dead Drops, and escalates via SMS. Supports sequential Streams within Waves. Replaces manual Build Orchestrator for unattended execution.
Close normal interactive conversation threads. Handles tier detection, position extraction, AAR generation, and commit suggestions. For Pulse workers use drop-close. For post-build synthesis use build-close.
Meeting ingestion pipeline v3 with calendar triangulation, CRM enrichment, org classification, quality gates, HITL queue, and canonical S-shape generation. Unified CLI for transcript processing from ingest to archive.
Close Pulse worker (Drop) threads. Writes structured deposit JSON for orchestrator review. Does NOT commit - that's the orchestrator's job. For normal threads use thread-close. For post-build synthesis use build-close.
Improve layout, spacing, and visual rhythm. Fixes monotonous grids, inconsistent spacing, and weak visual hierarchy to create intentional compositions.
Post-build synthesis for Pulse builds. Aggregates all deposits, synthesizes decisions and learnings, extracts positions, generates build AAR. Replaces N per-worker closes with 1 build-level close. For normal threads use thread-close. For Pulse workers use drop-close.
| name | close |
| description | Universal close skill. Just say "close" and it auto-routes to the right close skill (thread-close, drop-close, or build-close) based on SESSION_STATE context. Works in both native Zo and Claude Code environments. |
| compatibility | Created for Zo Computer |
| metadata | {"author":"<YOUR_HANDLE>.zo.computer"} |
Check if running in Claude Code:
python3 N5/scripts/cc_close_bridge.py detect
CLAUDE_CODE=false → Native Zo path (Step 2a)CLAUDE_CODE=true → Claude Code path (Step 2b)Run the router with the current conversation ID:
python3 Skills/thread-close/scripts/router.py --convo-id <CONVO_ID>
The router reads SESSION_STATE and picks the right skill.
Claude Code sessions don't have a Zo conversation ID or SESSION_STATE. Use the bridge to create a synthetic workspace first.
You (the LLM) must determine these from conversation context:
build, research, discussion, planning, debug)Then run:
python3 N5/scripts/cc_close_bridge.py init
--type <type>
--focus "<focus>"
--tier <tier>
Add --build-slug <slug> if build context applies.
Add --artifacts path1 path2 ... for key files.
Capture the CC_CONVO_ID from output, then run the normal router:
python3 Skills/thread-close/scripts/router.py --convo-id <CC_CONVO_ID>
From here the flow is identical in both environments.
Read and follow file Skills/thread-close/SKILL.md (or whichever skill the router selected).
The script outputs JSON context → you do semantic analysis → you call write functions → you echo the title.