@forwardimpact/basecamp 2.0.0 → 2.3.0

package/template/.claude/skills/weekly-update/SKILL.md

@@ -0,0 +1,250 @@
+---
+name: weekly-update
+description: Generate or refresh a weekly priorities document. Pulls from task boards, recent activity, and calendar to create a point-in-time snapshot. Use when the user asks to update their weekly, prep for the week, or on a Monday morning schedule.
+---
+
+# Weekly Update
+
+Generate or refresh a weekly priorities document in
+`knowledge/Weeklies/{Person Name}/`. Each weekly is a point-in-time snapshot —
+created at the start of the week, updated as priorities shift, and closed out
+with a retrospective at end-of-week.
+
+## Trigger
+
+Run this skill:
+
+- When the user asks to update their weekly or prep for the week
+- Monday mornings (scheduled)
+- When the user asks to review someone's weekly
+- End-of-week to fill in accomplishments and retrospective
+
+## Prerequisites
+
+- `knowledge/Weeklies/` directory exists
+- `knowledge/Tasks/{Person Name}.md` exists (task board — see `manage-tasks`
+  skill)
+- Calendar data in `~/.cache/fit/basecamp/apple_calendar/`
+- User identity configured in `USER.md`
+
+## Inputs
+
+- `knowledge/Tasks/{Person Name}.md` — current task board
+- `knowledge/People/{Person Name}.md` — recent activity, context
+- `~/.cache/fit/basecamp/apple_calendar/*.json` — calendar events for the week
+- Previous weekly document (if exists) — for continuity and carry-forward
+
+## Outputs
+
+- `knowledge/Weeklies/{Person Name}/{YYYY}-W{WW}.md` — the weekly document
+
+---
+
+## Weekly Document Format
+
+```markdown
+# {YYYY}-W{WW} — {Person Name}
+
+> {Focus statement: one sentence summarizing the week's theme}
+
+## Priorities
+
+- [ ] Priority one — [[Projects/Name]]
+- [ ] Priority two
+- [x] Completed priority
+
+## Key Meetings
+
+- **Monday**: Meeting title with [[People/Name]] — purpose
+- **Wednesday**: Meeting title — purpose
+
+## Blockers
+
+- Waiting on X from [[People/Name]]
+
+## Accomplishments
+
+- Completed X
+- Shipped Y
+
+## Retrospective
+
+- **Went well:** ...
+- **Didn't go as planned:** ...
+- **Carry forward:** ...
+```
+
+**Key conventions:**
+
+- **Week numbers:** ISO 8601 (e.g., `2026-W08`)
+- **Priorities:** Top 3-7 items pulled from the task board
+- **Key Meetings:** Substantive meetings only (skip recurring standups)
+- **Retrospective:** Filled at end-of-week only
+- **All backlinks** use absolute paths: `[[People/Name]]`, `[[Projects/Name]]`,
+  `[[Tasks/Name]]`
+
+## Before Starting
+
+1. Read `USER.md` to identify the user.
+2. Determine the target person (default: current user from `USER.md`).
+3. Calculate the current ISO week number and date range:
+
+```bash
+# Current ISO week
+date +%G-W%V
+
+# Monday and Friday of current week (macOS)
+date -v-mon +%Y-%m-%d
+date -v+fri +%Y-%m-%d
+```
+
+4. Check if a weekly already exists for this week:
+
+```bash
+ls "knowledge/Weeklies/{Person Name}/" 2>/dev/null
+```
+
+5. Determine the mode:
+   - **No existing weekly:** Create new (start-of-week)
+   - **Existing weekly:** Update (mid-week or end-of-week)
+
+## Step 1: Gather Context
+
+### 1a. Read the task board
+
+```bash
+cat "knowledge/Tasks/{Person Name}.md"
+```
+
+Extract:
+
+- `## In Progress` tasks → top priorities (already being worked on)
+- `## Open` tasks with `high` priority or near due dates → candidate priorities
+- `## Blocked` tasks → blockers section
+- `## Recently Done` tasks completed this week → accomplishments
+
+### 1b. Read recent activity
+
+```bash
+cat "knowledge/People/{Person Name}.md"
+```
+
+Look at the `## Activity` section for entries from this week. These inform
+accomplishments and provide context for the focus statement.
+
+### 1c. Read calendar for the week
+
+Find events falling within the Monday–Friday range:
+
+```bash
+ls ~/.cache/fit/basecamp/apple_calendar/
+```
+
+Read each calendar event and filter by date. Extract:
+
+- Meeting title
+- Attendees (resolve to `[[People/Name]]` where possible)
+- Time/day
+- Description or agenda (if present)
+
+Filter out:
+
+- All-day placeholder events with no attendees ("Block", "OOO", "Focus time")
+- Declined events
+- Cancelled events
+
+### 1d. Read previous weekly (if exists)
+
+Check for last week's document:
+
+```bash
+ls "knowledge/Weeklies/{Person Name}/" | sort | tail -1
+```
+
+If it exists, read it to:
+
+- Carry forward any `[ ]` unchecked priorities
+- Note retrospective items that affect this week
+- Maintain continuity of ongoing themes
+
+## Step 2: Generate or Update
+
+### Creating a new weekly (start of week)
+
+1. **Focus:** Synthesize from highest-priority tasks and key meetings. What's
+   the main theme? Write one sentence.
+2. **Priorities:** Pull from task board:
+   - All `## In Progress` items first
+   - Then `high` priority `## Open` items
+   - Then items with due dates this week
+   - Carry forward incomplete priorities from last week
+   - Cap at 5-7 items. If more exist, prioritize ruthlessly.
+3. **Key Meetings:** From calendar. Format as
+   `**{Day}**: {title} with [[People/Name]] — {purpose}`. Look up attendees in
+   knowledge base to add context about purpose.
+4. **Blockers:** From task board's `## Blocked` section. Include what's needed
+   and from whom.
+5. **Accomplishments:** Leave empty (or pre-fill with anything completed Monday
+   morning).
+6. **Retrospective:** Leave empty.
+
+### Updating an existing weekly (mid-week)
+
+1. Re-read the task board for changes since the weekly was last updated.
+2. Mark completed priorities as `[x]`.
+3. Add new priorities that emerged (append to the list).
+4. Update blockers — remove resolved ones, add new ones.
+5. Add accomplishments as they happen.
+6. Do NOT touch the retrospective mid-week.
+
+### End-of-week update
+
+1. Final pass on priorities — mark all completed items `[x]`.
+2. Fill in accomplishments from the full week's activity (task board + People
+   note activity log).
+3. Write a brief retrospective:
+   - What went well?
+   - What didn't go as planned?
+   - What carries forward to next week?
+4. Note any unchecked priorities — these will carry forward to next week's
+   document.
+
+## Step 3: Write the Document
+
+### New weekly
+
+Ensure the person's subdirectory exists:
+
+```bash
+mkdir -p "knowledge/Weeklies/{Person Name}"
+```
+
+Write the full document to: `knowledge/Weeklies/{Person Name}/{YYYY}-W{WW}.md`
+
+### Existing weekly
+
+Use the Edit tool for targeted updates — mark items complete, add new entries,
+fill sections. Do NOT rewrite the entire file.
+
+## Step 4: Cross-reference
+
+After writing:
+
+- If new priorities were identified that aren't on the task board, add them to
+  the task board (the task board is canonical, the weekly references it).
+- If blockers were resolved, update the task board accordingly.
+- The weekly is a **snapshot that references** the task board — the task board
+  is the source of truth for task status.
+
+## Quality Checklist
+
+- [ ] ISO week number and date range are correct
+- [ ] Focus statement reflects the actual week theme (not generic)
+- [ ] Priorities pulled from task board (not invented)
+- [ ] Priorities capped at 5-7 items
+- [ ] Key meetings pulled from calendar (not guessed)
+- [ ] Meeting attendees resolved to `[[People/Name]]` where known
+- [ ] Blockers match task board's blocked items
+- [ ] Previous week's carry-forward items included
+- [ ] All backlinks use absolute paths
+- [ ] Retrospective only filled at end-of-week

