Token导航 LogoToken导航TokenDH.com
研究检索权限需确认github未标认证来源可访问许可证需确认审计通过

calendar-optimization日历优化

Agent Skill

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

总安装

1,572

周安装

63

GitHub Stars

37

下载量

509
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:calendar-optimization(日历优化)
来源仓库:https://github.com/majesticlabs-dev/majestic-marketplace
仓库路径:skills/calendar-optimization
安装命令:
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill calendar-optimization
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill calendar-optimization

简介

calendar-optimization 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词或任务场景快速定位候选结果。

  • 它帮助平衡专业时间在管理、创作、客户交付和战略四类中的分配,避免时间被过度占用。
  • 使用时需确认项目现有测试框架、运行命令和夹具数据,确保逻辑真实有效。
  • 涉及浏览器或外部服务时,应区分本地模拟与生产环境差异。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Calendar Optimization

Balance your professional time across 4 essential categories.

The 4 Types of Professional Time

1. Management Time (Red)

What it includes:

  • Meetings and calls
  • Email processing
  • Presentations
  • Team and people management
  • Administrative tasks

The problem: Most professionals spend 70-90% here, leaving scraps for everything else.

2. Creation Time (Green)

What it includes:

  • Writing and content creation
  • Coding and building
  • Designing and prototyping
  • Strategic document preparation
  • Deep work on deliverables

The problem: Gets squeezed into gaps between Management Time. Never protected.

3. Consumption Time (Blue)

What it includes:

  • Reading books and articles
  • Listening to podcasts
  • Studying new skills
  • Research and learning
  • Course completion

The problem: Often happens passively (doom-scrolling) rather than intentionally.

4. Ideation Time (Yellow)

What it includes:

  • Brainstorming sessions
  • Journaling and reflection
  • Walking and thinking
  • Strategic planning (alone)
  • Connecting dots across domains

The problem: Almost never scheduled. Happens accidentally, if at all.

The Calendar Audit Exercise

Week 1: Baseline Assessment

At the end of each weekday, color-code that day's events:

ColorTypeExamples
RedManagementMeetings, emails, calls, admin
GreenCreationBuilding, writing, coding, designing
BlueConsumptionReading, learning, researching
YellowIdeationThinking, brainstorming, journaling

End of Week: Analyze the Mix

Look at your calendar's overall color distribution:

Typical Unhealthy Pattern:

  • 80% Red (Management)
  • 15% Green (Creation)
  • 4% Blue (Consumption)
  • 1% Yellow (Ideation)

Healthier Target:

  • 40-50% Red (Management)
  • 30-40% Green (Creation)
  • 10-15% Blue (Consumption)
  • 5-10% Yellow (Ideation)

3 Optimization Tips

Tip 1: Batch Management Time

The Goal: Keep red from bleeding across every hour of every day.

Actions:

  • Email blocks: 1-3 discrete processing windows per day (e.g., 9am, 1pm, 5pm)
  • Meeting blocks: Cluster calls/meetings into specific windows
  • No-meeting days: At least 1-2 days per week with zero scheduled meetings

Example Schedule:

Monday: Meeting block 10am-12pm, 2pm-4pm
Tuesday: No meetings (Creation day)
Wednesday: Meeting block 9am-11am, 3pm-5pm
Thursday: No meetings (Creation day)
Friday: Meeting block 10am-12pm only

Tip 2: Protect Creation Time

The Goal: Creation propels you forward with interesting projects and opportunities.

Actions:

  • Block it first: Schedule creation time before meetings can claim the space
  • Protect the block: No email, Slack, or messages during creation windows
  • Morning advantage: First 2-3 hours often highest quality for creation
  • Minimum viable block: 90 minutes minimum for meaningful deep work

Microsoft Research Finding:

Users spend significantly more time on email and meetings than creating. The ratio has worsened year over year.

Example Protection:

Daily: 6am-9am Creation Block (non-negotiable)
- Phone on airplane mode
- Slack closed
- Email untouched
- One focused project only

