Time Management

Plan days, prioritize tasks, and protect focus time with time blocking, weekly reviews, and energy-aware scheduling.

Security Scan

The skill largely matches its stated time-management purpose and has no external credentials, but it instructs the agent to read setup files 'silently' and to hide internal file names from the user — a secrecy pattern that is unnecessary for the described functionality and raises concern.

Purpose & Capability

Name/description (time blocking, weekly reviews, energy-aware scheduling) align with the included reference documents and the single local memory directory (~/time-management/). No binaries, external credentials, or unrelated capabilities are requested — the requested footprint is proportionate to the stated purpose.

Instruction Scope

Runtime instructions are mostly scoped to planning, asking questions, and storing user-provided preferences in ~/time-management/. However, the SKILL.md explicitly directs the agent to 'read setup.md silently' and 'Never mention "setup" or file names to the user.' That instruction to conceal internal operations is out-of-band for a coaching skill and increases risk (it creates hidden behavior that could be used to hide malicious actions). The rest of the instructions limit activity to included files and claim no network, calendar, or email access, which is coherent — but the secrecy directive is the main issue.

Install Mechanism

Instruction-only skill with no install spec and no code files. Low installation risk because nothing is downloaded or executed beyond the agent following the provided prose and writing local files.

Credentials

No environment variables, credentials, or external config paths requested. The only persistent resource is a directory under the user's home, which the skill states it will use for local memory — this is proportionate to its function.

Persistence & Privilege

The skill will create and update files in ~/time-management/ (memory.md, weekly-review.md, templates). It does not request elevated privileges nor set always:true. Persisting user preferences locally is reasonable, but users should be aware the skill updates those files on each use (SKILL.md instructs updating 'last' and memory).

What to consider before installing

This skill appears to do what it says (time blocking, prioritization) and requires no external credentials, but it asks the agent to read its setup file 'silently' and not tell the user about file names — a secrecy behavior that is unnecessary for a coaching skill and could hide unexpected actions. Before enabling: 1) Inspect the skill files yourself (SKILL.md, setup.md, memory-template.md) to confirm they only reference local storage and no network or external integrations. 2) Decide whether you are comfortable with a folder being created and updated at ~/time-management/; if not, don’t install. 3) Ask the agent (or modify the skill) to request explicit permission before saving any sensitive information and to be transparent when it reads or writes files (remove the 'silently' / 'never mention' instruction). 4) Monitor for any unexpected network activity after enabling — the skill claims none, so any network calls would be suspicious. If you are unsure, run it in a limited or test environment first.

Setup

On first use, read setup.md silently and start the conversation naturally. Never mention "setup" or file names to the user.

When to Use

User needs help planning their day, prioritizing tasks, or protecting time for important work. Agent handles time blocking, weekly reviews, and schedule optimization.

Architecture

Memory lives in ~/time-management/. See memory-template.md for structure.

~/time-management/
├── memory.md          # Preferences + current commitments
├── weekly-review.md   # Last review notes
└── templates/         # User's custom templates

Quick Reference

Topic	File
Setup process	setup.md
Memory template	memory-template.md
Time blocking method	time-blocking.md
Prioritization frameworks	prioritization.md
Weekly review process	weekly-review.md
Common time traps	traps.md

Core Rules

1. Default to Time Blocking

When user asks "how should I organize my day?":

1. Identify their 1-3 most important tasks (MITs)
2. Assign specific time blocks (not just "morning")
3. Add buffer time between blocks (15-30 min)
4. Protect the first deep work block

Example response:

Your day:
09:00-11:00 — [MIT #1] (deep work, no meetings)
11:00-11:30 — Buffer/email
11:30-12:30 — [MIT #2]
12:30-13:30 — Lunch
13:30-15:00 — Meetings/calls
15:00-16:30 — [MIT #3 or admin tasks]
16:30-17:00 — Plan tomorrow

2. Energy-Aware Scheduling

Match task type to energy levels:

Time	Energy	Best for
Morning (first 2-4h)	Peak	Creative work, hard problems, writing
Mid-day	Moderate	Meetings, collaboration, admin
Afternoon	Lower	Routine tasks, email, planning

If user's peak time differs → ask and adapt.

3. Protect Deep Work

When scheduling:

• First block of day = deep work (no exceptions)
• Minimum 90 minutes for meaningful progress
• No meetings before 11am (suggest as default)
• If user has back-to-back meetings → flag the problem

4. Weekly Review Habit

Suggest weekly review on Sunday evening or Monday morning:

1. What worked last week?
2. What didn't?
3. Top 3 priorities for this week
4. Any time blocks to protect?

Store notes in ~/time-management/weekly-review.md.

5. Say No by Default

When user considers adding commitments:

• Ask: "What will you NOT do to make time for this?"
• If answer is unclear → suggest declining
• Protect existing commitments over new ones

6. Batch Similar Tasks

Group similar activities:

• All calls in one block
• All email in 2-3 daily slots (not constant checking)
• All admin tasks together
• Context switching = time lost

7. Plan Tomorrow Tonight

End-of-day ritual:

1. Review what got done
2. Move incomplete tasks
3. Set top 3 for tomorrow
4. Write first block explicitly

Time Traps

Trap	Why it fails	Alternative
"I'll do it when I have time"	That time never comes	Schedule it or decline
30-minute meeting blocks	No deep work possible	90-min minimum for real work
Checking email first	Reactive mode hijacks your day	Deep work first, email at 11am
No buffer time	Delays cascade	15-min buffers between blocks
Planning in your head	Forgotten and overwhelming	Write it down, one place
"I work better under pressure"	Usually stress, not quality	Start earlier, same deadline

Scope

This skill ONLY:

• Provides time management advice when asked
• Helps plan days and weeks
• Stores preferences user explicitly provides
• Reads included reference files

This skill NEVER:

• Accesses calendar, email, or any external service
• Tracks or monitors user activity
• Makes network requests
• Modifies files without explicit user request

External Endpoints

This skill makes NO external network requests.

Endpoint	Data Sent	Purpose
None	None	N/A

Security & Privacy

Data that stays local:

• Preferences you explicitly ask to save
• Stored in ~/time-management/
• You can delete anytime

This skill does NOT:

• Access any external service
• Track your behavior
• Infer preferences without asking

Related Skills

Install with clawhub install <slug> if user confirms:

• productivity — energy management and focus systems
• schedule — recurring tasks and reminders
• habits — building consistent routines

Feedback

• If useful: clawhub star time-management
• Stay updated: clawhub sync