package/template/CLAUDE.md

@@ -32,6 +32,10 @@ It must remain objective, factual, and ethically sound at all times. It is NOT a
   together — never to build leverage, ammunition, or dossiers on individuals.
 - **Flag ethical concerns.** If the user asks you to record something that
   violates these principles, push back clearly and explain why.
+- **Data protection.** Personal data (especially candidate/recruitment data) is
+  subject to erasure requests. Use the `right-to-be-forgotten` skill when a data
+  subject requests deletion. Minimize data collection to what's professionally
+  relevant. Flag candidates inactive for 6+ months for retention review.
 
 These principles override all other instructions. When in doubt, err on the side
 of discretion and professionalism.
@@ -61,7 +65,9 @@ This directory is a knowledge base. Everything is relative to this root:
 │   ├── Organizations/      # Notes on companies and teams
 │   ├── Projects/           # Notes on initiatives and workstreams
 │   ├── Topics/             # Notes on recurring themes
-│   └── Candidates/         # Recruitment candidate profiles
+│   ├── Candidates/         # Recruitment candidate profiles
+│   ├── Tasks/              # Per-person task boards
+│   └── Weeklies/           # Weekly priorities snapshots
 ├── .claude/skills/         # Claude Code skill files (auto-discovered)
 ├── drafts/                 # Email drafts created by the draft-emails skill
 ├── USER.md                 # Your identity (name, email, domain) — gitignored