Tip 3: Schedule Consumption & Ideation

The Goal: These "forgotten" time types drive long-term compounding progress.

Historical Pattern:

  • Warren Buffett: 5-6 hours daily reading
  • Bill Gates: Think Weeks (pure ideation)
  • Darwin: 3 daily thinking walks
  • Einstein: Violin breaks for ideation

Actions:

  • Start small: One 30-60 minute Consumption block per week
  • Start small: One 30-60 minute Ideation block per week
  • Protect the purpose: Don't let these become meeting overflow
  • Expand gradually: Only increase after consistently honoring small blocks

Example Schedule:

Wednesday 4-5pm: Consumption (reading/learning)
Friday 3-4pm: Ideation (journaling/walking/thinking)

Weekly Calendar Template

MONDAY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6:00-9:00   [GREEN] Creation Block
9:00-9:30   [RED] Email Processing #1
9:30-12:00  [RED] Meeting Block
12:00-1:00  Lunch
1:00-1:30   [RED] Email Processing #2
1:30-4:00   [GREEN] Creation Block
4:00-5:00   [RED] Meeting Overflow

TUESDAY (No-Meeting Day)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6:00-12:00  [GREEN] Deep Creation
12:00-1:00  Lunch
1:00-5:00   [GREEN] Deep Creation
5:00-5:30   [RED] Email Processing

WEDNESDAY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6:00-9:00   [GREEN] Creation Block
9:00-12:00  [RED] Meeting Block
12:00-1:00  Lunch
1:00-4:00   [RED] Meeting Block
4:00-5:00   [BLUE] Consumption (reading)

THURSDAY (No-Meeting Day)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6:00-12:00  [GREEN] Deep Creation
12:00-1:00  Lunch
1:00-5:00   [GREEN] Deep Creation
5:00-5:30   [RED] Email Processing

FRIDAY
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
6:00-9:00   [GREEN] Creation Block
9:00-12:00  [RED] Meeting Block
12:00-1:00  Lunch
1:00-3:00   [RED] Weekly wrap-up
3:00-4:00   [YELLOW] Ideation (week reflection)
4:00-5:00   [BLUE] Consumption (reading)

Conversation Starter

Use AskUserQuestion to begin:

"I'll help you optimize your calendar for better balance across the 4 types of professional time.

First, let's understand your current state:

How would you estimate your current time split?

  • Management (meetings, email, calls): ____%
  • Creation (building, writing, coding): ____%
  • Consumption (reading, learning): ____%
  • Ideation (thinking, journaling): ____% "

Then ask:

  1. "What's your biggest calendar frustration right now?"
  2. "Do you have any existing protected time blocks?"
  3. "What's one type of time you want more of?"

Output Format

# CALENDAR OPTIMIZATION PLAN

## Current State
| Type | Current % | Target % | Gap |
|------|-----------|----------|-----|
| Management (Red) | X% | Y% | -Z% |
| Creation (Green) | X% | Y% | +Z% |
| Consumption (Blue) | X% | Y% | +Z% |
| Ideation (Yellow) | X% | Y% | +Z% |

## This Week's Changes

### 1. Batch Management
- [ ] Set email processing windows: [times]
- [ ] Cluster meetings to: [days/times]
- [ ] Establish no-meeting day: [day]

### 2. Protect Creation
- [ ] Block creation time: [times]
- [ ] Remove during creation: [distractions]
- [ ] Minimum block length: [duration]

### 3. Schedule Growth Time
- [ ] Consumption block: [day/time]
- [ ] Ideation block: [day/time]

## 30-Day Milestones
- Week 1: Audit and baseline
- Week 2: Implement batching
- Week 3: Add consumption block
- Week 4: Add ideation block + measure improvement

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.79%
按下载量换算177

Claude

30.6%
按下载量换算156

Cursor

20.51%
按下载量换算104

Gemini CLI

9.81%
按下载量换算50

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills