707-command-center-mcp 1.0.0 → 1.0.2

package/dist/server.js

@@ -21831,33 +21831,30 @@ function createMcpServer(api) {
 }
 
 // ../src/mcp/server.ts
-import { existsSync, mkdirSync, readdirSync, readFileSync, writeFileSync, statSync } from "fs";
+import { existsSync, cpSync } from "fs";
 import { join, dirname } from "path";
 import { homedir } from "os";
 import { fileURLToPath } from "url";
 function syncSkills() {
   const __filename = fileURLToPath(import.meta.url);
   const __dirname = dirname(__filename);
-  const bundledSkillsDir = join(__dirname, "..", "skills");
-  if (!existsSync(bundledSkillsDir)) {
-    return;
-  }
-  const targetDir = join(homedir(), ".claude", "skills");
-  mkdirSync(targetDir, { recursive: true });
-  function copyDir(src, dest) {
-    mkdirSync(dest, { recursive: true });
-    for (const entry of readdirSync(src)) {
-      const srcPath = join(src, entry);
-      const destPath = join(dest, entry);
-      if (statSync(srcPath).isDirectory()) {
-        copyDir(srcPath, destPath);
-      } else {
-        writeFileSync(destPath, readFileSync(srcPath));
-      }
+  const bundledDir = join(__dirname, "..", "skills");
+  if (!existsSync(bundledDir)) return;
+  const claudeDir = join(homedir(), ".claude");
+  try {
+    const bundledSkills = join(bundledDir, "skills");
+    if (existsSync(bundledSkills)) {
+      cpSync(bundledSkills, join(claudeDir, "skills"), { recursive: true, force: true });
+      console.error(`Skills synced to ${join(claudeDir, "skills")}`);
+    }
+    const bundledCommands = join(bundledDir, "commands");
+    if (existsSync(bundledCommands)) {
+      cpSync(bundledCommands, join(claudeDir, "commands"), { recursive: true, force: true });
+      console.error(`Commands synced to ${join(claudeDir, "commands")}`);
     }
+  } catch (err) {
+    console.error(`Failed to sync skills: ${err.message}`);
   }
-  copyDir(bundledSkillsDir, targetDir);
-  console.error(`Skills synced to ${targetDir}`);
 }
 async function main() {
   const apiKey = process.env.CC_API_KEY;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "707-command-center-mcp",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "MCP server for 707 Command Center — deal management, valuation, and mineral data tools",
   "type": "module",
   "bin": {

package/skills/.claude-plugin/plugin.json

@@ -0,0 +1,8 @@
+{
+  "name": "show-goat-skills",
+  "description": "Deal valuation skills and commands for Show Goat Capital",
+  "version": "1.0.0",
+  "author": {
+    "name": "Show Goat Capital"
+  }
+}

package/skills/.github/workflows/trigger-mcp-rebuild.yml

@@ -0,0 +1,16 @@
+name: Trigger MCP Package Rebuild
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  dispatch:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Trigger MCP rebuild in command center
+        uses: peter-evans/repository-dispatch@v3
+        with:
+          token: ${{ secrets.DISPATCH_TOKEN }}
+          repository: landman-coder/707-command-center
+          event-type: skills-updated

package/skills/.gitignore

@@ -0,0 +1,29 @@
+# Only track commands and skills — everything else is local state
+*
+!.gitignore
+!.claude-plugin/
+!.claude-plugin/**
+!commands/
+!commands/**
+!skills/
+!skills/**
+!.github/
+!.github/**
+
+# Claude Code internal state (never track)
+cache/
+debug/
+file-history/
+paste-cache/
+plans/
+plugins/
+projects/
+shell-snapshots/
+statsig/
+tasks/
+telemetry/
+todos/
+history.jsonl
+settings.json
+settings.local.json
+stats-cache.json

package/skills/commands/assign-deals.md

@@ -0,0 +1,187 @@
+# Assign Deals to Caller
+
+Bulk assign HubSpot deals to a caller by county, date, and amount filters.
+
+## Usage
+```
+/assign-deals
+```
+
+No arguments — the command asks questions interactively.
+
+## What This Does
+1. Asks who to assign to, which counties, how many, and date range
+2. Searches HubSpot for matching deals owned by Reid
+3. Filters out trusts/estates client-side
+4. Shows summary + sample deals for confirmation
+5. Batch updates deal ownership
+
+## Instructions for Claude
+
+When the user runs this command:
+
+### 1. Ask Questions (Single Message)
+
+Ask all four questions at once using `AskUserQuestion`:
+
+- **Caller**: Who should these deals be assigned to?
+- **Counties**: Which TX counties? (comma-separated, e.g., "Madison, Leon, Grimes")
+- **Count**: How many deals to assign? (default: all matching)
+- **Date range**: How far back? (default: last 90 days)
+
+### 2. Resolve Caller to Owner ID
+
+Use `mcp__claude_ai_HubSpot__search_owners` to find the caller's HubSpot owner ID.
+
+**Known callers (quick reference — verify against HubSpot):**
+
+| Name | Likely ID | Role |
+|------|-----------|------|
+| Reid Valentine | 193538161 | Owner (source for deals) |
+
+If the caller name doesn't match any owner, show the full owner list and ask the user to pick.
+
+### 3. Search HubSpot for Deals
+
+Use `mcp__claude_ai_HubSpot__search_crm_objects` with these filters:
+
+```
+objectType: deals
+searchRequest:
+  filterGroups:
+    - filters:
+        - propertyName: hubspot_owner_id
+          operator: EQ
+          value: "193538161"              # Reid = source owner
+        - propertyName: county
+          operator: IN
+          values: [{user_counties}]       # From question
+        - propertyName: amount
+          operator: GT
+          value: "50000"
+        - propertyName: amount
+          operator: LT
+          value: "5000000"
+        - propertyName: createdate
+          operator: GTE
+          value: "{epoch_ms}"             # Based on date range
+  sorts:
+    - propertyName: createdate
+      direction: DESCENDING
+  properties:
+    - dealname
+    - amount
+    - county
+    - createdate
+    - hubspot_owner_id
+    - dealstage
+  limit: 200
+```
+
+**Pagination**: If `total` > 200, paginate using `after` cursor until all results collected.
+
+### 4. Filter Names Client-Side
+
+Exclude deals where `dealname` matches ANY of these patterns (case-insensitive):
+
+- `Trust`
+- `Living`
+- `Life Estate`
+- `Revocable`
+- `Irrev` (catches Irrevocable)
+- `Estate`
+
+Keep a count of excluded deals for reporting.
+
+### 5. Apply Count Limit
+
+If the user requested a specific count and eligible deals exceed it, take only that many (already sorted by createdate DESC = freshest first).
+
+If eligible deals are fewer than requested, stop and report:
+```
+Found only {eligible} eligible deals (requested {count}). Proceed with all {eligible}?
+```
+
+### 6. Confirm Before Executing
+
+Present a summary table:
+
+```
+## Deal Assignment Summary
+
+**Caller:** {caller_name}
+**Counties:** {county_list}
+**Date range:** {start_date} to today
+
+| Metric | Count |
+|--------|-------|
+| Total matches | {total_found} |
+| Excluded (trusts/estates) | {excluded_count} |
+| Eligible | {eligible_count} |
+| **Assigning** | **{assigning_count}** |
+
+### Sample Deals (first 5)
+| Deal Name | County | Amount | Created |
+|-----------|--------|--------|---------|
+| {name} | {county} | ${amount} | {date} |
+| ... | ... | ... | ... |
+
+Proceed with assigning {assigning_count} deals to {caller_name}?
+```
+
+**Wait for explicit user confirmation before proceeding.**
+
+### 7. Batch Update Ownership
+
+Use `mcp__hubspot__hubspot-batch-update-objects` to update deals in batches of 100:
+
+```
+objectType: deals
+inputs: [
+  { id: "{deal_id}", properties: { hubspot_owner_id: "{caller_owner_id}" } },
+  ...
+]
+```
+
+Report progress for large batches:
+```
+Batch 1/3: Updated 100 deals...
+Batch 2/3: Updated 100 deals...
+Batch 3/3: Updated 47 deals...
+```
+
+### 8. Final Summary
+
+```
+## Assignment Complete
+
+Assigned {count} deals to {caller_name}.
+
+| Detail | Value |
+|--------|-------|
+| Caller | {caller_name} |
+| Counties | {county_list} |
+| Deals assigned | {count} |
+| Trusts/estates skipped | {excluded_count} |
+```
+
+## Edge Cases
+
+| Situation | Action |
+|-----------|--------|
+| 0 matches found | Report "No deals match these filters." Suggest adjusting county list or date range. |
+| Fewer than requested | Stop and ask user if they want to proceed with all available. |
+| Caller not found in HubSpot | Show owner list from `search_owners` and ask user to pick. |
+| Large batch (>1000 deals) | Warn: "This will update {count} deals. Are you sure?" before proceeding. |
+| API rate limit / error | Stop, report the error, and show how many were successfully updated. |
+
+## Fixed Parameters (Not Asked)
+
+These don't change between runs:
+
+| Parameter | Value | Reason |
+|-----------|-------|--------|
+| Source owner | Reid Valentine (193538161) | All unassigned deals start with Reid |
+| Min amount | $50,000 | Below this = not worth calling |
+| Max amount | $5,000,000 | Above this = Reid handles directly |
+| Name exclusions | Trust, Living, Life Estate, Revocable, Irrev, Estate | Trusts/estates require specialized handling |

package/skills/commands/deal-intake.md

@@ -0,0 +1,67 @@
+# Deal Intake
+
+Process a closed deal into the inventory database.
+
+## Usage
+```
+/deal-intake [deal_name_or_path]
+```
+
+## Arguments
+- `deal_name_or_path` — Deal name (searches HubSpot/Command Center) or path to the deal folder
+
+## Instructions for Claude
+
+When the user runs this command:
+
+### 1. Load the deal-intake skill
+Load the `deal-intake` skill for field specs and workflow details.
+
+### 2. Locate the deal folder
+If a name was provided, use `/deal-context` to find it. If a path was provided, use that directly.
+
+Expected location: `1 - Qualified/{Deal Name}/`
+
+### 3. Inventory the folder contents
+List what's in the deal folder. Look for:
+- `_Claude_Analysis.md` — read if it exists (has prior analysis)
+- `*.xlsx` or `*.csv` — conveyance exhibit / property schedule
+- `Stubs/` folder — revenue stubs (NRI, operators, lease IDs)
+- `Title/` folder — title opinions (legal descriptions, depth clauses)
+- Division orders, bank statements, etc.
+
+Not all folders will have the same documents. Work with what's available.
+
+### 4. Extract what you can
+Use Python openpyxl for Excel files. Read PDFs with the Read tool. Extract:
+- Legal descriptions, counties, interest amounts
+- Operator names, lease IDs, NRI from stubs
+- Well names and API numbers
+
+### 5. Ask the user to fill gaps
+After extracting available data, tell the user:
+- What fields you were able to fill
+- What fields are missing and where they typically come from
+- Ask the user to provide missing required fields (entity_short_name, NRI, etc.)
+
+**Track what was missing and where it came from** — record this in a note at the end so we can improve the skill for future deals.
+
+### 5b. Include Ptolemy geometry (if available)
+If `{deal}_tracts.geojson` exists in the deal folder, read it and include it as the `tract_geojson` field in the payload. This populates `tract_geometries` with geometry immediately during intake instead of requiring a separate backfill step.
+
+### 6. Build and POST payload
+Once all required fields are confirmed, POST to the inventory API using the MCP `inventory` → `intake_deal` action.
+Include `tract_geojson` in the payload if a Ptolemy GeoJSON file was found in step 5b.
+
+### 7. Report results
+- Show counts: legals, leases, wells, recordings created
+- Show any master lease diffs and ask user to confirm/reject
+
+### 8. Record learnings
+After completing the intake, append to `Dev/notes/deal-intake-learnings.md`:
+- Deal name and date
+- What documents were available
+- What data was missing and how it was obtained
+- Any new patterns discovered (file naming, folder structure, data locations)
+
+This log helps us make the skill more robust over time.

package/skills/commands/nm-pooling.md

@@ -0,0 +1,158 @@
+# NM Compulsory Pooling Contact Extractor
+
+Extract owner contacts from NM OCD compulsory pooling case files for mail merge.
+
+## Usage
+```
+/nm-pooling [input_file] [--workers N]
+```
+
+## Arguments
+- `input_file` - Path to Excel file with case URLs (optional - will prompt if not provided)
+- `--workers N` - Number of parallel workers (default: 4)
+
+## What This Does
+1. Reads the input Excel file containing NM OCD case URLs
+2. Downloads the largest PDF from each case (contains mailing lists)
+3. OCRs mailing list pages and extracts contacts
+4. Handles multiple formats (PS Form 3877, Postal Delivery Reports, etc.)
+5. Deduplicates contacts and flags oil companies/government entities
+6. Outputs formatted Excel ready for CRM upload and mail merge
+
+## Output Location
+```
+C:\Users\ReidValentine\OneDrive - 707 Advisors, LLC\Show Goat Capital, LP - Show Goat Capital, LP\01 Land\99 Drilling Permit & Compulsory Pooling Query\NM - Mail Merge Lists\2026\{YYYYMMDD} - NMCompPooling - All\
+```
+
+## Instructions for Claude
+
+When the user runs this command:
+
+1. If no input file specified, ask for the path to the Excel file containing the cases.
+
+2. Run the extraction script:
+```bash
+cd C:\Users\ReidValentine\Dev\automation\nm-pooling
+python nm_pooling_extractor.py "<input_file>" --workers 4
+```
+
+3. The script will:
+   - Process cases in parallel (4 workers by default)
+   - Show progress as it downloads and processes each case
+   - Create output in the 2026 folder with today's date
+
+4. After completion, report:
+   - Total cases processed
+   - Total unique contacts extracted
+   - Number flagged for review (oil companies/government)
+   - Any cases with errors that need manual review
+   - Path to output file
+
+5. If there are errors, offer to help troubleshoot specific cases by examining their PDFs.
+
+## Known Format Variations
+
+| Operator/Law Firm | Format | Pages | Status |
+|-------------------|--------|-------|--------|
+| Modrall Sperling | PS Form 3877 | Last 50-100 pages | ✅ Supported |
+| MRC/Matador | Postal Delivery Report | Pages 190-220 | ✅ Supported |
+| Hardy McLean LLC | USPS Electronic Return Receipt | Exhibit C-3 (varies) | ⚠️ Needs parser |
+| Spencer Fane LLP | PS Form 3811 | Pages 60-120 | ⚠️ Needs parser |
+| Spencer Fane LLP | Tabular Certified Mail List | Last 70 pages | ⚠️ Needs parser |
+
+### Format Details
+
+#### 1. PS Form 3877 (Modrall Sperling)
+- **Detection**: Look for "PS Form 3877" header, rotated 90 degrees
+- **Location**: Last 50-100 pages of PDF
+- **Pattern**: Name and address in columnar format
+- **OCR Required**: Yes (Type3 embedded fonts)
+
+#### 2. Postal Delivery Report (MRC/Matador)
+- **Detection**: "Postal Delivery Report" header with table columns
+- **Location**: Pages 180-220
+- **Pattern**: Table with Name, Address, City, State, Zip columns
+- **OCR Required**: Yes
+
+#### 3. USPS Electronic Return Receipt (Hardy McLean LLC)
+- **Operators**: Permian Resources Operating, LLC
+- **Detection**: "UNITED STATES POSTAL SERVICE" + "Simple Certified" or "proof of delivery"
+- **Location**: Exhibit C-3 (pages 40-60 typically)
+- **Pattern**: Footer block on each page:
+  ```
+  [Company Name]
+  [Street Address]
+  [City, State ZIP]
+  Reference #: PR [Well Name]
+  ```
+- **OCR Required**: No (text extractable)
+- **Notes**: One recipient per page, ~10-20 recipients per case
+
+#### 4. PS Form 3811 (Spencer Fane LLP)
+- **Operators**: Longfellow Energy, various
+- **Detection**: "Article Addressed to:" header
+- **Location**: Pages 60-120 (Exhibit C-3)
+- **Pattern**:
+  ```
+  1. Article Addressed to:
+
+  [Company Name]
+  [Street Address]
+  [City, State ZIP]
+  ```
+- **OCR Required**: Yes
+- **Notes**: Individual tracking pages per recipient, ~40 pages = ~40 recipients
+
+#### 5. Spencer Fane Tabular Format
+- **Operators**: Tumbler Operating Partners, various
+- **Detection**: Column headers "Entity / Individual | Date Notice Letter Mailed | Certified Mail Number"
+- **Location**: Last 70 pages (Exhibit E-2)
+- **Pattern**:
+  ```
+  [Entity Name]          June 20, 2025    9314 7699 0430...    Delivered
+  [Street Address]
+  [City, State ZIP]
+  ```
+- **Sections**: WORKING INTERESTS, ROYALTY INTEREST OWNERS, ORRI, FEDERAL/STATE AGENCIES
+- **OCR Required**: Yes
+- **Notes**: ~40 contacts per case, handles "Texas" and "TX" state formats
+
+## Troubleshooting
+
+If a case fails with "No contacts found":
+
+1. **Identify the law firm** from the PDF cover page or application
+2. **Check the format table above** to see if it's a known format
+3. **Find the mailing list pages**:
+   - Look for Exhibit C (Proof of Service) or Exhibit E (Certified Mail)
+   - Check last 50-100 pages first
+   - Look for USPS tracking numbers (9314..., 9590...)
+4. **If it's a new format**, document:
+   - Law firm name
+   - Page numbers where contacts appear
+   - Text pattern/structure
+   - Whether OCR is needed
+5. **Add to this table** for future reference
+
+### Known Edge Cases
+
+**Upside-down pages (Case 25803 pattern)**: Some Modrall Sperling PDFs have pages rotated 180°. If a case shows 0 contacts but you know mailing lists exist:
+1. Download the PDF manually
+2. Check if pages are upside-down
+3. Rotate in PDF editor or use: `img.rotate(180, expand=True)` before OCR
+
+### Manual Extraction Fallback
+
+If automated extraction fails, use Claude to manually OCR specific pages:
+```python
+import fitz
+import pytesseract
+from PIL import Image
+
+pdf = fitz.open("path/to/pdf.pdf")
+page = pdf[PAGE_NUMBER - 1]  # 0-indexed
+pix = page.get_pixmap(dpi=300)
+img = Image.frombytes("RGB", [pix.width, pix.height], pix.samples)
+text = pytesseract.image_to_string(img)
+print(text)
+```

package/skills/commands/review.md

@@ -0,0 +1,131 @@
+# Session Review
+
+Review all work done during this session and surface messy/weak spots.
+
+## Usage
+```
+/review
+```
+
+## Arguments
+None. Reviews everything touched in the current session.
+
+## What This Does
+1. Identifies all files modified during the session (git-tracked and untracked)
+2. Collects diffs and reads modified files in full
+3. Launches 3 parallel review agents (Shape, Mechanics, Cleanup)
+4. Aggregates findings, deduplicates, applies confidence scoring
+5. Outputs a structured review report
+6. Interactive issue resolution with the user
+
+## Instructions for Claude
+
+When the user runs this command:
+
+### 1. Gather Session Context
+
+First, identify which repos under `C:\Users\ReidValentine\Dev` have changes:
+
+```bash
+# Check each known repo for changes
+for repo in 707-command-center seller-portal automation config; do
+  echo "=== $repo ==="
+  git -C /c/Users/ReidValentine/Dev/$repo status --short 2>/dev/null
+  git -C /c/Users/ReidValentine/Dev/$repo diff --stat 2>/dev/null
+done
+```
+
+Also check for changes in non-git locations:
+- `.claude/commands/` — new or modified commands
+- `.claude/skills/` — new or modified skills
+- `Dev/notes/` — modified notes
+
+Use conversation history to identify files touched during this session that may already be committed.
+
+### 2. Get Recent Commit Context
+
+For each repo with changes or recent commits:
+
+```bash
+git -C /c/Users/ReidValentine/Dev/$repo log --oneline -10
+```
+
+This shows what was already committed during the session.
+
+### 3. Collect Full Diffs
+
+For uncommitted changes:
+```bash
+git -C /c/Users/ReidValentine/Dev/$repo diff
+git -C /c/Users/ReidValentine/Dev/$repo diff --cached
+```
+
+### 4. Launch 3 Parallel Review Agents
+
+Launch all three agents in a **single message** using the Agent tool. Pass each agent the full diff and the list of changed files.
+
+#### Agent 1: Shape Review (Architecture + Naming + Consistency)
+Prompt the agent with:
+- The full diff
+- Instructions to read each changed file in full (diffs alone lack context for naming/architecture judgment)
+- Check: Does new code follow established codebase patterns? Are there abstraction leaks, wrong-layer logic, or CLAUDE.md convention violations?
+- Check: Are names clear, consistent, and non-misleading? Flag generic names, inconsistent casing, abbreviation soup.
+- Check: Does new code match surrounding style? Mixed conventions? New patterns where existing ones already work?
+- Apply confidence scoring (only report findings > 0.7)
+- Reference: `.claude/skills/session-review/references/review-checklist.md` for Architecture, Naming anti-patterns
+
+#### Agent 2: Mechanics Review (Reuse + Efficiency)
+Prompt the agent with:
+- The full diff
+- Instructions to **Grep the codebase** for existing utilities and helpers that match newly written code. Check utility directories, shared modules, adjacent files.
+- Flag: new functions that duplicate existing functionality (name the existing function), inline logic reimplementing an existing utility, copy-paste with slight variation, stringly-typed code where constants/enums exist
+- Flag: N+1 queries, sequential-but-independent awaits, redundant computation, duplicate I/O, TOCTOU existence checks, startup bloat, unbounded accumulation, overly broad reads
+- Apply confidence scoring (only report findings > 0.7)
+- Reference: `.claude/skills/session-review/references/review-checklist.md` for Reuse, Efficiency anti-patterns
+
+#### Agent 3: Cleanup Review (Simplicity + Completeness + Cruft)
+Prompt the agent with:
+- The full diff
+- Instructions to read each changed file in full
+- Check: YAGNI violations, premature abstractions, unnecessary indirection, config where a constant would do
+- Check: Unhandled cases at system boundaries, missing validation on external input, silent error swallowing, partial implementations without TODO markers
+- Check: Dead comments, contextless TODOs, debug artifacts, unused imports/variables, hardcoded values that should be constants
+- Apply confidence scoring (only report findings > 0.7)
+- Reference: `.claude/skills/session-review/references/review-checklist.md` for Over-Engineering, Completeness, Cruft anti-patterns
+
+### 5. Aggregate & Report
+
+After all 3 agents return:
+1. Deduplicate findings (agents may flag the same issue from different angles)
+2. Assign category tags: `ARCHITECTURE`, `REUSE`, `NAMING`, `EFFICIENCY`, `SIMPLICITY`, `COMPLETENESS`, `CONSISTENCY`, `CRUFT`
+3. Output using the structured format in SKILL.md, grouped by file, ordered by severity
+
+### 6. Interactive Issue Resolution
+
+After presenting the review report, ask the user: **"Ready to go through the issues, or any pushback/context first?"**
+
+Wait for the user to respond. They may:
+- Push back on findings ("Issue #2 isn't actually a problem because...")
+- Add context that changes the assessment
+- Remove or re-prioritize issues
+- Say they're ready to proceed
+
+Once the user confirms they're ready, use `AskUserQuestion` to let them act on each finding. Group related issues where possible (max 4 questions per call).
+
+For each issue, present options like:
+- **Fix now** — Claude makes the change immediately
+- **Verify first** — Claude checks assumptions before acting (e.g., confirm an endpoint exists)
+- **Skip** — Not worth addressing
+
+If there are more than 4 issues, batch them across multiple AskUserQuestion calls. Process the first batch, apply fixes, then ask about remaining issues.
+
+After all issues are resolved or skipped, output a one-line summary: "Review complete — X fixed, Y skipped."
+
+## Auto-Suggest Behavior
+
+Claude should proactively suggest running `/review` in these situations:
+- Before the user makes a commit (if substantial work was done)
+- At the natural end of a session when work is wrapping up
+- After completing a multi-file change
+
+This is a **suggestion only** — do not run automatically without the user invoking `/review`.