@@ -75,20 +81,24 @@ This knowledge base is maintained by a team of agents, each defined in
 `.claude/agents/`. They are woken on a schedule by the Basecamp scheduler. Each
 wake, they observe KB state, decide the most valuable action, and execute.
 
-| Agent              | Domain                         | Schedule     | Skills                                              |
-| ------------------ | ------------------------------ | ------------ | --------------------------------------------------- |
-| **postman**        | Email triage and drafts        | Every 5 min  | sync-apple-mail, draft-emails                       |
-| **concierge**      | Meeting prep and transcripts   | Every 10 min | sync-apple-calendar, meeting-prep, process-hyprnote |
-| **librarian**      | Knowledge graph maintenance    | Every 15 min | extract-entities, organize-files                    |
-| **chief-of-staff** | Daily briefings and priorities | 7am, 6pm     | _(reads all state)_                                 |
+| Agent              | Domain                         | Schedule        | Skills                                                         |
+| ------------------ | ------------------------------ | --------------- | -------------------------------------------------------------- |
+| **postman**        | Email triage and drafts        | Every 5 min     | sync-apple-mail, draft-emails                                  |
+| **concierge**      | Meeting prep and transcripts   | Every 10 min    | sync-apple-calendar, meeting-prep, process-hyprnote            |
+| **librarian**      | Knowledge graph maintenance    | Every 15 min    | extract-entities, organize-files, manage-tasks                 |
+| **recruiter**      | Engineering recruitment        | Every 30 min    | track-candidates, analyze-cv, right-to-be-forgotten, fit-pathway, fit-map |
+| **chief-of-staff** | Daily briefings and priorities | 7am, Mon 7:30am | weekly-update _(Mon)_, _(reads all state for daily briefings)_ |
 
-Agent state files are in `~/.cache/fit/basecamp/state/`:
+Each agent writes a triage file to `~/.cache/fit/basecamp/state/` every wake
+cycle. The naming convention is `{agent}_triage.md`:
 
-- `postman_triage.md` — latest email triage
-- `concierge_outlook.md` — today's calendar outlook
-- `librarian_digest.md` — knowledge graph status
+- `postman_triage.md` — email urgency, reply needs, awaiting responses
+- `concierge_triage.md` — schedule, meeting prep status, unprocessed transcripts
+- `librarian_triage.md` — unprocessed files, knowledge graph size
+- `recruiter_triage.md` — candidate pipeline, assessments, track distribution
 
-Daily briefings are in `knowledge/Briefings/`.
+The **chief-of-staff** reads all three triage files to synthesize daily
+briefings in `knowledge/Briefings/`.
 
 ## Cache Directory (`~/.cache/fit/basecamp/`)
 
