compound-engineering-pi 0.2.3

package/plugins/compound-engineering/skills/rclone/SKILL.md

@@ -0,0 +1,150 @@
+---
+name: rclone
+description: Upload, sync, and manage files across cloud storage providers using rclone. Use when uploading files (images, videos, documents) to S3, Cloudflare R2, Backblaze B2, Google Drive, Dropbox, or any S3-compatible storage. Triggers on "upload to S3", "sync to cloud", "rclone", "backup files", "upload video/image to bucket", or requests to transfer files to remote storage.
+---
+
+# rclone File Transfer Skill
+
+## Setup Check (Always Run First)
+
+Before any rclone operation, verify installation and configuration:
+
+```bash
+# Check if rclone is installed
+command -v rclone >/dev/null 2>&1 && echo "rclone installed: $(rclone version | head -1)" || echo "NOT INSTALLED"
+
+# List configured remotes
+rclone listremotes 2>/dev/null || echo "NO REMOTES CONFIGURED"
+```
+
+### If rclone is NOT installed
+
+Guide the user to install:
+
+```bash
+# macOS
+brew install rclone
+
+# Linux (script install)
+curl https://rclone.org/install.sh | sudo bash
+
+# Or via package manager
+sudo apt install rclone  # Debian/Ubuntu
+sudo dnf install rclone  # Fedora
+```
+
+### If NO remotes are configured
+
+Walk the user through interactive configuration:
+
+```bash
+rclone config
+```
+
+**Common provider setup quick reference:**
+
+| Provider | Type | Key Settings |
+|----------|------|--------------|
+| AWS S3 | `s3` | access_key_id, secret_access_key, region |
+| Cloudflare R2 | `s3` | access_key_id, secret_access_key, endpoint (account_id.r2.cloudflarestorage.com) |
+| Backblaze B2 | `b2` | account (keyID), key (applicationKey) |
+| DigitalOcean Spaces | `s3` | access_key_id, secret_access_key, endpoint (region.digitaloceanspaces.com) |
+| Google Drive | `drive` | OAuth flow (opens browser) |
+| Dropbox | `dropbox` | OAuth flow (opens browser) |
+
+**Example: Configure Cloudflare R2**
+```bash
+rclone config create r2 s3 \
+  provider=Cloudflare \
+  access_key_id=YOUR_ACCESS_KEY \
+  secret_access_key=YOUR_SECRET_KEY \
+  endpoint=ACCOUNT_ID.r2.cloudflarestorage.com \
+  acl=private
+```
+
+**Example: Configure AWS S3**
+```bash
+rclone config create aws s3 \
+  provider=AWS \
+  access_key_id=YOUR_ACCESS_KEY \
+  secret_access_key=YOUR_SECRET_KEY \
+  region=us-east-1
+```
+
+## Common Operations
+
+### Upload single file
+```bash
+rclone copy /path/to/file.mp4 remote:bucket/path/ --progress
+```
+
+### Upload directory
+```bash
+rclone copy /path/to/folder remote:bucket/folder/ --progress
+```
+
+### Sync directory (mirror, deletes removed files)
+```bash
+rclone sync /local/path remote:bucket/path/ --progress
+```
+
+### List remote contents
+```bash
+rclone ls remote:bucket/
+rclone lsd remote:bucket/  # directories only
+```
+
+### Check what would be transferred (dry run)
+```bash
+rclone copy /path remote:bucket/ --dry-run
+```
+
+## Useful Flags
+
+| Flag | Purpose |
+|------|---------|
+| `--progress` | Show transfer progress |
+| `--dry-run` | Preview without transferring |
+| `-v` | Verbose output |
+| `--transfers=N` | Parallel transfers (default 4) |
+| `--bwlimit=RATE` | Bandwidth limit (e.g., `10M`) |
+| `--checksum` | Compare by checksum, not size/time |
+| `--exclude="*.tmp"` | Exclude patterns |
+| `--include="*.mp4"` | Include only matching |
+| `--min-size=SIZE` | Skip files smaller than SIZE |
+| `--max-size=SIZE` | Skip files larger than SIZE |
+
+## Large File Uploads
+
+For videos and large files, use chunked uploads:
+
+```bash
+# S3 multipart upload (automatic for >200MB)
+rclone copy large_video.mp4 remote:bucket/ --s3-chunk-size=64M --progress
+
+# Resume interrupted transfers
+rclone copy /path remote:bucket/ --progress --retries=5
+```
+
+## Verify Upload
+
+```bash
+# Check file exists and matches
+rclone check /local/file remote:bucket/file
+
+# Get file info
+rclone lsl remote:bucket/path/to/file
+```
+
+## Troubleshooting
+
+```bash
+# Test connection
+rclone lsd remote:
+
+# Debug connection issues
+rclone lsd remote: -vv
+
+# Check config
+rclone config show remote
+```

