reeboot 1.0.0 → 1.3.0

package/skills/files/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: files
+description: Local filesystem operations — read files, list directories, search with find/grep, write files. Use when reading, writing, searching, or managing local files and directories.
+---
+
+# Files
+
+Local filesystem operations using standard shell tools. No external dependencies beyond bash.
+
+## Setup
+
+No installation required — all tools (`cat`, `ls`, `find`, `grep`, `head`, `tail`) are built into macOS and Linux.
+
+**Protected paths**: reeboot's protected-paths extension blocks access to sensitive directories (e.g., `~/.ssh`, `~/.reeboot/credentials`). The agent will refuse to read or modify files in these paths.
+
+Check which paths are protected:
+```bash
+# The protected-paths extension documents blocked directories
+# Default blocked: ~/.ssh, ~/.gnupg, /etc/passwd, /etc/shadow, ~/.reeboot/credentials
+```
+
+## Usage
+
+### Reading files
+
+```bash
+# Read an entire file
+cat /path/to/file.txt
+
+# Read first N lines
+head -n 50 /path/to/file.txt
+
+# Read last N lines
+tail -n 100 /path/to/file.log
+
+# Read a specific range of lines
+sed -n '10,30p' /path/to/file.txt
+```
+
+### Listing directories
+
+```bash
+# List with details
+ls -la /path/to/directory
+
+# List recursively (shallow)
+ls -la /path/to/directory/
+
+# Tree view (if available)
+find /path/to/directory -maxdepth 2 -print | sed 's|[^/]*/|  |g'
+```
+
+### Searching
+
+```bash
+# Search file contents
+grep -r "pattern" /path/to/directory
+grep -r "TODO" . --include="*.ts"
+grep -n "function auth" src/auth.ts
+
+# Find files by name
+find /path -name "*.json" -type f
+find . -name "*.log" -mtime -7   # modified in last 7 days
+
+# Find and grep
+find . -name "*.ts" | xargs grep "import.*config"
+```
+
+### Writing files
+
+```bash
+# Write (overwrite) a file
+echo "content" > /path/to/file.txt
+cat > /path/to/file.txt << 'HEREDOC'
+multi-line
+content here
+HEREDOC
+
+# Append to a file
+echo "new line" >> /path/to/file.log
+
+# Copy a file
+cp /source/file.txt /dest/file.txt
+
+# Move/rename a file
+mv /old/path.txt /new/path.txt
+```
+
+### Safe practices
+
+- Always `head` or `wc -l` a file before `cat` if you don't know its size
+- Use `find` with `-maxdepth` to avoid traversing huge directory trees
+- Prefer `cat` over editors for reading; use redirect operators for writing
+- Check file size first: `ls -lh /path/to/file`

package/skills/gcal/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: gcal
+description: Google Calendar operations via gccli — list events, create meetings, update or delete events, check free/busy. Use when managing calendar events, scheduling meetings, or checking availability.
+---
+
+# Google Calendar
+
+Wraps `gccli` (`@mariozechner/gccli`) for Google Calendar operations — list, create, update, delete events, and free/busy queries.
+
+## Setup
+
+1. Install gccli:
+   ```
+   npm install -g @mariozechner/gccli
+   ```
+
+2. Use the same GCP project as the Gmail skill (or create a new one):
+   - Enable the **Google Calendar API** under APIs & Services → Library
+   - Use the same OAuth 2.0 Desktop credentials JSON (or create new ones)
+
+3. Configure gccli with your credentials:
+   ```
+   gccli accounts credentials ~/path/to/credentials.json
+   ```
+
+4. Add your Google account:
+   ```
+   gccli accounts add user@gmail.com
+   ```
+   Follow the browser OAuth consent flow.
+
+5. Verify:
+   ```
+   gccli accounts list
+   gccli user@gmail.com list --days 1
+   ```
+
+## Usage
+
+```bash
+# List upcoming events (next 7 days)
+gccli user@gmail.com list --days 7
+
+# List events in a date range
+gccli user@gmail.com list --from 2026-03-21 --to 2026-03-28
+
+# Create an event
+gccli user@gmail.com create \
+  --title "Team Standup" \
+  --start "2026-03-21T09:00" \
+  --end "2026-03-21T09:30" \
+  --description "Daily sync"
+
+# Create an all-day event
+gccli user@gmail.com create \
+  --title "Conference" \
+  --date "2026-03-21"
+
+# Update an event
+gccli user@gmail.com update <eventId> --title "New Title"
+
+# Delete an event
+gccli user@gmail.com delete <eventId>
+
+# Check free/busy
+gccli user@gmail.com freebusy \
+  --from "2026-03-21T08:00" \
+  --to "2026-03-21T18:00"
+```

