Daily standup engine. An agent skill from profbernardoj/everclaw-community-branches.

MITAuto-check passedProductivity & Automation

Install Three Shifts

skills CLI
$ npx skills add profbernardoj/everclaw-community-branches --skill three-shifts -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install profbernardoj/everclaw-community-branches three-shifts --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/three-shifts .claude/skills/three-shifts && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
three-shifts
GitHub stars
112
Token cost
~1.5k tokens
SKILL.md length
550 words
Files
4 (incl. references)
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Daily standup engine. An agent skill from profbernardoj/everclaw-community-branches.

  • Works in 4 steps: Planner cron fires (6 AM, 2 PM, 10 PM) —… → User reviews — approves, modifies, or… → Agent executes in main session — when… → …
  • Tasks that involve Meeting notes and agendas
  • SKILL.md covers How It Works, File Structure, Shifts and Planning Phase, plus 4 more sections
  • Needs BASE_WALLET_PRIVATE_KEY

What it does

Three Shifts is an agent skill from profbernardoj/everclaw-community-branches. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `PLANNER.md`, `references/config.md` and `references/cycle-executor-v2.md`).

It sits in Productivity & Automation, covering Meeting notes and agendas. The repository describes itself as: Decentralized AI inference for OpenClaw agents. Powered by Morpheus AI. Stake MOR, access Kimi K2.5 + 10 models, never run out of inference. The licence is MIT.

When your agent uses it

  • Tasks that involve Meeting notes and agendas

Example prompts

  • “/three-shifts”

Requirements

  • A credential in BASE_WALLET_PRIVATE_KEY

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Planner cron fires (6 AM, 2 PM, 10 PM) — reads context, generates a prioritized task list
  2. User reviews — approves, modifies, or skips
  3. Agent executes in main session — when the user says "go" or gives specific instructions
  4. Daily memory captures what was done — next planner reads it for continuity

What it can do on your machine

Read from SKILL.md and the folder at commit 0b30b36. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • BASE_WALLET_PRIVATE_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Three Shifts loads about 1.5k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 58 tokens; SKILL.md has 550 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~58
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~2.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from profbernardoj/everclaw-community-branches at commit 0b30b36, republished under its MIT licence (© profbernardoj). 550 words, ~1,461 tokens.

Download SKILL.mdSave it as .claude/skills/three-shifts/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
three-shifts
description
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.
version
3.0.0

Three Shifts v3 — Daily Standup Engine

Architecture: Plan 3x daily → deliver for approval → execute in main session.

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.


How It Works

  1. Planner cron fires (6 AM, 2 PM, 10 PM) — reads context, generates a prioritized task list
  2. User reviews — approves, modifies, or skips
  3. Agent executes in main session — when the user says "go" or gives specific instructions
  4. Daily memory captures what was done — next planner reads it for continuity

No file-based state machine. No autonomous executor. The main session IS the executor.


File Structure

shifts/
├── tasks.md        # Current shift plan (generated by planner)
├── context.md      # Stack, constraints, known pitfalls
└── state.json      # Shift metadata (which shift, approval status)
tasks.md

Generated by the planner each shift. This is a task list, not a state machine.

markdown
# Morning Shift — 2026-03-13
Approved by: user | Approved at: 6:15 AM CST

## P1 (Must do)
1. Fix bootstrap key server (keys.everclaw.xyz returning 404)
2. Test installer on fresh Linux environment

## P2 (Should do)
3. Update MEMORY.md with yesterday's work
4. Review open PRs across EverClaw repos

## P3 (Could do)
5. Memory file maintenance (archive >7 day old dailies)

## Blocked/Waiting
- XMTP agent-to-agent — blocked on BASE_WALLET_PRIVATE_KEY
state.json

Minimal metadata for the planner to read between shifts:

json
{
  "shift": "morning",
  "date": "2026-03-13",
  "status": "approved",
  "approvedAt": "2026-03-13T06:15:00-05:00",
  "approvedBy": "user"
}

Status values: planned | approved | skipped

context.md

Living document of constraints and lessons. Updated by the agent when something new is learned.


Shifts

ShiftCronWindowCharacter
Morning ☀️6:00 AM6 AM – 2 PMComms, decisions, urgent items
Afternoon 🌤️2:00 PM2 PM – 10 PMDeep work, building, coding
Night 🌙10:00 PM10 PM – 6 AMResearch, maintenance, cleanup

All times in user's local timezone.


Planning Phase

Model: venice/kimi-k2-5 (cost-efficient, good at structured plans)

