Timeblock

Plan your day hour-by-hour with intentional time blocking. Use when blocking sessions, checking plans, analyzing allocation, generating agendas.

Security Scan

The skill is internally consistent: it is a local, instruction-driven time‑logging tool that only writes/read files under ~/.local/share/timeblock and does not request credentials, network access, or unusual install steps.

Purpose & Capability

Name/description match the actual behavior. The skill provides a CLI script for creating and querying local timeblock logs and does not request unrelated binaries, credentials, or services.

Instruction Scope

SKILL.md instructs the agent to run the included bash script and stay local; the runtime instructions and script only read/write files in ~/.local/share/timeblock, show stats, search, and export. Minor implementation notes: JSON export does simple concatenation and does not escape values (entries containing quotes/newlines could produce invalid JSON), and search uses grep with the raw term which behaves as a pattern rather than a literal search—these are quality/robustness issues but not evidence of malicious scope creep.

Install Mechanism

No install spec; the skill is instruction-only with one included shell script. Nothing is downloaded or written outside the user's home data directory at runtime.

Credentials

No environment variables, credentials, or config paths are requested. The script only uses HOME to compute a local data directory—appropriate for the stated purpose.

Persistence & Privilege

always is false and the skill does not request elevated/persistent platform privileges or modify other skills. It creates and updates files only under its own data directory.

Assessment

This skill appears to do exactly what it claims: log and manage time-block entries locally under ~/.local/share/timeblock. Before installing, be aware that: (1) it will create and update files in that directory; (2) you should avoid storing sensitive secrets or passwords in log entries since they are plain text; (3) exported JSON may be malformed if entries contain quotes or newlines, and search treats your query as a grep pattern (escape if needed). No network calls or credentials are requested, so the privacy surface is limited to local files.

Timeblock v2.0.0 — a utility toolkit for logging, tracking, and managing time-blocking operations from the command line. All data is stored locally in flat log files with timestamps, making it easy to review history, export records, and search across entries.

Commands

Run scripts/script.sh <command> [args] to use.

Core Operations

Command	Description
run <input>	Log a run entry (e.g. execute a time block, start a session)
check <input>	Log a check entry (e.g. verify block completion, review schedule)
convert <input>	Log a convert entry (e.g. convert time formats, transform schedules)
analyze <input>	Log an analyze entry (e.g. analyze time allocation, productivity patterns)
generate <input>	Log a generate entry (e.g. generate daily schedules, weekly plans)
preview <input>	Log a preview entry (e.g. preview tomorrow's blocks, upcoming week)
batch <input>	Log a batch entry (e.g. batch-create time blocks for a week)
compare <input>	Log a compare entry (e.g. compare planned vs actual time usage)
export <input>	Log an export entry (e.g. export schedule to calendar, share plan)
config <input>	Log a config entry (e.g. set block durations, default categories)
status <input>	Log a status entry (e.g. current block status, schedule progress)
report <input>	Log a report entry (e.g. daily/weekly time reports, utilization summaries)

Each command without arguments shows the 20 most recent entries for that category.

Utility Commands

Command	Description
stats	Summary statistics across all log categories with entry counts and disk usage
export <fmt>	Export all data in json, csv, or txt format
search <term>	Search across all log files for a keyword (case-insensitive)
recent	Show the 20 most recent entries from the global activity history
status	Health check — version, data directory, total entries, disk usage, last activity
help	Show full usage information
version	Show version string (timeblock v2.0.0)

Data Storage

All data is persisted locally under ~/.local/share/timeblock/:

• <command>.log — One log file per command (e.g. run.log, check.log, analyze.log)
• history.log — Global activity log with timestamps for every operation
• export.<fmt> — Generated export files (json/csv/txt)

Each entry is stored as YYYY-MM-DD HH:MM|<input> (pipe-delimited). No external services, no API keys, no network calls — everything stays on your machine.

Requirements

• Bash 4.0+ with set -euo pipefail
• Standard Unix utilities: date, wc, du, grep, tail, cat, sed, basename
• No external dependencies or packages required
• No API keys or accounts needed

When to Use

1. Planning your day — Use generate and run to create and log time blocks for each hour, building a structured daily schedule you can search and review later
2. Tracking schedule adherence — Use check and compare to record whether you completed blocks as planned, then stats to see completion patterns over time
3. Analyzing time allocation — Use analyze to log how you actually spent your time, then search to find patterns across categories like deep work, meetings, or breaks
4. Batch-creating weekly plans — Use batch to log entire week schedules at once, then preview to review upcoming blocks before each day starts
5. Generating productivity reports — Use report to log daily summaries, then export csv to pull structured data for time-tracking spreadsheets or dashboards

Examples

# Log a time block session
timeblock run "09:00-10:30 Deep work on project Alpha"

# Generate a daily schedule
timeblock generate "Monday: 09:00 deep work, 10:30 standup, 11:00 code review, 14:00 planning"

# Check schedule completion
timeblock check "Morning blocks completed: 3/4, missed 10:30 standup"

# Compare planned vs actual
timeblock compare "Planned 4h deep work, actual 2.5h — meetings overran by 1.5h"

# Search for all deep work entries
timeblock search "deep work"

# Export everything to JSON
timeblock export json

# View overall statistics
timeblock stats

---

Powered by BytesAgain | bytesagain.com | [e-mail]