deepwork-tracker
Track deep work sessions locally (start/stop/status) and generate a GitHub-contribution-graph style minutes-per-day heatmap for sharing (e.g., via Telegram). Use when the user says things like “start deep work”, “stop deep work”, “am I in a session?”, “show my deep work graph”, or asks to review deep work history.
What this skill does
# Deepwork Tracker Use the local deepwork app (SQLite-backed) at `~/clawd/deepwork/deepwork.js`. ## Bootstrap (if the script is missing) If `~/clawd/deepwork/deepwork.js` does not exist, bootstrap it from the public repo: ```bash mkdir -p ~/clawd cd ~/clawd # Clone if missing [ -d ~/clawd/deepwork-tracker/.git ] || git clone https://github.com/adunne09/deepwork-tracker.git ~/clawd/deepwork-tracker # Ensure expected runtime path exists mkdir -p ~/clawd/deepwork cp -f ~/clawd/deepwork-tracker/app/deepwork.js ~/clawd/deepwork/deepwork.js chmod +x ~/clawd/deepwork/deepwork.js ``` (Do not fail the user request if clone/copy fails—still attempt other steps and report what’s missing.) ## Commands Run via exec: - Start a session (also starts a macOS Clock timer; default target 60m): - `~/clawd/deepwork/deepwork.js start --target-min 60` - Stop a session: - `~/clawd/deepwork/deepwork.js stop` - Check status: - `~/clawd/deepwork/deepwork.js status` - Generate a report: - Last 7 days (default): `~/clawd/deepwork/deepwork.js report --days 7 --format text` - Telegram-ready last 7 days: `~/clawd/deepwork/deepwork.js report --days 7 --format telegram` - Heatmap (optional): `~/clawd/deepwork/deepwork.js report --mode heatmap --weeks 52 --format telegram` ## Chat workflows ### Start deep work 1) Run `~/clawd/deepwork/deepwork.js start --target-min 60` (or another target if the user specifies it). 2) This should also start a macOS Clock timer for the target duration (best-effort; may require Accessibility permissions). 3) Reply with the confirmation line. ### Stop deep work 1) Run `~/clawd/deepwork/deepwork.js stop`. 2) Reply with duration. ### Show deep work graph 1) Run `~/clawd/deepwork/deepwork.js report --days 7 --format telegram`. 2) **Always send** the output to Alex on Telegram (id `8551040296`) using the `message` tool with a Markdown monospace code block. 3) Optionally acknowledge in the current chat that it was sent. If the user wants different ranges, support `--days 7|14|30|60`. (Heatmap is still available via `--mode heatmap --weeks ...` when explicitly requested.)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.