package/skills/gdrive/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: gdrive
+description: Google Drive operations via gdcli — list files, read documents, search, upload, and share. Use when accessing, reading, or managing files in Google Drive.
+---
+
+# Google Drive
+
+Wraps `gdcli` (`@mariozechner/gdcli`) for Google Drive operations — list, read, search, upload, and share files.
+
+## Setup
+
+1. Install gdcli:
+   ```
+   npm install -g @mariozechner/gdcli
+   ```
+
+2. Use the same GCP project as the Gmail/Calendar skills (or create a new one):
+   - Enable the **Google Drive API** under APIs & Services → Library
+   - Use the same OAuth 2.0 Desktop credentials JSON
+
+3. Configure gdcli with your credentials:
+   ```
+   gdcli accounts credentials ~/path/to/credentials.json
+   ```
+
+4. Add your Google account:
+   ```
+   gdcli accounts add user@gmail.com
+   ```
+   Follow the browser OAuth consent flow.
+
+5. Verify:
+   ```
+   gdcli accounts list
+   gdcli user@gmail.com list --limit 5
+   ```
+
+## Usage
+
+```bash
+# List files in root
+gdcli user@gmail.com list --limit 20
+
+# List files in a folder
+gdcli user@gmail.com list --folder <folderId>
+
+# Search files
+gdcli user@gmail.com search "quarterly report"
+gdcli user@gmail.com search "type:spreadsheet name:budget"
+
+# Read a file (returns text content)
+gdcli user@gmail.com read <fileId>
+
+# Upload a file
+gdcli user@gmail.com upload /path/to/file.pdf --name "Report Q1"
+
+# Upload to a specific folder
+gdcli user@gmail.com upload /path/to/file.pdf --folder <folderId>
+
+# Share a file
+gdcli user@gmail.com share <fileId> --email colleague@example.com --role reader
+
+# Get file metadata
+gdcli user@gmail.com info <fileId>
+```

package/skills/github/SKILL.md

@@ -0,0 +1,80 @@
+---
+name: github
+description: GitHub operations via gh CLI — issues, PRs, releases, code search, GitHub Actions workflows. Use when working with GitHub repositories, managing issues, reviewing pull requests, or automating GitHub tasks.
+---
+
+# GitHub
+
+Wraps the `gh` CLI for GitHub operations — issues, pull requests, releases, code search, and GitHub Actions.
+
+## Setup
+
+1. Install the GitHub CLI:
+   ```
+   brew install gh           # macOS
+   # or: https://cli.github.com/
+   ```
+
+2. Authenticate:
+   ```
+   gh auth login
+   ```
+   Follow the prompts to authenticate via browser or token.
+
+3. Verify:
+   ```
+   gh auth status
+   ```
+
+## Usage
+
+### Issues
+
+```bash
+gh issue list --repo owner/repo --state open --limit 20
+gh issue view 123 --repo owner/repo
+gh issue create --title "Bug: ..." --body "..." --label bug
+gh issue close 123
+```
+
+### Pull Requests
+
+```bash
+gh pr list --repo owner/repo --state open
+gh pr view 456 --repo owner/repo
+gh pr create --title "Feature: ..." --body "..." --base main
+gh pr merge 456 --squash
+gh pr review 456 --approve
+```
+
+### Releases
+
+```bash
+gh release list --repo owner/repo
+gh release create v1.2.3 --title "v1.2.3" --notes "Changelog..."
+gh release view v1.2.3
+```
+
+### Code Search
+
+```bash
+gh search code "function authenticate" --repo owner/repo
+gh search issues "memory leak" --repo owner/repo
+```
+
+### GitHub Actions
+
+```bash
+gh run list --repo owner/repo --limit 10
+gh run view 789 --repo owner/repo
+gh run watch 789
+gh workflow run deploy.yml --ref main
+```
+
+### Repos
+
+```bash
+gh repo list --limit 20
+gh repo clone owner/repo
+gh repo view owner/repo
+```

package/skills/gmail/SKILL.md

