[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RTQ1RGSH5JHN4GPYSECZR2":3,"skill-same:01M6RTQ1RGSH5JHN4GPYSECZR2":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":26,"commitSha":45,"skillDirectory":46,"forksCount":13,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M6RTQ1RGSH5JHN4GPYSECZR2","three-shifts",null,"Daily standup engine. Plans tasks 3x daily (6 AM, 2 PM, 10 PM) and delivers them for approval. Execution happens in the main session via direct conversation. Night shifts auto-approve carryover from earlier in the day.","EverClaw\u002Fbuddybots.org","EverClaw","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F262691656?v=4","01M6RTE2R7A5898VSQ3HAZNTRN","01M6RTE2WCCGNTM8VWGPZY3NTT",0,"MIT","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fthree-shifts\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"three shifts","three","daily","approve","for","via","plans","pm","main","conversation","tasks","auto","approval","session","main session","direct","daily standup","engine","standup","execution","2026-11-10 10:12:30",false,"---\nname: three-shifts\ndescription: >\n  Daily standup engine. Plans tasks 3x daily (6 AM, 2 PM, 10 PM) and delivers\n  them for approval. Execution happens in the main session via direct conversation.\n  Night shifts auto-approve carryover from earlier in the day.\nversion: 3.0.0\n---\n\n# Three Shifts v3 — Daily Standup Engine\n\n**Architecture:** Plan 3x daily → deliver for approval → execute in main session.\n\n**Why v3:** V2 had a 15-minute autonomous cycle executor that never worked — state machine deadlocked for 19 days, burning ~27M tokens on no-ops. V3 removes it entirely. Plans are generated by cron, execution happens through normal conversation when the user approves.\n\n---\n\n## How It Works\n\n1. **Planner cron fires** (6 AM, 2 PM, 10 PM) — reads context, generates a prioritized task list\n2. **User reviews** — approves, modifies, or skips\n3. **Agent executes** in main session — when the user says \"go\" or gives specific instructions\n4. **Daily memory** captures what was done — next planner reads it for continuity\n\nNo file-based state machine. No autonomous executor. The main session IS the executor.\n\n---\n\n## File Structure\n\n```\nshifts\u002F\n├── tasks.md        # Current shift plan (generated by planner)\n├── context.md      # Stack, constraints, known pitfalls\n└── state.json      # Shift metadata (which shift, approval status)\n```\n\n### tasks.md\n\nGenerated by the planner each shift. This is a task list, not a state machine.\n\n```markdown\n# Morning Shift — 2026-03-13\nApproved by: user | Approved at: 6:15 AM CST\n\n## P1 (Must do)\n1. Fix bootstrap key server (keys.everclaw.xyz returning 404)\n2. Test installer on fresh Linux environment\n\n## P2 (Should do)\n3. Update MEMORY.md with yesterday's work\n4. Review open PRs across EverClaw repos\n\n## P3 (Could do)\n5. Memory file maintenance (archive >7 day old dailies)\n\n## Blocked\u002FWaiting\n- XMTP agent-to-agent — blocked on BASE_WALLET_PRIVATE_KEY\n```\n\n### state.json\n\nMinimal metadata for the planner to read between shifts:\n\n```json\n{\n  \"shift\": \"morning\",\n  \"date\": \"2026-03-13\",\n  \"status\": \"approved\",\n  \"approvedAt\": \"2026-03-13T06:15:00-05:00\",\n  \"approvedBy\": \"user\"\n}\n```\n\nStatus values: `planned` | `approved` | `skipped`\n\n### context.md\n\nLiving document of constraints and lessons. Updated by the agent when something new is learned.\n\n---\n\n## Shifts\n\n| Shift | Cron | Window | Character |\n|-------|------|--------|-----------|\n| Morning ☀️ | 6:00 AM | 6 AM – 2 PM | Comms, decisions, urgent items |\n| Afternoon ?️ | 2:00 PM | 2 PM – 10 PM | Deep work, building, coding |\n| Night ? | 10:00 PM | 10 PM – 6 AM | Research, maintenance, cleanup |\n\nAll times in user's local timezone.\n\n---\n\n## Planning Phase\n\n**Model:** `venice\u002Fkimi-k2-5` (cost-efficient, good at structured plans)\n\nSee `PLANNER.md` for the full planner instructions.\n\n### What the planner reads:\n- `shifts\u002Ftasks.md` — previous shift's plan (check for incomplete items)\n- `shifts\u002Fcontext.md` — rules, constraints, pitfalls\n- `shifts\u002Fstate.json` — previous shift metadata\n- `memory\u002Fdaily\u002FYYYY-MM-DD.md` — recent activity\n- `MEMORY.md` — active projects (⚡ Active Context section)\n\n### Plan format:\n\n```\n☀️\u002F?️\u002F? [SHIFT] SHIFT PLAN\nDate: [DATE] | Window: [START]–[END] CST\n\nP1 (Must do):\n1. [Task] — [Est. time] — [Why now]\n\nP2 (Should do):\n3. [Task] — [Est. time]\n\nP3 (Could do):\n5. [Task] — [Est. time]\n\nBlocked\u002FWaiting:\n- [Item] — [Blocker]\n\nReply: \"Approve\" \u002F \"Skip\" \u002F \"Add: [task]\"\n```\n\n### Carryover\n\nIf `shifts\u002Ftasks.md` has items from a previous shift that weren't completed:\n- Carry forward into the new plan, marked as `[carryover]`\n- Night shift: auto-approve carryover from morning\u002Fafternoon (no user ping)\n\n### Approval flow\n\n| User says | What happens |\n|-----------|-------------|\n| \"Approve\" | Plan written to tasks.md, state.json updated |\n| \"Add: [task]\" | Task added to plan, then approved |\n| \"Skip\" | State.json set to \"skipped\", next planner picks up |\n| No response (30 min) | Plan stays, next shift carries forward |\n\n---\n\n## Execution\n\nExecution happens in the **main session** through normal conversation. There is no autonomous executor.\n\nWhen the user approves a shift plan:\n- The agent works through the tasks in priority order\n- Progress is captured in `memory\u002Fdaily\u002FYYYY-MM-DD.md`\n- If interrupted by higher-priority work, remaining tasks carry over to the next shift\n\nThe planner's job is to **surface the right priorities** — not to control execution.\n\n---\n\n## Safety Rules\n\n### Always OK (any shift)\n- Reading files, organizing workspace\n- Research and analysis\n- Code review, documentation\n- Memory updates, planning\n- Git status, non-destructive commands\n\n### Requires Approval (via shift plan)\n- Sending emails, messages, social posts\n- Creating PRs, pushing code\n- Financial transactions\n- Any external-facing action\n\n### Night Shift Constraints\n- No external communications (Signal, email, social)\n- No financial transactions\n- No destructive operations (rm, force push, branch delete)\n- No security changes (key rotation, permissions)\n- P3 maintenance tasks (memory, cleanup, docs) are OK autonomous\n\n---\n\n## Cron Setup\n\nThree planner jobs. No executor job.\n\n```\nMorning ☀️:    cron 0 6 * * * (America\u002FChicago)\nAfternoon ?️:  cron 0 14 * * * (America\u002FChicago)\nNight ?:      cron 0 22 * * * (America\u002FChicago)\n```\n\nAll use `venice\u002Fkimi-k2-5`, isolated sessions, deliver via Signal.\n\nSee `references\u002Fconfig.md` for customizing schedule, models, and weekend behavior.\n\n---\n\n## Version History\n\n- **v3.0.0** (2026-03-13) — Removed broken cycle executor. Simplified to daily standup engine. Plans generated by cron, execution in main session.\n- **v2.0.0** (2026-02-27) — Added 15-minute cycle executor (state machine). Never worked — state deadlock caused 1,527 no-op runs over 19 days.\n- **v1.0.0** (2026-02-22) — Single long session per shift. Timeouts killed entire shifts.\n","# Three Shifts v3 — Daily Standup Engine\n\n**Architecture:** Plan 3x daily → deliver for approval → execute in main session.\n\n**Why v3:** V2 had a 15-minute autonomous cycle executor that never worked — state machine deadlocked for 19 days, burning ~27M tokens on no-ops. V3 removes it entirely. Plans are generated by cron, execution happens through normal conversation when the user approves.\n\n---\n\n## How It Works\n\n1. **Planner cron fires** (6 AM, 2 PM, 10 PM) — reads context, generates a prioritized task list\n2. **User reviews** — approves, modifies, or skips\n3. **Agent executes** in main session — when the user says \"go\" or gives specific instructions\n4. **Daily memory** captures what was done — next planner reads it for continuity\n\nNo file-based state machine. No autonomous executor. The main session IS the executor.\n\n---\n\n## File Structure\n\n```\nshifts\u002F\n├── tasks.md        # Current shift plan (generated by planner)\n├── context.md      # Stack, constraints, known pitfalls\n└── state.json      # Shift metadata (which shift, approval status)\n```\n\n### tasks.md\n\nGenerated by the planner each shift. This is a task list, not a state machine.\n\n```markdown\n# Morning Shift — 2026-03-13\nApproved by: user | Approved at: 6:15 AM CST\n\n## P1 (Must do)\n1. Fix bootstrap key server (keys.everclaw.xyz returning 404)\n2. Test installer on fresh Linux environment\n\n## P2 (Should do)\n3. Update MEMORY.md with yesterday's work\n4. Review open PRs across EverClaw repos\n\n## P3 (Could do)\n5. Memory file maintenance (archive >7 day old dailies)\n\n## Blocked\u002FWaiting\n- XMTP agent-to-agent — blocked on BASE_WALLET_PRIVATE_KEY\n```\n\n### state.json\n\nMinimal metadata for the planner to read between shifts:\n\n```json\n{\n  \"shift\": \"morning\",\n  \"date\": \"2026-03-13\",\n  \"status\": \"approved\",\n  \"approvedAt\": \"2026-03-13T06:15:00-05:00\",\n  \"approvedBy\": \"user\"\n}\n```\n\nStatus values: `planned` | `approved` | `skipped`\n\n### context.md\n\nLiving document of constraints and lessons. Updated by the agent when something new is learned.\n\n---\n\n## Shifts\n\n| Shift | Cron | Window | Character |\n|-------|------|--------|-----------|\n| Morning ☀️ | 6:00 AM | 6 AM – 2 PM | Comms, decisions, urgent items |\n| Afternoon ?️ | 2:00 PM | 2 PM – 10 PM | Deep work, building, coding |\n| Night ? | 10:00 PM | 10 PM – 6 AM | Research, maintenance, cleanup |\n\nAll times in user's local timezone.\n\n---\n\n## Planning Phase\n\n**Model:** `venice\u002Fkimi-k2-5` (cost-efficient, good at structured plans)\n\nSee `PLANNER.md` for the full planner instructions.\n\n### What the planner reads:\n- `shifts\u002Ftasks.md` — previous shift's plan (check for incomplete items)\n- `shifts\u002Fcontext.md` — rules, constraints, pitfalls\n- `shifts\u002Fstate.json` — previous shift metadata\n- `memory\u002Fdaily\u002FYYYY-MM-DD.md` — recent activity\n- `MEMORY.md` — active projects (⚡ Active Context section)\n\n### Plan format:\n\n```\n☀️\u002F?️\u002F? [SHIFT] SHIFT PLAN\nDate: [DATE] | Window: [START]–[END] CST\n\nP1 (Must do):\n1. [Task] — [Est. time] — [Why now]\n\nP2 (Should do):\n3. [Task] — [Est. time]\n\nP3 (Could do):\n5. [Task] — [Est. time]\n\nBlocked\u002FWaiting:\n- [Item] — [Blocker]\n\nReply: \"Approve\" \u002F \"Skip\" \u002F \"Add: [task]\"\n```\n\n### Carryover\n\nIf `shifts\u002Ftasks.md` has items from a previous shift that weren't completed:\n- Carry forward into the new plan, marked as `[carryover]`\n- Night shift: auto-approve carryover from morning\u002Fafternoon (no user ping)\n\n### Approval flow\n\n| User says | What happens |\n|-----------|-------------|\n| \"Approve\" | Plan written to tasks.md, state.json updated |\n| \"Add: [task]\" | Task added to plan, then approved |\n| \"Skip\" | State.json set to \"skipped\", next planner picks up |\n| No response (30 min) | Plan stays, next shift carries forward |\n\n---\n\n## Execution\n\nExecution happens in the **main session** through normal conversation. There is no autonomous executor.\n\nWhen the user approves a shift plan:\n- The agent works through the tasks in priority order\n- Progress is captured in `memory\u002Fdaily\u002FYYYY-MM-DD.md`\n- If interrupted by higher-priority work, remaining tasks carry over to the next shift\n\nThe planner's job is to **surface the right priorities** — not to control execution.\n\n---\n\n## Safety Rules\n\n### Always OK (any shift)\n- Reading files, organizing workspace\n- Research and analysis\n- Code review, documentation\n- Memory updates, planning\n- Git status, non-destructive commands\n\n### Requires Approval (via shift plan)\n- Sending emails, messages, social posts\n- Creating PRs, pushing code\n- Financial transactions\n- Any external-facing action\n\n### Night Shift Constraints\n- No external communications (Signal, email, social)\n- No financial transactions\n- No destructive operations (rm, force push, branch delete)\n- No security changes (key rotation, permissions)\n- P3 maintenance tasks (memory, cleanup, docs) are OK autonomous\n\n---\n\n## Cron Setup\n\nThree planner jobs. No executor job.\n\n```\nMorning ☀️:    cron 0 6 * * * (America\u002FChicago)\nAfternoon ?️:  cron 0 14 * * * (America\u002FChicago)\nNight ?:      cron 0 22 * * * (America\u002FChicago)\n```\n\nAll use `venice\u002Fkimi-k2-5`, isolated sessions, deliver via Signal.\n\nSee `references\u002Fconfig.md` for customizing schedule, models, and weekend behavior.\n\n---\n\n## Version History\n\n- **v3.0.0** (2026-03-13) — Removed broken cycle executor. Simplified to daily standup engine. Plans generated by cron, execution in main session.\n- **v2.0.0** (2026-02-27) — Added 15-minute cycle executor (state machine). Never worked — state deadlock caused 1,527 no-op runs over 19 days.\n- **v1.0.0** (2026-02-22) — Single long session per shift. Timeouts killed entire shifts.\n",{"name":5,"version":43,"description":44},"3.0.0","Daily standup engine. Plans tasks 3x daily (6 AM, 2 PM, 10 PM) and delivers them for approval. Execution happens in the main session via direct conversation. Night shifts auto-approve carryover from earlier in the day.\n","b15f4b37683ab5d816814787927959993ef4398c","skills\u002Fthree-shifts","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org","https:\u002F\u002Fgithub.com\u002FEverClaw","https:\u002F\u002Feverclaw.xyz","AI Inference You Own, Forever Powering Your OpenClaw Agents. Open-source skill connecting OpenClaw to the Morpheus decentralized inference network — GLM-5","2026-09-02 03:56:55",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add EverClaw\u002Fbuddybots.org --skill three-shifts",{"tool":58,"command":59},"bunx","bunx skills add EverClaw\u002Fbuddybots.org --skill three-shifts",{"tool":61,"command":62},"pnpm","pnpm dlx skills add EverClaw\u002Fbuddybots.org --skill three-shifts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fthree-shifts\u002FSKILL.md",true,[66,72,76],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"PLANNER.md","REFERENCE","参考文档",1754,"https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fthree-shifts\u002FPLANNER.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fconfig.md",2025,"https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fthree-shifts\u002Freferences\u002Fconfig.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fcycle-executor-v2.md",1573,"https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fthree-shifts\u002Freferences\u002Fcycle-executor-v2.md",[81,99,125,136,151,168],{"skillNo":82,"name":5,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":38},"01M6RTQW04G5PH8910S8PTD85W","Cyclic shift execution engine. Plans tasks 3x daily (6 AM, 2 PM, 10 PM), decomposes them into granular steps, then executes via 15-minute cron cycles. Each cycle reads state files, picks the next step, executes it, writes results back. Errors are logged and skipped — never fatal. Planning uses Claude 4.6; execution uses GLM-5.","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fthree-shifts\u002FSKILL.md",[],[19,18,87,37,88,89,90,28,35,91,92,20,93,94,95,96,25,24,97,98],"cron","errors","state","planning","results","never","files","back","cycle","next","glm","next step",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":38},"01M6RTQM0PCGTCKCZCK312PAWJ","xmtp-comms-guard","Security middleware for all XMTP communications in EverClaw. Enforces guarded client usage with validation, integrity checks, and fail-closed security policies. Integrates approval flows for sensitive operations. Use when integrating XMTP messaging, configuring communication security, or auditing guarded client enforcement.","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fxmtp-comms-guard\u002FSKILL.md",[],[106,107,108,109,110,111,112,22,113,114,115,116,117,118,119,120,121,122,123,124],"guard","comms","xmtp comms guard","with","usage","when","everclaw","flows","integrity checks","validation","communication","messaging","integrity","operations","use","enforcement","client","communications","middleware",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":38},"01M6RTPV7ZWGV38QFAMG5RXEDJ","super-helper","A helpful utility skill for agents","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fskillguard\u002Ftest-fixtures\u002Fmalicious-skill\u002FSKILL.md",[],[132,133,134,135,22],"super","helper","super helper","utility",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":38},"01M6RTPRM3GE8G43WD72BZK4Q7","github-issues","Fetch and manage GitHub issues via the API","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fskillguard\u002Ftest-fixtures\u002Flegit-api-skill\u002FSKILL.md",[],[143,144,145,146,147,148,149,150,23],"issues","github issues","github","api","curl","fetch","manage","token",{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":162,"publishedAt":38},"01M6RTPME21Z0A1JF8BV6KTZT3","code-formatter","Format and lint code files","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fskillguard\u002Ftest-fixtures\u002Fevasive-12-multi-stage\u002FSKILL.md",[157],{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[163,164,165,166,167,93],"formatter","code formatter","code","lint","format",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"publishedAt":38},"01M6RTP2QZWN8PZ8HK4GND3D78","config-helper","Parse and validate configuration files","https:\u002F\u002Fgithub.com\u002FEverClaw\u002Fbuddybots.org\u002Fblob\u002Fmain\u002Fskills\u002Fskillguard\u002Ftest-fixtures\u002Fevasive-11-polyglot-json\u002FSKILL.md",[],[175,133,176,177,93,178,179],"config","config helper","validate","configuration","parse"]