pawmode 1.0.0

package/skills/c-display/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: c-display
+description: Control display brightness and safely move files to trash instead of permanently deleting with rm.
+tags: [display, brightness, trash, safety]
+---
+
+# Display & Safety
+
+## brightness
+
+```bash
+# Get current brightness (0.0 to 1.0)
+brightness -l
+
+# Set brightness to 80%
+brightness 0.8
+
+# Set brightness to minimum
+brightness 0.0
+
+# Set brightness to maximum
+brightness 1.0
+```
+
+## trash (macos-trash)
+
+Safe alternative to `rm` — moves files to macOS Trash:
+
+```bash
+# Move file to trash
+trash file.txt
+
+# Move multiple files
+trash file1.txt file2.txt dir/
+
+# Move with confirmation prompt
+trash --interactive file.txt
+```
+
+## Guidelines
+
+- Use `trash` instead of `rm` when the user might want to recover files
+- Use `rm` only for temporary/generated files where recovery isn't needed
+- Brightness value is 0.0 (off) to 1.0 (max)
+- `brightness -l` lists all displays when multiple monitors connected

package/skills/c-email/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: c-email
+description: Read, send, search, and label email via gog (Gmail CLI) or himalaya (IMAP). Supports inbox management, drafting replies, thread viewing, and label/folder operations across Gmail and standard IMAP accounts.
+tags: [email, gmail, imap, gog, himalaya, inbox]
+---
+
+This skill manages email via `gog` (Gmail) or `himalaya` (IMAP). Check availability with `which gog himalaya`.
+
+## Gmail — `gog mail` (gogcli)
+
+```bash
+gog mail list                              # List inbox messages
+gog mail list --label "INBOX" --max 20
+gog mail read <message-id>                 # Read a message
+gog mail send --to "user@example.com" --subject "Subject" --body "Body"
+gog mail reply <message-id> --body "Reply text"
+gog mail search "from:alice subject:report"
+gog mail search "is:unread after:2026/02/01"
+gog mail label add <message-id> "Label"
+gog mail label remove <message-id> "INBOX"
+gog mail archive <message-id>
+gog mail trash <message-id>
+gog mail labels                            # List all labels
+gog mail thread <thread-id>                # View full thread
+```
+
+## IMAP — `himalaya`
+
+```bash
+himalaya list                              # List inbox
+himalaya list -m 50                        # List last 50 messages
+himalaya read <id>                         # Read message
+himalaya write                             # Compose new message (interactive)
+himalaya send --to "user@example.com" --subject "Subj" < body.txt
+himalaya reply <id>
+himalaya forward <id>
+himalaya search "subject:report"
+himalaya move <id> "Archive"               # Move to folder
+himalaya delete <id>
+himalaya folders                           # List folders
+himalaya --account work list               # Use a specific account
+```
+
+## Usage Guidelines
+
+- Prefer `gog` for Gmail accounts; prefer `himalaya` for non-Gmail IMAP.
+- Use `gog mail search` with Gmail search syntax (from:, to:, subject:, is:unread, has:attachment).
+- For sending with body content, pass the body directly or pipe a file.
+- Both tools require prior authentication setup.
+
+## Notes
+
+- `gog` requires Google OAuth configured via `gog auth`.
+- `himalaya` requires IMAP credentials in `~/.config/himalaya/config.toml`.