@@ -0,0 +1,68 @@
+---
+name: gmail
+description: Gmail operations via gmcli — search emails, read threads, send messages, manage labels, handle attachments. Use when working with Gmail: reading, searching, sending, or organising emails.
+---
+
+# Gmail
+
+Wraps `gmcli` (`@mariozechner/gmcli`) for Gmail operations — search, read, send, draft, labels, attachments.
+
+## Setup
+
+1. Install gmcli:
+   ```
+   npm install -g @mariozechner/gmcli
+   ```
+
+2. Create a GCP project and enable the Gmail API:
+   - Go to https://console.cloud.google.com/
+   - Create a new project (or use an existing one)
+   - Enable the **Gmail API** under APIs & Services → Library
+   - Create **OAuth 2.0 Desktop credentials**: APIs & Services → Credentials → Create Credentials → OAuth client ID → Desktop app
+   - Download the credentials JSON file
+
+3. Configure gmcli with your credentials:
+   ```
+   gmcli accounts credentials ~/path/to/credentials.json
+   ```
+
+4. Add your Gmail account:
+   ```
+   gmcli accounts add user@gmail.com
+   ```
+   This opens a browser for OAuth consent. Grant the requested permissions.
+
+5. Verify:
+   ```
+   gmcli accounts list
+   ```
+
+## Usage
+
+```bash
+# Search emails
+gmcli user@gmail.com search "from:boss@company.com is:unread"
+gmcli user@gmail.com search "subject:invoice after:2025/01/01"
+
+# Read a thread
+gmcli user@gmail.com thread <threadId>
+
+# Send an email
+gmcli user@gmail.com send \
+  --to recipient@example.com \
+  --subject "Hello" \
+  --body "Message content here"
+
+# Send with attachment
+gmcli user@gmail.com send \
+  --to recipient@example.com \
+  --subject "Report" \
+  --body "See attached" \
+  --attach /path/to/report.pdf
+
+# List labels
+gmcli user@gmail.com labels list
+
+# List unread in inbox
+gmcli user@gmail.com search "in:inbox is:unread" --limit 10
+```

package/skills/hubspot/SKILL.md

@@ -0,0 +1,77 @@
+---
+name: hubspot
+description: HubSpot CRM operations via HUBSPOT_ACCESS_TOKEN and curl — manage contacts, deals, companies, pipelines, and notes via the HubSpot v3 API. Use when working with CRM data in HubSpot.
+---
+
+# HubSpot
+
+Uses `HUBSPOT_ACCESS_TOKEN` env var + curl against the HubSpot CRM v3 API to manage contacts, deals, companies, pipelines, and notes.
+
+## Setup
+
+1. Create a Private App in HubSpot:
+   - Go to HubSpot Settings → **Integrations** → **Private Apps**
+   - Click **Create a private app**
+   - Name it (e.g., "reeboot-agent")
+   - Under **Scopes**, add:
+     - `crm.objects.contacts.read` / `crm.objects.contacts.write`
+     - `crm.objects.deals.read` / `crm.objects.deals.write`
+     - `crm.objects.companies.read` / `crm.objects.companies.write`
+     - `crm.objects.notes.read` / `crm.objects.notes.write`
+   - Click **Create app** → copy the **Access token** (starts with `pat-`)
+
+2. Set the environment variable:
+   ```
+   export HUBSPOT_ACCESS_TOKEN=pat-na1-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
+   ```
+   Add to your shell profile for persistence.
+
+3. Verify:
+   ```
+   curl -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+        https://api.hubapi.com/crm/v3/objects/contacts?limit=1
+   ```
+
+## Usage
+
+```bash
+# List contacts
+curl -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+     "https://api.hubapi.com/crm/v3/objects/contacts?limit=20&properties=firstname,lastname,email"
+
+# Search contacts
+curl -X POST \
+  -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+  -H "Content-Type: application/json" \
+  "https://api.hubapi.com/crm/v3/objects/contacts/search" \
+  -d '{"filterGroups": [{"filters": [{"propertyName": "email", "operator": "EQ", "value": "john@example.com"}]}]}'
+
+# Create a contact
+curl -X POST \
+  -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+  -H "Content-Type: application/json" \
+  "https://api.hubapi.com/crm/v3/objects/contacts" \
+  -d '{"properties": {"email": "new@example.com", "firstname": "New", "lastname": "Contact"}}'
+
+# List deals
+curl -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+     "https://api.hubapi.com/crm/v3/objects/deals?limit=20&properties=dealname,amount,closedate,dealstage"
+
+# Create a deal
+curl -X POST \
+  -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+  -H "Content-Type: application/json" \
+  "https://api.hubapi.com/crm/v3/objects/deals" \
+  -d '{"properties": {"dealname": "New Deal", "amount": "10000", "closedate": "2026-06-30", "pipeline": "default", "dealstage": "appointmentscheduled"}}'
+
+# List companies
+curl -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+     "https://api.hubapi.com/crm/v3/objects/companies?limit=20&properties=name,domain,industry"
+
+# Create a note
+curl -X POST \
+  -H "Authorization: Bearer $HUBSPOT_ACCESS_TOKEN" \
+  -H "Content-Type: application/json" \
+  "https://api.hubapi.com/crm/v3/objects/notes" \
+  -d '{"properties": {"hs_note_body": "Called customer, interested in enterprise plan.", "hs_timestamp": "2026-03-20T10:00:00Z"}}'
+```