package/plugins/compound-engineering/skills/rclone/scripts/check_setup.sh

@@ -0,0 +1,60 @@
+#!/bin/bash
+# rclone setup checker - verifies installation and configuration
+
+set -e
+
+echo "=== rclone Setup Check ==="
+echo
+
+# Check if rclone is installed
+if command -v rclone >/dev/null 2>&1; then
+    echo "✓ rclone installed"
+    rclone version | head -1
+    echo
+else
+    echo "✗ rclone NOT INSTALLED"
+    echo
+    echo "Install with:"
+    echo "  macOS:  brew install rclone"
+    echo "  Linux:  curl https://rclone.org/install.sh | sudo bash"
+    echo "          or: sudo apt install rclone"
+    exit 1
+fi
+
+# Check for configured remotes
+REMOTES=$(rclone listremotes 2>/dev/null || true)
+
+if [ -z "$REMOTES" ]; then
+    echo "✗ No remotes configured"
+    echo
+    echo "Run 'rclone config' to set up a remote, or use:"
+    echo
+    echo "  # Cloudflare R2"
+    echo "  rclone config create r2 s3 provider=Cloudflare \\"
+    echo "    access_key_id=KEY secret_access_key=SECRET \\"
+    echo "    endpoint=ACCOUNT_ID.r2.cloudflarestorage.com"
+    echo
+    echo "  # AWS S3"
+    echo "  rclone config create aws s3 provider=AWS \\"
+    echo "    access_key_id=KEY secret_access_key=SECRET region=us-east-1"
+    echo
+    exit 1
+else
+    echo "✓ Configured remotes:"
+    echo "$REMOTES" | sed 's/^/  /'
+    echo
+fi
+
+# Test connectivity for each remote
+echo "Testing remote connectivity..."
+for remote in $REMOTES; do
+    remote_name="${remote%:}"
+    if rclone lsd "$remote" >/dev/null 2>&1; then
+        echo "  ✓ $remote_name - connected"
+    else
+        echo "  ✗ $remote_name - connection failed (check credentials)"
+    fi
+done
+
+echo
+echo "=== Setup Complete ==="

package/plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.md

@@ -0,0 +1,89 @@
+---
+name: resolve_pr_parallel
+description: Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
+argument-hint: "[optional: PR number or current PR]"
+disable-model-invocation: true
+allowed-tools: Bash(gh *), Bash(git *), Read
+---
+
+# Resolve PR Comments in Parallel
+
+Resolve all unresolved PR review comments by spawning parallel agents for each thread.
+
+## Context Detection
+
+Claude Code automatically detects git context:
+- Current branch and associated PR
+- All PR comments and review threads
+- Works with any PR by specifying the number
+
+## Workflow
+
+### 1. Analyze
+
+Fetch unresolved review threads using the GraphQL script:
+
+```bash
+bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
+```
+
+This returns only **unresolved, non-outdated** threads with file paths, line numbers, and comment bodies.
+
+If the script fails, fall back to:
+```bash
+gh pr view PR_NUMBER --json reviews,comments
+gh api repos/{owner}/{repo}/pulls/PR_NUMBER/comments
+```
+
+### 2. Plan
+
+Create a TodoWrite list of all unresolved items grouped by type:
+- Code changes requested
+- Questions to answer
+- Style/convention fixes
+- Test additions needed
+
+### 3. Implement (PARALLEL)
+
+Spawn a `pr-comment-resolver` agent for each unresolved item in parallel.
+
+If there are 3 comments, spawn 3 agents:
+
+1. Task pr-comment-resolver(comment1)
+2. Task pr-comment-resolver(comment2)
+3. Task pr-comment-resolver(comment3)
+
+Always run all in parallel subagents/Tasks for each Todo item.
+
+### 4. Commit & Resolve
+
+- Commit changes with a clear message referencing the PR feedback
+- Resolve each thread programmatically:
+
+```bash
+bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/resolve-pr-thread THREAD_ID
+```
+
+- Push to remote
+
+### 5. Verify
+
+Re-fetch comments to confirm all threads are resolved:
+
+```bash
+bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
+```
+
+Should return an empty array `[]`. If threads remain, repeat from step 1.
+
+## Scripts
+
+- [scripts/get-pr-comments](scripts/get-pr-comments) - GraphQL query for unresolved review threads
+- [scripts/resolve-pr-thread](scripts/resolve-pr-thread) - GraphQL mutation to resolve a thread by ID
+
+## Success Criteria
+
+- All unresolved review threads addressed
+- Changes committed and pushed
+- Threads resolved via GraphQL (marked as resolved on GitHub)
+- Empty result from get-pr-comments on verify