package/skills/c-files/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: c-files
+description: Sync files to Google Drive, S3, Dropbox, OneDrive, and 70+ cloud providers using rclone.
+tags: [files, cloud, sync, backup, storage]
+---
+
+# Cloud Files (rclone)
+
+```bash
+# List configured remotes
+rclone listremotes
+
+# List files in a remote
+rclone ls remote:path
+rclone lsd remote:path    # directories only
+
+# Copy files to/from cloud
+rclone copy local/path remote:path
+rclone copy remote:path local/path
+
+# Sync (make remote match local — deletes extra files on remote)
+rclone sync local/path remote:path
+
+# Move files
+rclone move local/path remote:path
+
+# Interactive file explorer
+rclone ncdu remote:path
+
+# Mount cloud storage as local folder
+rclone mount remote:path /mnt/cloud --daemon
+
+# Check for differences
+rclone check local/path remote:path
+
+# Show storage usage
+rclone about remote:
+```
+
+## Setup
+
+Run `rclone config` to add remotes. Supports:
+- Google Drive, S3, Dropbox, OneDrive, Backblaze B2
+- Azure Blob, SFTP, FTP, WebDAV
+- 70+ providers total
+
+## Guidelines
+
+- `rclone sync` deletes files on destination — use `rclone copy` if unsure
+- Always confirm before sync operations that delete remote files
+- Use `--dry-run` flag to preview what would change
+- Use `rclone check` to verify files match without transferring

package/skills/c-github/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: c-github
+description: Interact with GitHub using the `gh` CLI and `jq`. Manage PRs, issues, repositories, and Actions workflows. Make raw API calls with `gh api` for anything not covered by built-in commands.
+tags: [github, git, prs, issues, actions, ci, repos, api]
+---
+
+## What This Skill Does
+
+Uses `gh` (GitHub CLI) and `jq` to manage GitHub resources including pull requests, issues, repositories, and Actions. Supports raw API calls for advanced queries.
+
+## CLI Tools: `gh` + `jq`
+
+### Pull Requests
+
+```bash
+gh pr list                          # List open PRs
+gh pr view 123                      # View PR details
+gh pr create --title "Fix bug" --body "..." --base main
+gh pr merge 123 --squash
+gh pr checkout 123
+gh pr review 123 --approve
+```
+
+### Issues
+
+```bash
+gh issue list --state open
+gh issue view 42
+gh issue create --title "Bug" --body "..." --label bug
+gh issue close 42
+gh issue comment 42 --body "Fixed in #123"
+```
+
+### Actions / CI
+
+```bash
+gh run list                         # List recent workflow runs
+gh run view 123456789               # View run details
+gh run watch                        # Watch current run live
+gh workflow run deploy.yml
+```
+
+### API Calls with `jq`
+
+```bash
+gh api repos/{owner}/{repo}/pulls | jq '.[].title'
+gh api /user/repos | jq '.[].full_name'
+gh api graphql -f query='{ viewer { login } }'
+```
+
+## Usage Guidelines
+
+1. Default to the current repo context when no `--repo` flag is specified.
+2. Use `jq` to filter and format `gh api` JSON output for readability.
+3. For bulk operations, pipe `gh issue list --json number,title` into `jq`.
+4. Always confirm before closing issues or merging PRs.
+
+## Notes
+
+- Requires `gh auth login` to be completed before use.
+- Install: `brew install gh` and `brew install jq`