package/skills/linear/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: linear
+description: Linear project management via LINEAR_API_KEY and GraphQL — create, list, update, and search issues and projects. Use when managing engineering tasks, sprint planning, or querying Linear issues.
+---
+
+# Linear
+
+Uses `LINEAR_API_KEY` env var + curl against the Linear GraphQL API to manage issues, projects, and teams.
+
+## Setup
+
+1. Generate a Personal API key:
+   - Go to Linear Settings → **API** → **Personal API keys**
+   - Click **Create key** → give it a label → copy the key
+
+2. Set the environment variable:
+   ```
+   export LINEAR_API_KEY=lin_api_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+   ```
+   Add to your shell profile for persistence.
+
+3. Verify:
+   ```
+   curl -X POST \
+     -H "Authorization: $LINEAR_API_KEY" \
+     -H "Content-Type: application/json" \
+     https://api.linear.app/graphql \
+     -d '{"query": "{ viewer { id name email } }"}'
+   ```
+
+## Usage
+
+All requests go to `https://api.linear.app/graphql` with `Authorization: $LINEAR_API_KEY`.
+
+```bash
+# List your assigned issues
+curl -X POST \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  https://api.linear.app/graphql \
+  -d '{
+    "query": "{ viewer { assignedIssues(first: 20) { nodes { id title state { name } priority } } } }"
+  }'
+
+# Search issues
+curl -X POST \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  https://api.linear.app/graphql \
+  -d '{
+    "query": "{ issueSearch(query: \"bug login\", first: 10) { nodes { id title state { name } assignee { name } } } }"
+  }'
+
+# Create an issue
+curl -X POST \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  https://api.linear.app/graphql \
+  -d '{
+    "query": "mutation { issueCreate(input: { teamId: \"<teamId>\", title: \"Fix login bug\", description: \"Steps to reproduce...\" }) { issue { id title } } }"
+  }'
+
+# List teams
+curl -X POST \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  https://api.linear.app/graphql \
+  -d '{"query": "{ teams { nodes { id name key } } }"}'
+
+# Update issue state
+curl -X POST \
+  -H "Authorization: $LINEAR_API_KEY" \
+  -H "Content-Type: application/json" \
+  https://api.linear.app/graphql \
+  -d '{
+    "query": "mutation { issueUpdate(id: \"<issueId>\", input: { stateId: \"<stateId>\" }) { issue { id state { name } } } }"
+  }'
+```

package/skills/notion/SKILL.md