package/plugins/compound-engineering/skills/resolve-pr-parallel/scripts/get-pr-comments

@@ -0,0 +1,68 @@
+#!/usr/bin/env bash
+
+set -e
+
+if [ $# -lt 1 ]; then
+    echo "Usage: get-pr-comments PR_NUMBER [OWNER/REPO]"
+    echo "Example: get-pr-comments 123"
+    echo "Example: get-pr-comments 123 EveryInc/cora"
+    exit 1
+fi
+
+PR_NUMBER=$1
+
+if [ -n "$2" ]; then
+    OWNER=$(echo "$2" | cut -d/ -f1)
+    REPO=$(echo "$2" | cut -d/ -f2)
+else
+    OWNER=$(gh repo view --json owner -q .owner.login 2>/dev/null)
+    REPO=$(gh repo view --json name -q .name 2>/dev/null)
+fi
+
+if [ -z "$OWNER" ] || [ -z "$REPO" ]; then
+    echo "Error: Could not detect repository. Pass OWNER/REPO as second argument."
+    exit 1
+fi
+
+gh api graphql -f owner="$OWNER" -f repo="$REPO" -F pr="$PR_NUMBER" -f query='
+query FetchUnresolvedComments($owner: String!, $repo: String!, $pr: Int!) {
+  repository(owner: $owner, name: $repo) {
+    pullRequest(number: $pr) {
+      title
+      url
+      reviewThreads(first: 100) {
+        totalCount
+        edges {
+          node {
+            id
+            isResolved
+            isOutdated
+            isCollapsed
+            path
+            line
+            startLine
+            diffSide
+            comments(first: 100) {
+              totalCount
+              nodes {
+                id
+                author {
+                  login
+                }
+                body
+                createdAt
+                updatedAt
+                url
+                outdated
+              }
+            }
+          }
+        }
+        pageInfo {
+          hasNextPage
+          endCursor
+        }
+      }
+    }
+  }
+}' | jq '.data.repository.pullRequest.reviewThreads.edges | map(select(.node.isResolved == false and .node.isOutdated == false))'

package/plugins/compound-engineering/skills/resolve-pr-parallel/scripts/resolve-pr-thread

@@ -0,0 +1,23 @@
+#!/usr/bin/env bash
+
+set -e
+
+if [ $# -eq 0 ]; then
+    echo "Usage: resolve-pr-thread THREAD_ID"
+    echo "Example: resolve-pr-thread PRRT_kwDOABC123"
+    exit 1
+fi
+
+THREAD_ID=$1
+
+gh api graphql -f threadId="$THREAD_ID" -f query='
+mutation ResolveReviewThread($threadId: ID!) {
+  resolveReviewThread(input: {threadId: $threadId}) {
+    thread {
+      id
+      isResolved
+      path
+      line
+    }
+  }
+}'

package/plugins/compound-engineering/skills/skill-creator/SKILL.md

@@ -0,0 +1,210 @@
+---
+name: skill-creator
+description: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
+license: Complete terms in LICENSE.txt
+disable-model-invocation: true
+---
+
+# Skill Creator
+
+This skill provides guidance for creating effective skills.
+
+## About Skills
+
+Skills are modular, self-contained packages that extend Claude's capabilities by providing
+specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
+domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
+equipped with procedural knowledge that no model can fully possess.
+
+### What Skills Provide
+
+1. Specialized workflows - Multi-step procedures for specific domains
+2. Tool integrations - Instructions for working with specific file formats or APIs
+3. Domain expertise - Company-specific knowledge, schemas, business logic
+4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
+
+### Anatomy of a Skill
+
+Every skill consists of a required SKILL.md file and optional bundled resources:
+
+```
+skill-name/
+├── SKILL.md (required)
+│   ├── YAML frontmatter metadata (required)
+│   │   ├── name: (required)
+│   │   └── description: (required)
+│   └── Markdown instructions (required)
+└── Bundled Resources (optional)
+    ├── scripts/          - Executable code (Python/Bash/etc.)
+    ├── references/       - Documentation intended to be loaded into context as needed
+    └── assets/           - Files used in output (templates, icons, fonts, etc.)
+```
+
+#### SKILL.md (required)
+
+**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when...").
+
+#### Bundled Resources (optional)
+
+##### Scripts (`scripts/`)
+
+Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
+
+- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
+- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
+- **Benefits**: Token efficient, deterministic, may be executed without loading into context
+- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
+
+##### References (`references/`)
+
+Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
+
+- **When to include**: For documentation that Claude should reference while working
+- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
+- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
+- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
+- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
+- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
+
+##### Assets (`assets/`)
+
+Files not intended to be loaded into context, but rather used within the output Claude produces.
+
+- **When to include**: When the skill needs files that will be used in the final output
+- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
+- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
+- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
+
+### Progressive Disclosure Design Principle
+
+Skills use a three-level loading system to manage context efficiently:
+
+1. **Metadata (name + description)** - Always in context (~100 words)
+2. **SKILL.md body** - When skill triggers (<5k words)
+3. **Bundled resources** - As needed by Claude (Unlimited*)
+
+*Unlimited because scripts can be executed without reading into context window.
+
+## Skill Creation Process
+
+To create a skill, follow the "Skill Creation Process" in order, skipping steps only if there is a clear reason why they are not applicable.
+
+### Step 1: Understanding the Skill with Concrete Examples
+
+Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
+
+To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
+
+For example, when building an image-editor skill, relevant questions include:
+
+- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
+- "Can you give some examples of how this skill would be used?"
+- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
+- "What would a user say that should trigger this skill?"
+
+To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
+
+Conclude this step when there is a clear sense of the functionality the skill should support.
+
+### Step 2: Planning the Reusable Skill Contents
+
+To turn concrete examples into an effective skill, analyze each example by:
+
+1. Considering how to execute on the example from scratch
+2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
+
+Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
+
+1. Rotating a PDF requires re-writing the same code each time
+2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
+
+Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
+
+1. Writing a frontend webapp requires the same boilerplate HTML/React each time
+2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
+
+Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
+
+1. Querying BigQuery requires re-discovering the table schemas and relationships each time
+2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
+
+To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
+
+### Step 3: Initializing the Skill
+
+At this point, it is time to actually create the skill.
+
+Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
+
+When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
+
+Usage:
+
+```bash
+scripts/init_skill.py <skill-name> --path <output-directory>
+```
+
+The script:
+
+- Creates the skill directory at the specified path
+- Generates a SKILL.md template with proper frontmatter and TODO placeholders
+- Creates example resource directories: `scripts/`, `references/`, and `assets/`
+- Adds example files in each directory that can be customized or deleted
+
+After initialization, customize or remove the generated SKILL.md and example files as needed.
+
+### Step 4: Edit the Skill
+
+When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
+
+#### Start with Reusable Skill Contents
+
+To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
+
+Also, delete any example files and directories not needed for the skill. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
+
+#### Update SKILL.md
+
+**Writing Style:** Write the entire skill using **imperative/infinitive form** (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X"). This maintains consistency and clarity for AI consumption.
+
+To complete SKILL.md, answer the following questions:
+
+1. What is the purpose of the skill, in a few sentences?
+2. When should the skill be used?
+3. In practice, how should Claude use the skill? All reusable skill contents developed above should be referenced so that Claude knows how to use them.
+
+### Step 5: Packaging a Skill
+
+Once the skill is ready, it should be packaged into a distributable zip file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder>
+```
+
+Optional output directory specification:
+
+```bash
+scripts/package_skill.py <path/to/skill-folder> ./dist
+```
+
+The packaging script will:
+
+1. **Validate** the skill automatically, checking:
+   - YAML frontmatter format and required fields
+   - Skill naming conventions and directory structure
+   - Description completeness and quality
+   - File organization and resource references
+
+2. **Package** the skill if validation passes, creating a zip file named after the skill (e.g., `my-skill.zip`) that includes all files and maintains the proper directory structure for distribution.
+
+If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
+
+### Step 6: Iterate
+
+After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
+
+**Iteration workflow:**
+1. Use the skill on real tasks
+2. Notice struggles or inefficiencies
+3. Identify how SKILL.md or bundled resources should be updated
+4. Implement changes and test again