@@ -97,20 +107,21 @@ Synced data and runtime state live outside the knowledge base in
 
 ```
 ~/.cache/fit/basecamp/
-├── apple_mail/         # Synced Apple Mail threads (.md files)
-├── apple_calendar/     # Synced Apple Calendar events (.json files)
-├── gmail/              # Synced Gmail threads (.md files)
-├── google_calendar/    # Synced Google Calendar events (.json files)
-└── state/              # Runtime state (plain text files)
-    ├── apple_mail_last_sync   # ISO timestamp of last mail sync
-    └── graph_processed        # TSV of processed files (path<TAB>hash)
+├── apple_mail/              # Synced Apple Mail threads (.md files)
+│   └── attachments/         # Copied email attachments by thread
+├── apple_calendar/          # Synced Apple Calendar events (.json files)
+└── state/                   # Runtime state
+    ├── apple_mail_last_sync # ISO timestamp of last mail sync
+    ├── graph_processed      # TSV of processed files (path<TAB>hash)
+    ├── postman_triage.md    # Agent triage files ({agent}_triage.md)
+    ├── concierge_triage.md
+    ├── librarian_triage.md
+    └── recruiter_triage.md
 ```
 
 This separation keeps the knowledge base clean — only the parsed knowledge
-graph, notes, documents, and drafts live in the KB directory. Raw synced data
-and processing state are cached externally. State files use simple Unix-friendly
-formats (single-value text files, TSV) rather than JSON, making them easy to
-read and write from shell scripts.
+graph, notes, documents, and drafts live in the KB directory. Raw synced data,
+processing state, and agent triage files are cached externally.
 
 ## How to Access the Knowledge Graph
 
@@ -165,10 +176,9 @@ build a complete picture, then respond. A single note is never the full story.
 Synced emails and calendar events are stored in `~/.cache/fit/basecamp/`,
 outside the knowledge base:
 
-- **Emails:** `~/.cache/fit/basecamp/apple_mail/` and
-  `~/.cache/fit/basecamp/gmail/` — each thread is a `.md` file
-- **Calendar:** `~/.cache/fit/basecamp/apple_calendar/` and
-  `~/.cache/fit/basecamp/google_calendar/` — each event is a `.json` file
+- **Emails:** `~/.cache/fit/basecamp/apple_mail/` — each thread is a `.md` file
+- **Calendar:** `~/.cache/fit/basecamp/apple_calendar/` — each event is a
+  `.json` file
 
 When the user asks about calendar, upcoming meetings, or recent emails, read
 directly from these folders.
@@ -179,19 +189,37 @@ Skills are auto-discovered by Claude Code from `.claude/skills/`. Each skill is
 a `SKILL.md` file inside a named directory. You do NOT need to read them
 manually — Claude Code loads them automatically based on context.
 