@@ -0,0 +1,85 @@
+---
+name: notion
+description: Notion workspace operations via NOTION_API_KEY and curl — search pages, read databases, create/update blocks and pages. Use when accessing or modifying content in a Notion workspace.
+---
+
+# Notion
+
+Uses `NOTION_API_KEY` env var + curl against the Notion REST API to manage pages, databases, and blocks.
+
+## Setup
+
+1. Create a Notion internal integration:
+   - Go to https://www.notion.so/my-integrations
+   - Click **New integration**
+   - Give it a name (e.g., "reeboot-agent")
+   - Select the workspace
+   - Copy the **Internal Integration Token** (starts with `secret_`)
+
+2. Set the environment variable:
+   ```
+   export NOTION_API_KEY=secret_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
+   ```
+   Add to your shell profile (`~/.zshrc` or `~/.bashrc`) for persistence.
+
+3. Share pages/databases with the integration:
+   - Open any Notion page you want the agent to access
+   - Click **Share** (top right) → **Invite** → search for your integration name → **Invite**
+
+4. Verify:
+   ```
+   curl -H "Authorization: Bearer $NOTION_API_KEY" \
+        -H "Notion-Version: 2022-06-28" \
+        https://api.notion.com/v1/users/me
+   ```
+
+## Usage
+
+```bash
+# Search across workspace
+curl -X POST \
+  -H "Authorization: Bearer $NOTION_API_KEY" \
+  -H "Notion-Version: 2022-06-28" \
+  -H "Content-Type: application/json" \
+  https://api.notion.com/v1/search \
+  -d '{"query": "project roadmap", "filter": {"value": "page", "property": "object"}}'
+
+# List databases
+curl -X POST \
+  -H "Authorization: Bearer $NOTION_API_KEY" \
+  -H "Notion-Version: 2022-06-28" \
+  -H "Content-Type: application/json" \
+  https://api.notion.com/v1/search \
+  -d '{"filter": {"value": "database", "property": "object"}}'
+
+# Query a database
+curl -X POST \
+  -H "Authorization: Bearer $NOTION_API_KEY" \
+  -H "Notion-Version: 2022-06-28" \
+  -H "Content-Type: application/json" \
+  "https://api.notion.com/v1/databases/<database_id>/query" \
+  -d '{"filter": {"property": "Status", "select": {"equals": "In Progress"}}}'
+
+# Get a page
+curl -H "Authorization: Bearer $NOTION_API_KEY" \
+     -H "Notion-Version: 2022-06-28" \
+     "https://api.notion.com/v1/pages/<page_id>"
+
+# Get page blocks (content)
+curl -H "Authorization: Bearer $NOTION_API_KEY" \
+     -H "Notion-Version: 2022-06-28" \
+     "https://api.notion.com/v1/blocks/<page_id>/children"
+
+# Create a page
+curl -X POST \
+  -H "Authorization: Bearer $NOTION_API_KEY" \
+  -H "Notion-Version: 2022-06-28" \
+  -H "Content-Type: application/json" \
+  https://api.notion.com/v1/pages \
+  -d '{
+    "parent": {"database_id": "<database_id>"},
+    "properties": {
+      "Name": {"title": [{"text": {"content": "New page"}}]}
+    }
+  }'
+```

package/skills/postgres/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: postgres
+description: PostgreSQL database operations via psql CLI and DATABASE_URL — run queries, inspect schemas, insert data, manage tables. Use when working with a PostgreSQL database.
+---
+
+# PostgreSQL
+
+Wraps the `psql` CLI for PostgreSQL database operations. Connects via the `DATABASE_URL` environment variable.
+
+## Setup
+
+1. Install psql:
+   ```
+   brew install postgresql    # macOS (installs psql client only)
+   # or on Ubuntu/Debian: apt-get install postgresql-client
+   ```
+
+2. Set the `DATABASE_URL` environment variable:
+   ```
+   export DATABASE_URL=postgresql://user:password@host:5432/dbname
+   ```
+   Examples:
+   ```
+   export DATABASE_URL=postgresql://postgres:secret@localhost:5432/myapp
+   export DATABASE_URL=postgresql://myuser:mypass@db.example.com:5432/production
+   ```
+   Add to your shell profile for persistence.
+
+3. Verify connection:
+   ```
+   psql "$DATABASE_URL" -c "SELECT version();"
+   ```
+
+## Usage
+
+```bash
+# Run a query
+psql "$DATABASE_URL" -c "SELECT * FROM users LIMIT 10;"
+
+# Inspect tables
+psql "$DATABASE_URL" -c "\dt"
+
+# Describe a table schema
+psql "$DATABASE_URL" -c "\d users"
+
+# Count rows
+psql "$DATABASE_URL" -c "SELECT COUNT(*) FROM orders WHERE status = 'pending';"
+
+# Insert data
+psql "$DATABASE_URL" -c "INSERT INTO logs (message, created_at) VALUES ('test', NOW());"
+
+# Update data
+psql "$DATABASE_URL" -c "UPDATE users SET active = true WHERE email = 'user@example.com';"
+
+# Run a SQL file
+psql "$DATABASE_URL" -f /path/to/migration.sql
+
+# Interactive mode (use with caution)
+psql "$DATABASE_URL"
+
+# Export query result to CSV
+psql "$DATABASE_URL" -c "COPY (SELECT * FROM users) TO STDOUT WITH CSV HEADER" > users.csv
+
+# List databases
+psql "$DATABASE_URL" -c "\l"
+
+# Check active connections
+psql "$DATABASE_URL" -c "SELECT pid, usename, application_name, state FROM pg_stat_activity;"
+```
+
+### Tips
+
+- Always `LIMIT` queries on large tables to avoid returning millions of rows
+- Use `-t` flag for tuple-only output (no headers) when parsing output programmatically
+- Use `--no-password` with `DATABASE_URL` to avoid password prompts