Token导航 LogoToken导航

Agent Skill · 研究检索

plan-my-day(计划我的一天)

plan-my-day 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

plan-my-day 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 38,018。

总安装 1,630周安装 70GitHub Stars 261下载 571核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:plan-my-day(计划我的一天)
来源仓库:https://github.com/brianrwagner/ai-marketing-claude-code-skills
仓库路径:skills/plan-my-day
安装命令:
npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill plan-my-day
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill plan-my-day

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

plan-my-day 基于优先级与精力模式生成小时级行动计划,提升日常执行效率。适用于在 Codex、Claude、Cursor、Gemini CLI 中优化时间分配与重点任务聚焦。支持快速优先排序或完整日程构建,适配灵活工作安排与深度工作时间需求。输出包含能量波动分析与周计划建议,帮助用户建立可持续工作节奏。

建议每日早晨使用并根据实际情况动态调整,避免机械照搬导致疲劳累积。

来源仓库内路径:skills/plan-my-day

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills -…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

plan-my-day 怎么安装?

在终端执行 npx skills add https://github.com/brianrwagner/ai-marketing-claude-code-skills --skill pla…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

plan-my-day 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

plan-my-day 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

plan-my-day 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

plan-my-day 用的人多吗?

公开数据是累计安装 1,630 次,近一周安装 70 次,下载 571 次,GitHub 261 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

plan-my-day 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
plan-my-day

计划我的一天 · 本页

1,630261只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Plan My Day

Generate a clean, actionable hour-by-hour plan for the day based on priorities, energy patterns, and constraints.

Mode

Detect from context or ask: *"Quick priorities, full day plan, or full plan + weekly structure?"*

ModeWhat you getBest for
quickTop 3 priorities + rough time blocks, 2 minMorning sprint, already know the day
standardFull hour-by-hour energy-optimized planDefault daily planning
deepFull plan + energy pattern analysis + weekly structure recommendationsOverhauling your schedule, high-performance week

Default: standard — use quick if they say "just help me prioritize." Use deep if they want to rethink their week, not just plan today.


Why This vs ChatGPT?

Problem with "just asking": You get a different plan each time. No consistency, no memory of what works, no optimization over time.

This skill provides:

  1. Consistent methodology - Same decision framework every day (Top 3 priorities, energy windows, buffer rules)
  2. Energy-aware scheduling - Automatically matches high-cognitive tasks to your peak hours
  3. Constraint-aware - Respects your existing calendar, energy patterns, personal boundaries
  4. Learning memory - Can track what scheduling patterns work best for you over time
  5. Evening reflection built-in - Forces accountability on what actually got done

You can replicate this by writing the same detailed prompt every day, manually checking your calendar, remembering your energy patterns, and tracking completion rates. Or use this skill in 2 minutes.

Usage

/plan-my-day [optional: YYYY-MM-DD for future date]

With custom energy profile:

/plan-my-day --peak 9-11,14-16 --recovery 13-14

Planning Principles (Research-Backed)

  1. Circadian optimization - Cognitive performance peaks ~2-3 hours after waking (Roenneberg, 2012)
  2. Ultradian rhythms - Work in 90-minute blocks with 15-20 minute breaks (Ericsson, 1993)
  3. Decision fatigue prevention - Schedule high-stakes decisions before 3pm (Kahneman, 2011)
  4. Implementation intentions - Specific time+task combinations increase completion by 2-3× (Gollwitzer, 1999)

Energy Windows (Default - Customize Yours)

Peak Performance (Morning): 9:00 AM - 12:00 PM

  • Deep work, strategic thinking, complex problem-solving
  • Highest cognitive capacity
  • Schedule your #1 priority here

Secondary Peak (Afternoon): 2:00 PM - 4:00 PM

  • Focused work, meetings with decisions, creative work
  • Still high capacity but slightly lower than morning

Administrative (Late Afternoon): 4:00 PM - 6:00 PM

  • Email processing, light tasks, 1-on-1s, planning
  • Lower energy, avoid complex decisions

Recovery Blocks: 12:00 PM - 1:00 PM, 6:00 PM+

  • Meals, exercise, walks, recharge
  • Non-negotiable for sustained performance

Wind Down (Evening): After 7:00 PM

  • Reflection, reading, light planning for tomorrow
  • No high-cognitive work

Process

1. Gather Context (30 seconds)

  • Check existing calendar events
  • Review yesterday's incomplete tasks
  • Identify any fixed commitments or deadlines
  • Note current project priorities