See PLANNER.md for the full planner instructions.

What the planner reads:
  • shifts/tasks.md — previous shift's plan (check for incomplete items)
  • shifts/context.md — rules, constraints, pitfalls
  • shifts/state.json — previous shift metadata
  • memory/daily/YYYY-MM-DD.md — recent activity
  • MEMORY.md — active projects (⚡ Active Context section)
Plan format:
☀️/🌤️/🌙 [SHIFT] SHIFT PLAN
Date: [DATE] | Window: [START]–[END] CST

P1 (Must do):
1. [Task] — [Est. time] — [Why now]

P2 (Should do):
3. [Task] — [Est. time]

P3 (Could do):
5. [Task] — [Est. time]

Blocked/Waiting:
- [Item] — [Blocker]

Reply: "Approve" / "Skip" / "Add: [task]"
Carryover

If shifts/tasks.md has items from a previous shift that weren't completed:

  • Carry forward into the new plan, marked as [carryover]
  • Night shift: auto-approve carryover from morning/afternoon (no user ping)
Approval flow
User saysWhat happens
"Approve"Plan written to tasks.md, state.json updated
"Add: [task]"Task added to plan, then approved
"Skip"State.json set to "skipped", next planner picks up
No response (30 min)Plan stays, next shift carries forward

Show full SKILL.md (215 more words)Show less

Execution

Execution happens in the main session through normal conversation. There is no autonomous executor.

When the user approves a shift plan:

  • The agent works through the tasks in priority order
  • Progress is captured in memory/daily/YYYY-MM-DD.md
  • If interrupted by higher-priority work, remaining tasks carry over to the next shift

The planner's job is to surface the right priorities — not to control execution.


Safety Rules

Always OK (any shift)
  • Reading files, organizing workspace
  • Research and analysis
  • Code review, documentation
  • Memory updates, planning
  • Git status, non-destructive commands
Requires Approval (via shift plan)
  • Sending emails, messages, social posts
  • Creating PRs, pushing code
  • Financial transactions
  • Any external-facing action
Night Shift Constraints
  • No external communications (Signal, email, social)
  • No financial transactions
  • No destructive operations (rm, force push, branch delete)
  • No security changes (key rotation, permissions)
  • P3 maintenance tasks (memory, cleanup, docs) are OK autonomous

Cron Setup

Three planner jobs. No executor job.

Morning ☀️:    cron 0 6 * * * (America/Chicago)
Afternoon 🌤️:  cron 0 14 * * * (America/Chicago)
Night 🌙:      cron 0 22 * * * (America/Chicago)

All use venice/kimi-k2-5, isolated sessions, deliver via Signal.

See references/config.md for customizing schedule, models, and weekend behavior.


Version History

  • v3.0.0 (2026-03-13) — Removed broken cycle executor. Simplified to daily standup engine. Plans generated by cron, execution in main session.
  • 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.
  • v1.0.0 (2026-02-22) — Single long session per shift. Timeouts killed entire shifts.

© profbernardoj, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/three-shifts of profbernardoj/everclaw-community-branches.

  • SKILL.md
  • PLANNER.md
  • references/config.md
  • references/cycle-executor-v2.md

Open the folder on GitHubat commit 0b30b36

Compare with similar skills

Three Shifts next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Three Shifts compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Three Shifts this skillprofbernardoj/everclaw-community-branches112—~1.5kAutomated safety check: PassMIT
Meeting Notesoutline/outline41k—~551Automated safety check: PassCustom licence
Management Talkthananon/9arm-skills3.2k—~3.2kAutomated safety check: PassNone
Challenge Baseline ModelAgibotTech/genie_sim1.4k—~2.4kAutomated safety check: PassCustom licence
Handwriting Stand Uplimin112/min-skill412—~2.5kAutomated safety check: PassNone
Daily Journalravila4/claude-adhd-skills157—~2.5kAutomated safety check: PassMIT

