BytesAgain is a curated directory of 60,000+ AI agent skills from ClawHub, GitHub, LobeHub, and Dify. Search skills by keyword in 7 languages, browse by role (developer, creator, trader, marketer) or by use case.

How do I find AI skills on BytesAgain?

Use the search bar on BytesAgain.com to search by keyword in 7 languages. You can also browse by role (developer, creator, trader, marketer) or by use case. Each skill shows install instructions for Claude, Cursor, OpenClaw, Continue, and more.

Yes, BytesAgain is completely free. No registration required for searching skills. The MCP API is also free with rate limits.

Does BytesAgain have an API for AI agents?

Yes! BytesAgain provides a free MCP SSE endpoint at /api/mcp/sse for AI agents, plus a REST API at /api/mcp?action=search&q= . No authentication needed.

Can I request a new AI skill on BytesAgain?

Yes! Visit the Requests page on BytesAgain.com to submit a skill request. Your request will be visible to the community and notified to the site admin.

🦀 ClawHub✦ BytesAgain

Stopwatch

by @ckchzh

Run stopwatch, timer, and lap tracking with precision in terminal. Use when timing tasks, checking durations, running countdowns, analyzing splits.

Versionv2.0.0

Downloads378

Installs2

#legal #productivity

View on ClawHub →

TERMINAL

clawhub install stopwatch

📖 About This Skill

name: Stopwatch description: "Run stopwatch, timer, and lap tracking with precision in terminal. Use when timing tasks, checking durations, running countdowns, analyzing splits." version: "2.0.0" author: "BytesAgain" homepage: https://bytesagain.com source: https://github.com/bytesagain/ai-skills tags: ["timer","stopwatch","countdown","time","lap"] categories: ["Developer Tools", "Utility"]

Stopwatch

Stopwatch v2.0.0 — a versatile utility toolkit for logging, tracking, and managing time-related entries from the command line. Each command logs timestamped entries to individual log files, provides history viewing, summary statistics, data export, and full-text search across all records.

Commands

Run stopwatch [args] to use.

| Command | Description | |---------|-------------| | run | Log a run entry (or view recent run entries if no input given) | | check | Log a check entry (or view recent check entries if no input given) | | convert | Log a convert entry (or view recent convert entries if no input given) | | analyze | Log an analyze entry (or view recent analyze entries if no input given) | | generate | Log a generate entry (or view recent generate entries if no input given) | | preview | Log a preview entry (or view recent preview entries if no input given) | | batch | Log a batch entry (or view recent batch entries if no input given) | | compare | Log a compare entry (or view recent compare entries if no input given) | | export | Log an export entry (or view recent export entries if no input given) | | config | Log a config entry (or view recent config entries if no input given) | | status | Log a status entry (or view recent status entries if no input given) | | report | Log a report entry (or view recent report entries if no input given) | | stats | Show summary statistics across all log files (entry counts, data size) | | export | Export all data in json, csv, or txt format | | search | Full-text search across all log entries (case-insensitive) | | recent | Show the 20 most recent entries from history.log | | help | Show usage help | | version | Show version (v2.0.0) |

How It Works

Every command (run, check, convert, analyze, etc.) works the same way:

With arguments: Saves a timestamped entry (YYYY-MM-DD HH:MM|input) to .log and writes to history.log.

Without arguments: Displays the 20 most recent entries from that command's log file.

This gives you a lightweight, file-based logging system for any kind of time-tracking workflow.

Data Storage

All data is stored locally in ~/.local/share/stopwatch/:

~/.local/share/stopwatch/
├── run.log          # Run entries (timestamp|value)
├── check.log        # Check entries
├── convert.log      # Convert entries
├── analyze.log      # Analyze entries
├── generate.log     # Generate entries
├── preview.log      # Preview entries
├── batch.log        # Batch entries
├── compare.log      # Compare entries
├── export.log       # Export entries
├── config.log       # Config entries
├── status.log       # Status entries
├── report.log       # Report entries
├── history.log      # Master activity log
└── export.     # Exported data files

Override the data directory by setting STOPWATCH_DIR (if supported) or editing the DATA_DIR variable in the script.

Requirements

Bash (4.0+)

Standard POSIX utilities: date, wc, du, tail, grep, sed, cat

No external dependencies — works on any Linux or macOS system out of the box

When to Use

1. Tracking timed activities — Log start/stop times for tasks, pomodoro sessions, or work intervals throughout the day. 2. Comparing performance across runs — Use compare and analyze to log different attempts, then search or stats to review trends. 3. Batch processing records — Use batch to log bulk operations, then export json to feed results into other tools. 4. Quick status checks in automation — Integrate stopwatch status or stopwatch stats into cron jobs or CI pipelines for operational dashboards. 5. Generating reports from logged data — Use report to log milestones, then export csv to create spreadsheets or feed into reporting tools.

Examples

# Log a run entry
stopwatch run "Morning sprint: 25 minutes"
Check recent activity
stopwatch recent
View all run entries
stopwatch run
Search for a specific term across all logs
stopwatch search "sprint"
Get summary statistics
stopwatch stats
Export everything to JSON
stopwatch export json
Export to CSV for spreadsheet import
stopwatch export csv

Output

All commands output to stdout. Redirect to a file if needed:

stopwatch stats > report.txt
stopwatch export json  # writes to ~/.local/share/stopwatch/export.json

⚡ When to Use

Trigger	Action
2. Comparing performance across runs — Use `compare` and `analyze` to log different attempts, then `search` or `stats` to review trends.
3. Batch processing records — Use `batch` to log bulk operations, then `export json` to feed results into other tools.
4. Quick status checks in automation — Integrate `stopwatch status` or `stopwatch stats` into cron jobs or CI pipelines for operational dashboards.
5. Generating reports from logged data — Use `report` to log milestones, then `export csv` to create spreadsheets or feed into reporting tools.

💡 Examples

# Log a run entry
stopwatch run "Morning sprint: 25 minutes"
Check recent activity
stopwatch recent
View all run entries
stopwatch run
Search for a specific term across all logs
stopwatch search "sprint"
Get summary statistics
stopwatch stats
Export everything to JSON
stopwatch export json
Export to CSV for spreadsheet import
stopwatch export csv

Trigger	Action
2. Comparing performance across runs — Use `compare` and `analyze` to log different attempts, then `search` or `stats` to review trends.
3. Batch processing records — Use `batch` to log bulk operations, then `export json` to feed results into other tools.
4. Quick status checks in automation — Integrate `stopwatch status` or `stopwatch stats` into cron jobs or CI pipelines for operational dashboards.
5. Generating reports from logged data — Use `report` to log milestones, then `export csv` to create spreadsheets or feed into reporting tools.