메뉴
Optimizes Claude Code Pro/Max usage by priming the 5-hour rolling window early morning, ensuring resets align with peak work hours for maximum Opus availability.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Ask a stronger Zo instance for planning, judgment, debugging guidance, or adjacent thinking through a minimal token-light oracle pattern using /zo/ask plus URL-based context drops.
Generate high-quality landing pages with anti-slop guardrails and multi-platform support. Creates modern, accessible designs for Zo.space, standalone HTML, and Next.js with professional aesthetics and clear typography hierarchy.
Maintain research repositories and a wiki-style compendium under Research/repos; scans existing knowledge folders before proposing repos, supports append-only intake, compaction, and repair sweeps for failed meeting-derived appends. Portable: owner/venture identity is externalized to a profile so the skill can ship publicly and be re-pointed on any Zo.
Portable Krisp transcript ingestion and meeting block pipeline for Zo Computer. Receives Krisp transcript webhooks or manual transcript files, normalizes meetings into repairable folders, optionally triangulates against calendar context, generates summary/metadata/decisions/action-item blocks, supports richer v3-style add-on blocks, archives monthly, and notifies the Zo owner when a meeting is partial or needs review.
Safe, archived Skill wrapper for the former standalone ZoATS applicant-tracking-system repo. Use when inspecting, packaging, validating, or exporting ZoATS as a reusable Zo skill scaffold; do not install live routes or run candidate/employer workflows on V's Zo without explicit approval.
Evaluate early-stage pitch decks across four investor credulity frames, stage-aware substantive rubric dimensions, optional named-POV reads, and markdown/JSON report rendering.
| name | claude-code-window-primer |
| description | Optimizes Claude Code Pro/Max usage by priming the 5-hour rolling window early morning, ensuring resets align with peak work hours for maximum Opus availability. |
| compatibility | Zo Computer with Claude Code Pro or Max subscription |
| metadata | {"author":"thevibethinker","version":"1.0","created":"2026-02-12T00:00:00.000Z","tags":["claude-code","optimization","scheduling"]} |
Claude Code Pro has a 5-hour rolling usage window. If you start using Opus at 9am, you hit the limit around 2pm and wait until... 2pm for reset. That's a dead zone right when you're productive.
Prime the window before you wake up. A trivial Opus request at 6:30am starts the clock, giving you resets at useful times:
| Time | Event |
|---|---|
| 6:30am | Window primed (while sleeping) |
| 11:30am | First reset (mid-morning) |
| 4:30pm | Second reset (afternoon) |
| 9:30pm | Third reset (evening if needed) |
This maximizes Opus availability during typical work hours (9am–11pm).
No. The primer uses ~15 tokens (asks Opus to return 0 or 1). Weekly limits track actual usage, not window starts. This is pure timing optimization.
In a Zo conversation:
Create a scheduled agent:
- Schedule: Daily at 6:30am (your timezone)
- Instruction: Run python3 Skills/claude-code-window-primer/scripts/prime_window.py
- Delivery: None (silent)
Or adjust the time to ~3 hours before you typically start working.
Check your Claude Code usage after the first run — you should see a tiny blip at 6:30am.
Shift your window anytime:
python3 Skills/claude-code-window-primer/scripts/prime_window.py
Useful if you wake up early or want to realign mid-day.
Different wake time? Edit the agent schedule. The math:
Max subscription? Same principle applies — you just have more headroom per window.
The script calls /zo/ask with a trivial prompt targeting Opus specifically:
"Return either 0 or 1 at random. Nothing else."
Minimal tokens, starts the window, done.
claude-code-window-primer/
├── SKILL.md # This file
└── scripts/
└── prime_window.py # The primer script