Similar skills

  • Meeting Notes

    outline/outline

    Create meeting notes in Outline from a template; use when the user wants an agenda, notes, or a follow-up document for a meeting.

    41k GitHub stars~551 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Management Talk

    thananon/9arm-skills

    Rewrite engineer-to-engineer content for engineering-org leadership (VPs, directors, PMs, release managers, execs in an engineering-savvy company) and shape it for the channel it is going to — JIRA…

    3.2k GitHub stars~3.2k tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check passed
  • Challenge Baseline Model

    AgibotTech/genie_sim

    Provision and launch the Simulation Challenge baseline inference model end to end: clone the inference code from a given git repo/branch, download the checkpoints from ModelScope into the repo's…

    1.4k GitHub stars~2.4k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check passed
  • Handwriting Stand Up

    limin112/min-skill

    Turn a screen recording of handwriting (or a photo of handwritten text) into a single-file HTML "continuation" — the recording plays, the ink lifts off the page as solid 3D letters, a short animated…

    412 GitHub stars~2.5k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Daily Journal

    ravila4/claude-adhd-skills

    Draft, organize, or update development journal entries. An agent skill from ravila4/claude-adhd-skills.

    157 GitHub stars~2.5k tokensUpdated 7 mo ago
    Productivity & AutomationAuto-check passed
  • Granola

    ArtemXTech/claude-code-obsidian-starter

    Query and sync Granola meetings to Obsidian vault. An agent skill from ArtemXTech/claude-code-obsidian-starter.

    224 GitHub stars~905 tokensUpdated 4 days ago
    Productivity & AutomationAuto-check passed

More from profbernardoj/everclaw-community-branches

All 12 skills in this repo
  • Memory Upgrade

    profbernardoj/everclaw-community-branches

    Diagnose and fix broken memory search in OpenClaw. An agent skill from profbernardoj/everclaw-community-branches.

    112 GitHub stars~574 tokensUpdated 1 mo ago
    Auto-check passed
  • Relationships

    profbernardoj/everclaw-community-branches

    Relationship CRM for tracking people, connections, and context.

    112 GitHub stars~765 tokensUpdated 1 mo ago
    Auto-check passed
  • Agent Chat

    profbernardoj/everclaw-community-branches

    XMTP real-time agent-to-agent and user-to-agent encrypted messaging daemon for EverClaw.

    112 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check: notes
  • Bagman

    profbernardoj/everclaw-community-branches

    Secure key management for AI agents. An agent skill from profbernardoj/everclaw-community-branches.

    112 GitHub stars~4.4k tokensUpdated 1 mo ago
    Auto-check: warnings
  • Night Shift

    profbernardoj/everclaw-community-branches

    Automated overnight task planning and execution engine for EverClaw.

    112 GitHub stars~1.2k tokensUpdated 1 mo ago
    Auto-check passed
  • Pii Guard

    profbernardoj/everclaw-community-branches

    Personally identifiable information (PII) leak prevention for EverClaw.

    112 GitHub stars~921 tokensUpdated 1 mo ago
    Auto-check passed

Questions about Three Shifts

What does Three Shifts do?

Daily standup engine. An agent skill from profbernardoj/everclaw-community-branches. Three Shifts is an agent skill from profbernardoj/everclaw-community-branches. Daily standup engine.

When should I use Three Shifts?

Three Shifts fits situations like: tasks that involve Meeting notes and agendas.

How do I install Three Shifts in Claude Code?

Run `npx skills add profbernardoj/everclaw-community-branches --skill three-shifts -a claude-code`. Or copy the skill folder (skills/three-shifts in profbernardoj/everclaw-community-branches) into .claude/skills/three-shifts in your project. Claude Code loads it when a task matches its description.

How do I install Three Shifts in Codex?

Run `npx skills add profbernardoj/everclaw-community-branches --skill three-shifts -a codex`. Or copy the skill folder (skills/three-shifts in profbernardoj/everclaw-community-branches) into .agents/skills/three-shifts in your project. Codex loads it when a task matches its description.

Can I use Three Shifts in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add profbernardoj/everclaw-community-branches --skill three-shifts -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/three-shifts, .gemini/skills/three-shifts, .github/skills/three-shifts and .opencode/skills/three-shifts in your project.

What does Three Shifts need to run?

Going by SKILL.md and its folder, Three Shifts needs credentials named BASE_WALLET_PRIVATE_KEY. Our summary lists: A credential in BASE_WALLET_PRIVATE_KEY.

Does Three Shifts access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Three Shifts safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Three Shifts use?

Three Shifts is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Three Shifts use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 900 tokens, read only when the agent opens those files.

What are the alternatives to Three Shifts?

Skills that share tags, products or a category with Three Shifts: Meeting Notes (outline/outline, 41k stars), Management Talk (thananon/9arm-skills, 3.2k stars), Challenge Baseline Model (AgibotTech/genie_sim, 1.4k stars) and Handwriting Stand Up (limin112/min-skill, 412 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Three Shifts?

profbernardoj (a GitHub user) maintains it in profbernardoj/everclaw-community-branches, which has 112 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 2, 2026.

Source: profbernardoj/everclaw-community-branches on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.