package/skills/c-jira/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: c-jira
+description: Manage Jira issues using `jira` (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
+tags: [jira, issues, project-management, sprints, tickets, atlassian]
+---
+
+## What This Skill Does
+
+Uses `jira` (jira-cli) to interact with Jira projects — listing issues, creating tickets, moving issues through workflow transitions, and managing sprints.
+
+## CLI Tool: `jira`
+
+### List & View Issues
+
+```bash
+jira issue list                             # List issues assigned to you
+jira issue list --project MYPROJ            # Filter by project
+jira issue list --status "In Progress"      # Filter by status
+jira issue list --type Bug                  # Filter by issue type
+jira issue view MYPROJ-123                  # View issue details
+```
+
+### Create Issues
+
+```bash
+jira issue create \
+  --project MYPROJ \
+  --type Bug \
+  --summary "Login page throws 500 error" \
+  --body "Steps to reproduce: ..." \
+  --priority High \
+  --label backend
+```
+
+### Transitions
+
+```bash
+jira issue move MYPROJ-123 "In Progress"
+jira issue move MYPROJ-123 "Done"
+jira issue move MYPROJ-123 "In Review"
+```
+
+### Comments
+
+```bash
+jira issue comment add MYPROJ-123 --body "Fixed in PR #456"
+```
+
+### Sprints
+
+```bash
+jira sprint list --project MYPROJ           # List sprints
+jira sprint add MYPROJ-123 --sprint 42      # Add issue to sprint
+```
+
+## Usage Guidelines
+
+1. Always use the full issue key (e.g., `MYPROJ-123`) in commands.
+2. Run `jira issue list` before creating tickets to check for existing duplicates.
+3. Use `jira issue move` to transition issues — confirm the valid transition names with `jira issue view` first.
+4. When the user says "close" or "resolve" an issue, use the appropriate transition name for their workflow.
+
+## Notes
+
+- Requires `jira init` to configure server URL and credentials before use.
+- Install: `brew install ankitpokhrel/jira-cli/jira-cli`

package/skills/c-lights/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: c-lights
+description: Control Philips Hue smart lights using the `openhue` CLI. Turn lights on/off, adjust brightness and color, activate scenes, and manage rooms and groups.
+tags: [hue, lights, smart-home, openhue, philips, automation]
+---
+
+## What This Skill Does
+
+Enables Claude to control Philips Hue smart lighting — individual bulbs, rooms, and scenes — using the `openhue` CLI.
+
+## Available CLI Tool: `openhue`
+
+### Common Commands
+
+```bash
+# List all lights
+openhue get lights
+
+# List all rooms/groups
+openhue get rooms
+
+# Turn a light on or off
+openhue set light "Desk Lamp" --on
+openhue set light "Desk Lamp" --off
+
+# Set brightness (0-100)
+openhue set light "Bedroom" --brightness 75
+
+# Set color by name or hex
+openhue set light "Living Room" --color red
+openhue set light "Living Room" --color "#FF6600"
+
+# Set color temperature (warm to cool, in mirek)
+openhue set light "Kitchen" --color-temp 370
+
+# Control an entire room
+openhue set room "Living Room" --on --brightness 80
+
+# List available scenes
+openhue get scenes
+
+# Activate a scene
+openhue set scene "Relax" --room "Living Room"
+```
+
+## Usage Guidelines
+
+- Use room-level commands when the user refers to a space, not a specific bulb
+- Brightness is 0–100; color-temp ranges roughly 153 (cool) to 500 (warm)
+- List lights/rooms first if unsure of exact names
+
+## Notes
+
+- Requires `openhue` configured with your Hue Bridge IP and API key
+- Bridge must be on the same local network

package/skills/c-linear/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: c-linear
+description: Manage Linear issues and projects using the `linear` CLI. List and filter issues, create new issues, update status, start work on a branch, and create linked pull requests directly from the terminal.
+tags: [linear, issues, project-management, tasks, sprint, prs]
+---
+
+## What This Skill Does
+
+Uses the `linear` CLI to manage Linear issues — list, create, update, and transition issues, as well as start work and create linked PRs.
+
+## CLI Tool: `linear`
+
+### List & View Issues
+
+```bash
+linear issue list                          # List your assigned issues
+linear issue list --team ENG               # Filter by team
+linear issue list --state "In Progress"    # Filter by state
+linear issue view ENG-123                  # View issue details
+```
+
+### Create Issues
+
+```bash
+linear issue create \
+  --title "Fix login redirect bug" \
+  --description "Users are redirected to /home instead of /dashboard" \
+  --team ENG \
+  --priority 2 \
+  --label bug
+```
+
+### Update & Transition Issues
+
+```bash
+linear issue update ENG-123 --state "In Progress"
+linear issue update ENG-123 --assignee me
+linear issue update ENG-123 --priority 1
+```
+
+### Start Work
+
+```bash
+# Creates a git branch linked to the issue
+linear issue start ENG-123
+```
+
+### Create a PR
+
+```bash
+# Creates a PR linked to the Linear issue
+linear pr create ENG-123
+```
+
+## Usage Guidelines
+
+1. Use `linear issue list` before creating issues to avoid duplicates.
+2. When starting work, `linear issue start` handles branch creation and status update in one command.
+3. Use issue identifiers (e.g., `ENG-123`) consistently — they are case-insensitive.
+
+## Notes
+
+- Requires `linear auth` to be completed before use.
+- Priority levels: 1 = Urgent, 2 = High, 3 = Medium, 4 = Low

package/skills/c-location/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: c-location
+description: Search Apple Maps, find nearby places, and get directions using the `goplaces` CLI. Supports keyword searches, category filters (restaurants, coffee, gas), and turn-by-turn directions by driving, walking, or transit.
+tags: [maps, location, apple-maps, directions, places, search]
+---
+
+## What This Skill Does
+
+Queries Apple Maps via the `goplaces` CLI to search for places, find businesses nearby, and get directions between locations.
+
+## CLI Tool: `goplaces`
+
+### Common Commands
+
+```bash
+# Search for a place by name or keyword
+goplaces search "coffee shops near downtown Austin"
+
+# Find nearby places by category
+goplaces nearby "pizza"
+goplaces nearby "gas station"
+
+# Get directions between two locations
+goplaces directions "Austin TX" "San Antonio TX"
+goplaces directions --mode walking "Zilker Park" "South Congress Ave"
+
+# Get details about a specific place
+goplaces details "Barton Springs Pool, Austin"
+```
+
+### Transport Modes
+
+- `--mode driving` (default)
+- `--mode walking`
+- `--mode transit`
+
+## Usage Guidelines
+
+1. Use natural language for location queries — `goplaces` handles geocoding automatically.
+2. For "nearby" searches, the current device location is used unless a starting point is specified.
+3. When providing directions, confirm origin and destination with the user if ambiguous.
+4. Present results as a numbered list when multiple places are returned.
+
+## Notes
+
+- Requires macOS with location services enabled for proximity searches.
+- Results are sourced from Apple Maps — coverage quality varies by region.

package/skills/c-memory/SKILL.md

@@ -0,0 +1,86 @@
+---
+name: c-memory
+description: Persistent memory across Claude Code sessions — remember facts, preferences, and context
+tags: [memory, context, persistence]
+---
+
+# Memory — Persistent Context
+
+Store and recall facts, preferences, and context across Claude Code sessions.
+
+## How It Works
+
+Memory lives in `~/.claude/memory/` as plain markdown files. Read them at session start, write to them when you learn something important.
+
+## Directory Structure
+
+```
+~/.claude/memory/
+├── MEMORY.md          # Key facts — always read this first
+├── people.md          # People the user mentions (names, roles, preferences)
+├── preferences.md     # User preferences (tools, workflows, habits)
+├── projects.md        # Active projects and their context
+└── journal.md         # Session log — append-only, dated entries
+```
+
+## Session Start
+
+At the beginning of every session, read `~/.claude/memory/MEMORY.md` to load context. This file should be concise — under 100 lines.
+
+## When to Save
+
+Save to memory when the user:
+- Shares their name, role, or preferences
+- Mentions people they work with
+- Describes a project or recurring task
+- Says "remember this" or "don't forget"
+- Corrects you about something
+
+## Writing Rules
+
+- **MEMORY.md**: Key facts only. Keep under 100 lines. Update, don't append.
+- **people.md**: Name, role, relationship, preferences. One section per person.
+- **preferences.md**: Tools, workflows, communication preferences.
+- **projects.md**: Project name, status, key files, context.
+- **journal.md**: Append a dated entry at the end of each session summarizing what was done.
+
+## Commands
+
+```bash
+# Read memory
+cat ~/.claude/memory/MEMORY.md
+
+# List memory files
+ls ~/.claude/memory/
+
+# Append to journal
+echo "## $(date +%Y-%m-%d)" >> ~/.claude/memory/journal.md
+```
+
+## Example MEMORY.md
+
+```markdown
+# Memory
+
+## User
+- Name: Alex
+- Role: Frontend developer
+- Prefers TypeScript, uses Neovim
+- Timezone: PST
+
+## Active Projects
+- ctrl.build — DeFi workflow automation (Next.js + Solidity)
+- openpaw — CLI tool for Claude Code setup
+
+## Preferences
+- Concise responses, no emoji unless asked
+- Always use bun instead of npm
+- Dark mode everything
+```
+
+## Guidelines
+
+- Never store passwords, API keys, or secrets in memory files
+- Always ask before overwriting existing memory entries
+- If memory files don't exist, create them on first write
+- Keep MEMORY.md focused — move details to topic-specific files

package/skills/c-messaging/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: c-messaging
+description: Send and read messages via imsg (iMessage) and wacli (WhatsApp). Supports sending to individuals or groups, reading recent conversations, and checking unread messages across both platforms.
+tags: [messaging, imessage, whatsapp, imsg, wacli, sms]
+---
+
+This skill manages messaging via `imsg` (iMessage/SMS) and `wacli` (WhatsApp). Check availability with `which imsg wacli`.
+
+## iMessage & SMS — `imsg`
+
+```bash
+imsg send "Phone or Email" "Message text"  # Send a message
+imsg send "+14155551234" "Hello!"
+imsg send "user@icloud.com" "Hey there"
+imsg list                                   # List recent conversations
+imsg list --limit 10                        # Last 10 conversations
+imsg read "+14155551234"                    # Read conversation with contact
+imsg read "+14155551234" --limit 20         # Read last 20 messages
+imsg unread                                 # Show unread messages
+imsg group send "Group Name" "Message"      # Send to a group chat
+imsg group list                             # List group chats
+imsg contacts                               # List contacts
+```
+
+## WhatsApp — `wacli`
+
+```bash
+wacli send "+14155551234" "Message text"    # Send a message
+wacli send "Contact Name" "Hello!"          # Send by name (if in contacts)
+wacli list                                  # List recent chats
+wacli read "+14155551234"                   # Read conversation
+wacli read "+14155551234" --limit 20
+wacli unread                                # Show unread messages
+wacli group list                            # List WhatsApp groups
+wacli group send "Group Name" "Message"
+wacli status "Your status text"            # Set WhatsApp status
+```
+
+## Usage Guidelines
+
+- Use `imsg` for iMessage/SMS to Apple devices or phone numbers.
+- Use `wacli` for WhatsApp contacts.
+- Phone numbers should include country code (e.g., +1 for US).
+- Check `imsg unread` or `wacli unread` before sending follow-ups.
+- If a contact name is ambiguous, prefer using the phone number directly.
+
+## Notes
+
+- `imsg` requires macOS and an active iMessage account.
+- `wacli` requires WhatsApp to be linked — run `wacli auth` to scan QR code on first use.
+- Both tools operate locally; no cloud API credentials required after initial auth.

package/skills/c-music/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: c-music
+description: Control Spotify playback using the `spogo` CLI. Play, pause, skip, search tracks/albums/playlists, manage the queue, and browse your library.
+tags: [spotify, music, playback, spogo, audio]
+---
+
+## What This Skill Does
+
+Enables Claude to control Spotify playback and search music via the `spogo` CLI tool.
+
+## Available CLI Tool: `spogo`
+
+### Common Commands
+
+```bash
+# Play/pause toggle
+spogo play
+spogo pause
+
+# Skip to next or previous track
+spogo next
+spogo prev
+
+# Search and play a track
+spogo search track "Bohemian Rhapsody" --play
+
+# Search an album and play it
+spogo search album "Dark Side of the Moon" --play
+
+# Search playlists
+spogo search playlist "chill vibes"
+
+# Play a specific playlist by name or URI
+spogo playlist play "My Playlist"
+
+# Add current track to queue
+spogo queue add "spotify:track:TRACK_ID"
+
+# Show current playback status
+spogo status
+
+# Set volume (0-100)
+spogo volume 60
+
+# List your saved playlists
+spogo playlist list
+```
+
+## Usage Guidelines
+
+- Use `spogo status` first to check what is currently playing
+- When searching, confirm the result with the user before playing if ambiguous
+- Volume is a 0–100 integer scale
+
+## Notes
+
+- Requires `spogo` configured with Spotify OAuth credentials
+- Playback requires an active Spotify Premium account
+- Spotify must be open on at least one device for commands to work