2. Identify Top 3 Priorities (60 seconds)

Ask for each potential priority:

  • Impact: Does this move a key metric or deadline?
  • Urgency: Must it happen today?
  • Effort: Can I complete it in available time?

Filter: Pick the 3 with highest impact×urgency score

3. Build Time-Blocked Schedule (90 seconds)

Sequencing logic:

  1. Place fixed commitments (meetings, calls) first
  2. Assign Priority #1 to longest peak energy block
  3. Assign Priority #2 to secondary peak or next available
  4. Assign Priority #3 to remaining focused time
  5. Add 20-minute buffers between major blocks
  6. Schedule admin work (email, Slack) in low-energy windows
  7. Protect breaks and meals (non-negotiable)

Buffer rule: Only schedule 80% of available time

4. Apply Constraints

  • Personal boundaries: No work before 8am or after 7pm (customize)
  • Meeting limits: Max 4 hours of meetings per day
  • Focus blocks: Minimum 90 minutes for deep work (no interruptions)
  • Break enforcement: 15-minute break every 90 minutes

Output Format

# Daily Plan - [Day], [Month] [Date], [Year]

## Today's Mission

**Primary Goal:** [One-sentence outcome for the day]

**Top 3 Priorities:**
1. [Priority 1 with specific, measurable outcome]
2. [Priority 2 with specific, measurable outcome]
3. [Priority 3 with specific, measurable outcome]

**Success looks like:** [What "done" means today]

---

## Time-Blocked Schedule

### 8:00 - 9:00: Morning Prime 🌅
**Focus:** Wake up, coffee, light movement, review plan