-Available skills:
-
-| Skill                  | Directory                              | Purpose                                         |
-| ---------------------- | -------------------------------------- | ----------------------------------------------- |
-| Sync Apple Mail        | `.claude/skills/sync-apple-mail/`      | Sync Apple Mail threads via SQLite              |
-| Sync Apple Calendar    | `.claude/skills/sync-apple-calendar/`  | Sync Apple Calendar events via SQLite           |
-| Extract Entities       | `.claude/skills/extract-entities/`     | Process synced data into knowledge graph notes  |
-| Draft Emails           | `.claude/skills/draft-emails/`         | Draft email responses using knowledge context   |
-| Meeting Prep           | `.claude/skills/meeting-prep/`         | Prepare briefings for upcoming meetings         |
-| Create Presentations   | `.claude/skills/create-presentations/` | Create slide decks as PDF                       |
-| Document Collaboration | `.claude/skills/doc-collab/`           | Document creation and collaboration             |
-| Organize Files         | `.claude/skills/organize-files/`       | File organization and cleanup                   |
-| Process Hyprnote       | `.claude/skills/process-hyprnote/`     | Extract entities from Hyprnote meeting sessions |
+Available skills (grouped by function):
+
+**Data pipeline** — sync raw sources into the cache directory:
+
+| Skill                 | Purpose                                    |
+| --------------------- | ------------------------------------------ |
+| `sync-apple-mail`     | Sync Mail threads to `.md` via SQLite      |
+| `sync-apple-calendar` | Sync Calendar events to `.json` via SQLite |
+
+**Knowledge graph** — build and maintain structured notes:
+
+| Skill              | Purpose                                  |
+| ------------------ | ---------------------------------------- |
+| `extract-entities` | Process synced data into knowledge notes |
+| `manage-tasks`     | Per-person task boards with lifecycle    |
+| `track-candidates` | Recruitment pipeline from email threads  |
+| `analyze-cv`       | CV assessment against career framework   |
+| `right-to-be-forgotten` | GDPR data erasure with audit trail  |
+| `weekly-update`    | Weekly priorities from tasks + calendar  |
+| `process-hyprnote` | Extract entities from Hyprnote sessions  |
+| `organize-files`   | Tidy Desktop/Downloads, chain to extract |
+
+**Communication** — draft, send, and present:
+
+| Skill                  | Purpose                                   |
+| ---------------------- | ----------------------------------------- |
+| `draft-emails`         | Draft email responses with KB context     |
+| `send-chat`            | Send chat messages via browser automation |
+| `meeting-prep`         | Briefings for upcoming meetings           |
+| `create-presentations` | Generate PDF slide decks                  |
+| `doc-collab`           | Document creation and editing             |
 
 ## User Identity
 

package/template/.claude/skills/create-presentations/scripts/convert-to-pdf.js

@@ -1,32 +0,0 @@
-// Convert HTML slides to PDF using Playwright.
-//
-// Usage: node scripts/convert-to-pdf.js [input.html] [output.pdf]
-//
-// Defaults:
-//   input:  /tmp/basecamp-presentation.html
-//   output: ~/Desktop/presentation.pdf
-//
-// Requires: npm install playwright && npx playwright install chromium
-
-const { chromium } = require("playwright");
-const path = require("path");
-
-const input = process.argv[2] || "/tmp/basecamp-presentation.html";
-const output =
-  process.argv[3] || path.join(process.env.HOME, "Desktop", "presentation.pdf");
-
-(async () => {
-  const browser = await chromium.launch();
-  const page = await browser.newPage();
-  await page.goto(`file://${path.resolve(input)}`, {
-    waitUntil: "networkidle",
-  });
-  await page.pdf({
-    path: output,
-    width: "1280px",
-    height: "720px",
-    printBackground: true,
-  });
-  await browser.close();
-  console.log(`Done: ${output}`);
-})();

package/template/.claude/skills/draft-emails/scripts/scan-emails.sh

@@ -1,34 +0,0 @@
-#!/bin/bash
-# Scan for unprocessed emails and output their IDs and subjects.
-#
-# Usage: bash scripts/scan-emails.sh
-#
-# Checks ~/.cache/fit/basecamp/apple_mail/ for email files not yet
-# listed in drafts/drafted or drafts/ignored.
-# Outputs tab-separated: email_id<TAB>subject
-
-set -euo pipefail
-
-MAIL_DIRS=(
-  "$HOME/.cache/fit/basecamp/apple_mail"
-  "$HOME/.cache/fit/basecamp/gmail"
-)
-
-for dir in "${MAIL_DIRS[@]}"; do
-  [ -d "$dir" ] || continue
-  for file in "$dir"/*.md; do
-    [ -f "$file" ] || continue
-
-    # Extract ID from filename (without extension)
-    EMAIL_ID="$(basename "$file" .md)"
-
-    # Skip if already drafted or ignored
-    rg -qxF "$EMAIL_ID" drafts/drafted 2>/dev/null && continue
-    rg -qxF "$EMAIL_ID" drafts/ignored 2>/dev/null && continue
-
-    # Extract subject from first H1 heading
-    SUBJECT="$(rg -m1 '^# ' "$file" 2>/dev/null | sed 's/^# //')"
-
-    printf '%s\t%s\n' "$EMAIL_ID" "$SUBJECT"
-  done
-done

package/template/.claude/skills/extract-entities/scripts/state.py

@@ -1,100 +0,0 @@
-#!/usr/bin/env python3
-"""Manage graph_processed state for entity extraction.
-
-Commands:
-  check   - Find unprocessed or changed source files
-  update  - Mark a file as processed (updates its hash in state)
-
-Usage:
-  python3 scripts/state.py check                    # List new/changed files
-  python3 scripts/state.py update <file-path>        # Mark file as processed
-  python3 scripts/state.py update <file1> <file2> …  # Mark multiple files
-
-State file: ~/.cache/fit/basecamp/state/graph_processed (TSV: path<TAB>hash)
-"""
-
-import hashlib
-import os
-import sys
-from pathlib import Path
-
-STATE_FILE = Path.home() / ".cache/fit/basecamp/state/graph_processed"
-SOURCE_DIRS = [
-    Path.home() / ".cache/fit/basecamp/apple_mail",
-    Path.home() / ".cache/fit/basecamp/apple_calendar",
-]
-
-
-def file_hash(path):
-    """Compute SHA-256 hash of a file."""
-    h = hashlib.sha256()
-    with open(path, "rb") as f:
-        for chunk in iter(lambda: f.read(8192), b""):
-            h.update(chunk)
-    return h.hexdigest()
-
-
-def load_state():
-    """Load the state file into a dict of {path: hash}."""
-    state = {}
-    if STATE_FILE.exists():
-        for line in STATE_FILE.read_text().splitlines():
-            parts = line.split("\t", 1)
-            if len(parts) == 2:
-                state[parts[0]] = parts[1]
-    return state
-
-
-def save_state(state):
-    """Write the full state dict back to the state file."""
-    STATE_FILE.parent.mkdir(parents=True, exist_ok=True)
-    lines = [f"{path}\t{h}" for path, h in sorted(state.items())]
-    STATE_FILE.write_text("\n".join(lines) + "\n" if lines else "")
-
-
-def check():
-    """Find source files that are new or have changed since last processing."""
-    state = load_state()
-    new_files = []
-    for source_dir in SOURCE_DIRS:
-        if not source_dir.is_dir():
-            continue
-        for f in source_dir.iterdir():
-            if not f.is_file():
-                continue
-            path_str = str(f)
-            h = file_hash(f)
-            if state.get(path_str) != h:
-                new_files.append(path_str)
-    for f in sorted(new_files):
-        print(f)
-    return len(new_files)
-
-
-def update(file_paths):
-    """Mark files as processed by updating their hashes in state."""
-    state = load_state()
-    for fp in file_paths:
-        p = Path(fp)
-        if not p.exists():
-            print(f"Warning: File not found: {fp}", file=sys.stderr)
-            continue
-        state[str(p)] = file_hash(p)
-    save_state(state)
-    print(f"Updated {len(file_paths)} file(s) in graph state")
-
-
-if __name__ == "__main__":
-    if len(sys.argv) < 2:
-        print(__doc__, file=sys.stderr)
-        sys.exit(1)
-
-    cmd = sys.argv[1]
-    if cmd == "check":
-        count = check()
-        print(f"\n{count} file(s) to process", file=sys.stderr)
-    elif cmd == "update" and len(sys.argv) >= 3:
-        update(sys.argv[2:])
-    else:
-        print(__doc__, file=sys.stderr)
-        sys.exit(1)

package/template/.claude/skills/organize-files/scripts/organize-by-type.sh

@@ -1,42 +0,0 @@
-#!/bin/bash
-# Organize files in a directory by type into subdirectories.
-#
-# Usage: bash scripts/organize-by-type.sh <directory>
-#
-# Creates subdirectories (Documents, Images, Archives, Installers, Screenshots)
-# and moves matching files. Only operates on top-level files (-maxdepth 1).
-# Prints each move with -v flag. Does NOT delete any files.
-
-set -euo pipefail
-
-if [ $# -ne 1 ]; then
-  echo "Usage: bash scripts/organize-by-type.sh <directory>" >&2
-  exit 1
-fi
-
-DIR="$1"
-
-if [ ! -d "$DIR" ]; then
-  echo "Error: Directory not found: $DIR" >&2
-  exit 1
-fi
-
-# Create subdirectories
-mkdir -p "$DIR"/{Documents,Images,Archives,Installers,Screenshots}
-
-# Screenshots
-find "$DIR" -maxdepth 1 -type f \( -name "Screenshot*" -o -name "Screen Shot*" \) -exec mv -v {} "$DIR/Screenshots/" \;
-
-# Documents
-find "$DIR" -maxdepth 1 -type f \( -name "*.pdf" -o -name "*.doc*" -o -name "*.txt" -o -name "*.md" -o -name "*.rtf" -o -name "*.csv" -o -name "*.xlsx" \) -exec mv -v {} "$DIR/Documents/" \;
-
-# Images (excluding screenshots already moved)
-find "$DIR" -maxdepth 1 -type f \( -name "*.png" -o -name "*.jpg" -o -name "*.jpeg" -o -name "*.gif" -o -name "*.webp" \) -exec mv -v {} "$DIR/Images/" \;
-
-# Archives
-find "$DIR" -maxdepth 1 -type f \( -name "*.zip" -o -name "*.tar.gz" -o -name "*.rar" \) -exec mv -v {} "$DIR/Archives/" \;
-
-# Installers
-find "$DIR" -maxdepth 1 -type f -name "*.dmg" -exec mv -v {} "$DIR/Installers/" \;
-
-echo "Organization complete: $DIR"

package/template/.claude/skills/organize-files/scripts/summarize.sh

@@ -1,21 +0,0 @@
-#!/bin/bash
-# Summarize the contents of ~/Desktop/ and ~/Downloads/.
-#
-# Usage: bash scripts/summarize.sh
-#
-# Counts files by type in both directories (top-level only).
-
-set -euo pipefail
-
-for dir in "$HOME/Desktop" "$HOME/Downloads"; do
-  [ -d "$dir" ] || continue
-  echo "=== $(basename "$dir") ==="
-  echo "Screenshots: $(find "$dir" -maxdepth 1 \( -name 'Screenshot*' -o -name 'Screen Shot*' \) 2>/dev/null | wc -l | tr -d ' ')"
-  echo "PDFs:        $(find "$dir" -maxdepth 1 -name '*.pdf' 2>/dev/null | wc -l | tr -d ' ')"
-  echo "Images:      $(find "$dir" -maxdepth 1 \( -name '*.png' -o -name '*.jpg' -o -name '*.jpeg' -o -name '*.gif' -o -name '*.webp' \) 2>/dev/null | wc -l | tr -d ' ')"
-  echo "Documents:   $(find "$dir" -maxdepth 1 \( -name '*.doc*' -o -name '*.txt' -o -name '*.md' -o -name '*.rtf' \) 2>/dev/null | wc -l | tr -d ' ')"
-  echo "Archives:    $(find "$dir" -maxdepth 1 \( -name '*.zip' -o -name '*.tar.gz' -o -name '*.rar' \) 2>/dev/null | wc -l | tr -d ' ')"
-  echo "Installers:  $(find "$dir" -maxdepth 1 -name '*.dmg' 2>/dev/null | wc -l | tr -d ' ')"
-  echo "Other:       $(find "$dir" -maxdepth 1 -type f ! \( -name 'Screenshot*' -o -name 'Screen Shot*' -o -name '*.pdf' -o -name '*.png' -o -name '*.jpg' -o -name '*.jpeg' -o -name '*.gif' -o -name '*.webp' -o -name '*.doc*' -o -name '*.txt' -o -name '*.md' -o -name '*.rtf' -o -name '*.zip' -o -name '*.tar.gz' -o -name '*.rar' -o -name '*.dmg' -o -name '.DS_Store' -o -name '.localized' \) 2>/dev/null | wc -l | tr -d ' ')"
-  echo ""
-done