- [ ] Morning routine (30 min)
- [ ] Review today's plan + priorities (10 min)
- [ ] Quick inbox scan (15 min - flag only, don't respond)

**Energy level:** Building

---

### 9:00 - 11:00: Deep Work Block 1 🎯 [PRIORITY #1]
**Focus:** [Specific priority 1 task]

- [ ] [Concrete subtask 1]
- [ ] [Concrete subtask 2]
- [ ] [Concrete subtask 3]

**Target:** [Measurable outcome by 11:00]

**Protection:** Phone off, Slack paused, door closed

---

### 11:00 - 11:15: Break ☕
**Focus:** Step away from desk

- Physical movement (walk, stretch)
- Hydrate
- No screens

---

### 11:15 - 12:30: Deep Work Block 2 🎯 [PRIORITY #2]
**Focus:** [Specific priority 2 task]

- [ ] [Concrete subtask 1]
- [ ] [Concrete subtask 2]

**Target:** [Measurable outcome by 12:30]

---

### 12:30 - 1:30: Lunch Break 🍽️
**Focus:** Eat, recharge, disconnect

- Proper meal (not at desk)
- 15-minute walk if possible
- No work talk

**Energy level:** Recovery

---

### 1:30 - 3:00: Focused Work Block 🎯 [PRIORITY #3]
**Focus:** [Specific priority 3 task]

- [ ] [Concrete subtask 1]
- [ ] [Concrete subtask 2]

**Target:** [Measurable outcome by 3:00]

---

### 3:00 - 3:15: Break ☕
**Focus:** Recharge

---

### 3:15 - 4:30: Meetings / Collaborative Work 👥
**Focus:** [Meeting name or collaborative task]

- [ ] [Meeting 1 with agenda]
- [ ] [Follow-up actions from meetings]

**Prep:** Review agendas 10 minutes before

---

### 4:30 - 5:30: Admin & Communication 📧
**Focus:** Process inbox, respond to messages, light tasks

- [ ] Clear email inbox (respond, archive, defer)
- [ ] Slack catch-up and responses
- [ ] Update project trackers
- [ ] Quick wins / small tasks

**Energy level:** Lower (perfect for admin)

---

### 5:30 - 6:00: Planning & Wrap-Up 📋
**Focus:** Close the day, plan tomorrow

- [ ] Evening check-in (see below)
- [ ] Tomorrow's top 3 priorities draft
- [ ] Inbox zero for peace of mind
- [ ] Close all work apps

---

### 6:00 PM+: Personal Time 🏡
**No work beyond this point**

---

## Success Criteria

### Must-Have (Non-Negotiable) ✓
- [ ] Priority 1 complete: [Specific outcome]
- [ ] Priority 2 complete: [Specific outcome]
- [ ] At least 80% progress on Priority 3

### Should-Have (Important) ⭐
- [ ] [Secondary task 1]
- [ ] [Secondary task 2]

### Nice-to-Have (Bonus) 💡
- [ ] [Bonus task 1]
- [ ] [Bonus task 2]

---

## Evening Check-In (5 minutes at 5:30 PM)

**Completion status:**
- Priority 1 done? **YES / NO** - [If no, why?]
- Priority 2 done? **YES / NO** - [If no, why?]
- Priority 3 done? **YES / NO** - [If no, why?]

**What went well:**
[What worked today? What helped you execute?]

**What got stuck:**
[Where did you lose time? What blocked you?]

**Energy assessment:**
- Peak hours productive? **YES / NO**
- Breaks taken? **YES / NO**
- Felt energized or drained? **[Score 1-10]**

**Tomorrow's adjustment:**
[What to change in tomorrow's plan based on today?]

---

## Quick Decision Framework

**Before saying YES to anything today:**

1. **Is this one of my top 3 priorities?**
   - YES → Schedule it in appropriate energy window
   - NO → Go to #2

2. **Does this directly support today's mission?**
   - YES → Add to relevant time block
   - NO → Go to #3

3. **Can this wait until tomorrow?**
   - YES → Add to tomorrow's list
   - NO → Question if it's really urgent

**If NO to all three → Decline or defer**

---

Real Examples

Example 1: High-Output Day (Founder/Exec)

Context: Product launch week, high-stakes demos, team coordination

## Top 3 Priorities:
1. Finalize launch announcement (900 words, 3 versions) - DONE by 11:30
2. Run partner demo with clear next steps - DONE by 3:00
3. Team sprint planning with Q2 priorities set - DONE by 5:00

## Schedule:
- 9:00-11:30: Deep work → Launch copy (Priority #1)
- 12:30-2:45: Partner demo prep + execution (Priority #2)
- 3:00-4:45: Sprint planning with team (Priority #3)
- 5:00-5:30: Email/admin/wrap

## Evening Check-In:
✓ Priority 1: YES (shipped 3 versions, CEO approved)
✓ Priority 2: YES (partner committed, contract signed)
✓ Priority 3: YES (team aligned, stories pointed)

What worked: Protected deep work time for writing, prepped demo thoroughly
Tomorrow: Start execution on sprint, less coordination overhead

Example 2: Deep Work Day (Individual Contributor)

Context: IC developer, needs 6+ hours of uninterrupted coding

## Top 3 Priorities:
1. Ship authentication refactor (PR ready for review) - DONE by 12:00
2. Debug production issue #847 (root cause found + fix deployed) - DONE by 4:00
3. Documentation for new API endpoints (published) - DONE by 6:00

## Schedule:
- 9:00-12:00: Deep work → Auth refactor (Priority #1)
- 1:00-4:00: Deep work → Debug + deploy (Priority #2)
- 4:15-5:45: Documentation writing (Priority #3)
- 5:45-6:00: Update tickets, close day

## Protections:
- Slack: Paused 9am-12pm, 1pm-4pm
- No meetings scheduled
- Phone: DND mode

## Evening Check-In:
✓ Priority 1: YES (PR approved, merged)
✓ Priority 2: YES (issue resolved, monitoring green)
✓ Priority 3: 90% (docs drafted, needs final review tomorrow)

What worked: Zero meetings = maximum flow state
Tomorrow: Finish docs, start new feature work

Example 3: Meeting-Heavy Day (Manager/Director)

Context: Leadership role, multiple teams, coordination day

## Top 3 Priorities:
1. Align exec team on Q2 budget priorities - DONE by 11:00
2. Resolve team conflict (performance conversation) - DONE by 3:00
3. Approve 3 critical design reviews - DONE by 5:30

## Schedule:
- 8:30-9:00: Pre-meeting prep (agendas, talking points)
- 9:00-11:00: Exec budget meeting (Priority #1)
- 11:15-12:15: 1-on-1 performance conversation (Priority #2)
- 1:30-3:00: Design review meetings (Priority #3, all 3 back-to-back)
- 3:15-4:30: Email/admin/follow-ups from meetings
- 4:30-5:00: Next week prep + team updates

## Evening Check-In:
✓ Priority 1: YES (budget approved, owners assigned)
✓ Priority 2: YES (performance plan agreed, follow-up scheduled)
✓ Priority 3: YES (2 approved, 1 needs revision)

What got stuck: Back-to-back meetings = no thinking time
Tomorrow: Block 2-hour deep work window, fewer meetings

Real Case Study

User: Marketing manager at B2B SaaS company, struggled with reactive days

Before using skill:

  • Average day: 6-8 hours in meetings, 2 hours of "work" squeezed in
  • Top priorities rarely completed
  • Constant email/Slack interruptions
  • 15% weekly goal completion rate
  • Felt productive but accomplished little

After implementing plan-my-day:

  • Used skill every morning (2-3 minutes to generate plan)
  • Protected 9-11am deep work block (calendar marked "Focus Time")
  • Set clear Top 3 priorities each day
  • Added evening check-ins to track completion

Results after 8 weeks:

  • 74% weekly goal completion rate (+59 points)
  • Meetings reduced from 6-8 hrs/day to 3-4 hrs/day
  • Deep work blocks protected 4 days/week (vs 0 before)
  • Self-reported energy levels: 8.2/10 (vs 4.1/10 before)
  • Team feedback: "You're more present and decisive"

Key insight: "The daily plan gave me permission to say no. If it wasn't in my Top 3, I deferred it. That one change unlocked everything."

Configuration Options

Standard Mode (default)

/plan-my-day
  • Balanced energy windows
  • 8-hour workday assumption
  • 20% buffer time

High-Output Mode

/plan-my-day --mode high-output
  • 10-hour workday
  • More aggressive scheduling
  • 10% buffer time
  • Best for: Launch weeks, crunch periods

Deep Work Mode

/plan-my-day --mode deep-work
  • Maximum uninterrupted blocks
  • Minimal meetings
  • 30% buffer time
  • Best for: Individual contributors, creators

Meeting-Heavy Mode

/plan-my-day --mode coordination
  • Meeting-first scheduling
  • Work blocks fit around commitments
  • 25% buffer time
  • Best for: Managers, executives, client-facing roles

Installation

# Copy skill to your skills directory
cp -r plan-my-day $HOME/.openclaw/skills/

# Verify installation
/plan-my-day --version

No dependencies required - Pure planning logic.

Future Integrations (Coming Soon)

  • Google Calendar sync - Auto-import existing events
  • Completion tracking - Analytics on your planning accuracy over time
  • Energy pattern learning - Adapts to when you actually perform best
  • Team coordination - Sync focus blocks across teams

Pro Tips

  1. Run it FIRST thing - Before checking email or Slack. Set the day, don't react to it.
  2. Protect Peak hours - Block 9-11am as "Focus Time" on your calendar. Decline meetings here.
  3. Track completion rates - Use evening check-in data to improve your estimations
  4. Adjust energy windows - Default is 9-11am peak, but if you're different, customize it
  5. Combine with "shutdown ritual" - Evening check-in + tomorrow's prep = mental closure
  6. Don't over-schedule - If plan shows 7 hours of tasks for 8-hour day, you're on track

Common Mistakes to Avoid

❌ Planning too much - If you schedule 100% of your time, you'll fail. Always leave 20% buffer. ❌ Ignoring energy windows - Putting hard thinking work at 4pm sets you up for failure. ❌ Skipping breaks - 90-minute focus blocks REQUIRE 15-minute breaks or performance drops. ❌ No evening reflection - Without check-ins, you can't improve your planning accuracy. ❌ Changing Top 3 mid-day - Unless genuinely urgent, stick to morning priorities.

Quality Checklist

A good daily plan has:

  • Clear Top 3 priorities with measurable outcomes
  • #1 priority scheduled in peak energy window
  • 20% buffer time (not every minute scheduled)
  • Breaks scheduled every 90 minutes
  • Protected lunch break (minimum 30 minutes)
  • Evening check-in template included
  • No work scheduled after 7pm (personal time protected)

Support

Issues or suggestions? Provide:

  • Your typical day structure (work hours, meeting load)
  • Top 3 priorities example
  • Energy pattern (when you're most focused)
  • What's not working in current output

Built on circadian rhythm research (Roenneberg), deliberate practice principles (Ericsson), and GTD methodology (Allen).

Plan your day in 2 minutes. Execute with focus. Win consistently.

平台分布

Codex

33.9%
按下载量换算194

Claude

32.8%
按下载量换算187

Cursor

20.44%
按下载量换算117

Gemini CLI

9.43%
按下载量换算54

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills