@simpleapps-com/augur-skills 0.0.20 → 0.0.21

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simpleapps-com/augur-skills",
-  "version": "0.0.20",
+  "version": "0.0.21",
   "description": "Install curated Claude Code skills",
   "license": "MIT",
   "type": "module",

package/skills/simpleapps/{workflow/basecamp.md → basecamp/SKILL.md}

@@ -1,6 +1,11 @@
-# Basecamp 2 Reference
+---
+name: basecamp
+description: Basecamp 2 integration via MCP. Covers MCP tool reference, URL parsing, authentication, Chrome fallback, attachments, and site-info documents. Use when reading or writing Basecamp data.
+---
 
-IMPORTANT: YOU MUST NOT create, edit, or delete anything in Basecamp without user permission.
+# Basecamp 2
+
+IMPORTANT: MUST NOT create, edit, or delete anything in Basecamp without user permission.
 
 **Content format**: All write tools SHOULD use plain text with line breaks, NOT HTML. Basecamp returns HTML in responses but prefers plain text for creation.
 
@@ -14,7 +19,7 @@ uv run basecamp-auth
 
 This opens the browser for OAuth, user clicks "Allow", credentials are saved automatically.
 
-## MCP Tools (Preferred)
+## MCP Tools
 
 The `basecamp` MCP server is bundled with this plugin and starts automatically. API reference: https://github.com/basecamp/bcx-api
 
@@ -143,7 +148,11 @@ Note: Messages may not be available on all Basecamp plans.
 
 **Note**: The BCX API does not have a search endpoint. To find content, use `list_topics(project_id)` to browse, or `list_messages(project_id)` for messages. For cross-project browsing, use `list_topics()` (no project_id) to get recent topics across all projects.
 
-**Extracting IDs from Basecamp URLs**: A URL like `https://basecamp.com/2805226/projects/18932786/todos/514631271` gives you project_id=`18932786` and todo_id=`514631271`.
+## URL Parsing
+
+A URL like `https://basecamp.com/2805226/projects/18932786/todos/514631271` gives you project_id=`18932786` and todo_id=`514631271`.
+
+**Base URL**: `https://basecamp.com/2805226`
 
 ## Downloading Attachments
 
@@ -156,6 +165,10 @@ Attachments can be on todos, comments, messages, or uploads. To retrieve them:
 
 To browse all attachments in a project, use `list_attachments(project_id)`.
 
+## Site Info Documents
+
+Each Basecamp project SHOULD have a **site-info** text document in its Documents section. It contains site-specific details like siteId and domain name needed for GitHub issues and development work. Use `list_documents` + `get_document` to find it. If no site-info document exists, ask the user to create one.
+
 ## Chrome Fallback
 
 If the MCP server is unavailable (credentials expired, server not running), use Chrome:
@@ -165,8 +178,6 @@ If the MCP server is unavailable (credentials expired, server not running), use
 3. Navigate to the Basecamp page
 4. Use `get_page_text` to extract content
 
-**Base URL**: `https://basecamp.com/2805226`
-
 **Top nav**: Projects | Calendar | Everything | Progress | Everyone | **Me**
 
 | Page | Path |
@@ -182,14 +193,6 @@ If the MCP server is unavailable (credentials expired, server not running), use
 
 **JSON API via Chrome**: Navigate to `/api/v1/projects/<project_id>/todos/<todo_id>.json` then use `get_page_text`. WebFetch will NOT work — Chrome carries session cookies.
 
-## Fyxer Meeting Transcripts
-
-To post Fyxer meeting recordings as Basecamp Discussions, see the `simpleapps:fyxer` skill. It handles extraction, local caching, duplicate detection, and posting via `create_message`.
-
-## Site Info Documents
-
-Each Basecamp project SHOULD have a **site-info** text document in its Documents section. It contains site-specific details like siteId and domain name needed for GitHub issues and development work. Use `list_documents` + `get_document` to find it. If no site-info document exists, ask the user to create one.
-
 ## Tips
 
 - Cache the user's `person_id` on first visit for the session

package/skills/simpleapps/fyxer/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: fyxer
-description: Fyxer AI meeting recording integration. Covers extraction, local caching, and posting to downstream services. Use when processing Fyxer recordings or meeting transcripts.
+description: Fyxer AI meeting recording integration. Covers extraction, local caching, posting to Basecamp, and Fyxer Index management. Use when processing Fyxer recordings or meeting transcripts.
 ---
 
 # Fyxer
 
-Fyxer AI records and summarizes meetings. This skill covers extracting data from Fyxer and routing it to other services.
+Fyxer AI records and summarizes meetings. This skill covers extracting data from Fyxer, posting to Basecamp, and managing the Fyxer Index.
 
 ## Fyxer URLs
 
@@ -28,7 +28,7 @@ All extracted data is cached at `~/.simpleapps/fyxer/<meeting-uuid>/`:
 ```
 summary.txt     - raw Fyxer summary (from Summary tab)
 transcript.txt  - raw Fyxer transcript (from Transcript tab)
-message.txt     - assembled output (generated by downstream processes, e.g. basecamp.md)
+message.txt     - assembled output (generated by posting process)
 ```
 
 Cache is populated via Chrome extraction (see below) and reused across processes.
@@ -84,11 +84,125 @@ Then write and verify: `pbpaste > target.txt && wc -c target.txt`
 
 MUST clean up `~/Downloads/` after copying downloaded files to the cache directory. Fyxer names downloads like `transcript-SA_USCCO.txt`. Repeated downloads append `(1)`, `(2)`, etc.
 
-## Processes
+## Posting to Basecamp
 
-- See `basecamp.md` for posting meeting transcripts as Basecamp Discussions
-- See `basecamp-index.md` for the Fyxer Index document (duplicate detection, reconciliation)
+Post Fyxer meeting recordings as searchable Discussions in Basecamp projects.
+
+**Inputs**: Fyxer recording URL + Basecamp project ID.
+
+### 1. Check for duplicate
+
+Extract the meeting UUID from the Fyxer URL. Find the **Fyxer Index** document in the project: `list_documents(project_id)` → scan for title `Fyxer Index`. If found, `get_document(project_id, document_id)` and search content for the meeting UUID. If found, the meeting has already been posted — inform the user and stop.
+
+If no Fyxer Index document exists, there are no tracked meetings. Proceed with posting.
+
+### 2. Check local cache
+
+If `~/.simpleapps/fyxer/<meeting-uuid>/summary.txt` and `transcript.txt` both exist, skip to step 3. Otherwise, follow the Chrome extraction steps above.
+
+### 3. Build message.txt
+
+Parse `summary.txt` for frontmatter fields, extract participants, and combine with the full transcript:
+
+```
+---
+meeting: SA/ClientName
+date: YYYY-MM-DD
+time: HH:MM-HH:MM
+participants: Person A, Person B, Person C
+topics: Topic One, Topic Two, Topic Three
+fyxer-id: <meeting-uuid>
+---
+
+[contents of transcript.txt]
+```
+
+| Field | Source |
+|-------|--------|
+| meeting | Meeting title from the page header |
+| date | Recording date |
+| time | Recording time range |
+| participants | Participant dropdown (click to reveal names) |
+| topics | Section headings from the Summary |
+| fyxer-id | Meeting UUID from the URL (before the colon) |
+
+Save as `~/.simpleapps/fyxer/<meeting-uuid>/message.txt`.
+
+### 4. Post to Basecamp
+
+Use `create_message(project_id, subject, content)`:
+
+- **Subject**: `Fyxer: YYYY-MM-DD`
+- **Content**: contents of `message.txt`
+
+Capture the **message_id** from the response.
+
+### 5. Update Fyxer Index
+
+After a successful post, update the Fyxer Index document:
+
+1. If no Fyxer Index document exists, create one: `create_document(project_id, "Fyxer Index", "")`
+2. Read current content: `get_document(project_id, document_id)`
+3. Prepend a new line (newest first): `<meeting-uuid> | <date> | <message-id> | <subject>`
+4. Update: `update_document(project_id, document_id, title="Fyxer Index", content=updated_content)`
+
+If the index update fails after a successful post, warn the user. The message is posted but the index is stale. Run reconciliation later.
+
+### Format rules
+
+- **Plain text only** — Basecamp prefers plain text over HTML
+- **YAML frontmatter** — machine-parseable so other Claude Code instances can search and parse meeting context
+- **Transcript only in body** — summary and action items belong on relevant Basecamp todos, not in this message
+- **Consistent title** — `Fyxer: YYYY-MM-DD` keeps messages uniform and sortable
+
+## Fyxer Index
+
+Each Basecamp project that receives Fyxer meeting transcripts MUST have a **Fyxer Index** document for duplicate detection and meeting history.
+
+### Index format
+
+- **Title**: `Fyxer Index`
+- **Location**: Documents section of each Basecamp project
+- **Content**: One line per posted meeting, newest first
+
+```
+<meeting-uuid> | <date> | <message-id> | <subject>
+```
+
+Example:
+
+```
+52f0cf2b-fdb8-4e95-8b01-2afb6d367c69 | 2026-01-19 | 514789012 | Fyxer: 2026-01-19
+a1b2c3d4-e5f6-7890-abcd-ef1234567890 | 2026-02-10 | 514801234 | Fyxer: 2026-02-10
+```
+
+### Finding posted transcripts
+
+- Check the index: `list_documents(project_id)` → find `Fyxer Index` → `get_document`
+- View a specific transcript: `get_message(project_id, message_id)` using the message_id from the index
+- Browse all messages: `list_messages(project_id)` — Fyxer posts use the title format `Fyxer: YYYY-MM-DD`
+
+### Reconciliation — missing entries
+
+The index MAY fall out of sync. To reconcile:
+
+1. `list_messages(project_id)` → filter for `Fyxer:` titles
+2. For each, `get_message` and extract `fyxer-id` from YAML frontmatter
+3. Compare against the index — add any missing entries
+4. Update the index document
+
+Run reconciliation when the index is first created in a project with existing Fyxer messages, or when the user suspects the index is incomplete.
+
+### Reconciliation — orphaned entries
+
+If an index entry references a deleted message:
+
+1. `get_message(project_id, message_id)` → if 404, remove entry from index
+2. Update the index document
+
+Only run orphan cleanup when explicitly requested by the user.
 
 ## Dependencies
 
+- `simpleapps:basecamp` skill — MCP tools for posting and index management
 - Chrome browser automation (for extraction when cache is empty)

package/skills/simpleapps/workflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: workflow
-description: How we track and deliver work. Covers the Basecamp-to-GitHub flow for client requests, task tracking, and cross-linking. Use when working on client tasks, creating issues, or checking assignments.
+description: How we track and deliver work. Covers the Basecamp-to-GitHub flow for client requests, task tracking, cross-linking, and issue templates. Use when working on client tasks, creating issues, or checking assignments.
 ---
 
 # Workflow
@@ -27,13 +27,41 @@ Basecamp todos and GitHub issues SHOULD cross-link (many-to-many — one todo MA
 
 ## Tooling
 
-The `basecamp` MCP server (bundled with this plugin) provides direct API access to Basecamp 2. Use MCP tools (`get_todo`, `list_my_todos`, `list_documents`, etc.) as the primary method. Chrome browser automation is the fallback if MCP is unavailable.
+Load `simpleapps:basecamp` for Basecamp MCP tools and Chrome fallback. Load `simpleapps:github` for `gh` CLI usage and org conventions.
 
-**First-time setup**: User MUST run `uv run basecamp-auth` once to authorize. Credentials are saved to `~/.simpleapps/basecamp.json`.
+## Creating Issues from Basecamp Todos
+
+Before creating an issue, gather context from Basecamp (see `simpleapps:basecamp` skill for full MCP tool reference):
+1. Use `get_todo` to read the Basecamp todo and summarize the client request
+2. Use `list_documents` + `get_document` to find the project's **site-info** document for siteId and domain name. If no site-info document exists, ask the user to create one in Basecamp.
+
+See the `simpleapps:github` skill for `gh` CLI usage and org conventions.
+
+Issue template for Basecamp-linked issues:
+
+```bash
+gh issue create --repo simpleapps-com/<repo> \
+  --title "<brief technical title>" \
+  --body "## Basecamp
+<basecamp_todo_url>
+
+## Client
+<client/project name> — <domain> (siteId: <siteId>)
+
+## Summary
+<technical summary of what needs to be done>
+
+## Acceptance Criteria
+- [ ] <criteria from the Basecamp request>"
+```
+
+## Cross-Linking
+
+- Include the Basecamp todo URL in the GitHub issue body (under a `## Basecamp` heading)
+- After creating the issue, provide the GitHub issue URL to the user so they can add it to the Basecamp todo comments
 
 ## References
 
-- See `basecamp.md` for MCP tools, Chrome fallback, and Basecamp navigation
-- See `github.md` for Basecamp-to-GitHub cross-linking
+- See `simpleapps:basecamp` skill for MCP tools, Chrome fallback, and Basecamp navigation
 - See `simpleapps:github` skill for GitHub org conventions and `gh` CLI usage
 - See `simpleapps:fyxer` skill for Fyxer meeting transcript processing and Basecamp posting

package/skills/simpleapps/fyxer/basecamp-index.md

@@ -1,110 +0,0 @@
-# Fyxer Index — Basecamp Document
-
-Each Basecamp project that receives Fyxer meeting transcripts MUST have a **Fyxer Index** document. This document serves as a fast lookup for duplicate detection and meeting history, accessible to all team members.
-
-## Document Format
-
-- **Title**: `Fyxer Index`
-- **Location**: Documents section of each Basecamp project
-- **Content**: One line per posted meeting, newest first
-
-Each line follows this format:
-
-```
-<meeting-uuid> | <date> | <message-id> | <subject>
-```
-
-Example:
-
-```
-52f0cf2b-fdb8-4e95-8b01-2afb6d367c69 | 2026-01-19 | 514789012 | Fyxer: 2026-01-19
-a1b2c3d4-e5f6-7890-abcd-ef1234567890 | 2026-02-10 | 514801234 | Fyxer: 2026-02-10
-d9e8f7a6-b5c4-3210-fedc-ba0987654321 | 2026-02-15 | 514823456 | Fyxer: 2026-02-15
-```
-
-Fields:
-
-| Field | Source |
-|-------|--------|
-| meeting-uuid | UUID from Fyxer URL (before the colon) |
-| date | Meeting date (YYYY-MM-DD) |
-| message-id | Basecamp message ID returned by `create_message` |
-| subject | Message subject as posted (e.g., `Fyxer: 2026-02-15`) |
-
-## Finding the Index
-
-```
-list_documents(project_id)
-```
-
-Scan for a document titled `Fyxer Index`. Use `get_document(project_id, document_id)` to read its contents.
-
-## Creating the Index
-
-If no `Fyxer Index` document exists in the project, create one before posting the first meeting:
-
-```
-create_document(project_id, "Fyxer Index", "")
-```
-
-This creates an empty document. The first meeting entry will be appended after posting.
-
-## Updating the Index
-
-After successfully posting a meeting transcript via `create_message`, append a new line to the index:
-
-1. Read the current index: `get_document(project_id, document_id)`
-2. Append the new entry to the content (newest first — add to the top)
-3. Update: `update_document(project_id, document_id, title="Fyxer Index", content=updated_content)`
-
-The `create_message` response includes the message ID needed for the index entry.
-
-## Duplicate Check
-
-Before posting a meeting transcript, check the index:
-
-1. Find the Fyxer Index document: `list_documents(project_id)` → scan for `Fyxer Index`
-2. Read it: `get_document(project_id, document_id)`
-3. Search the content for the meeting UUID
-4. If found → the meeting has already been posted. Inform the user and stop.
-5. If not found → safe to proceed with posting.
-
-If no Fyxer Index document exists, there are no posted meetings in this project. Proceed with posting and create the index.
-
-## Reconciliation — Missing Entries
-
-The index MAY fall out of sync if a meeting was posted without updating the index (e.g., manual posting, index creation after existing meetings). To reconcile:
-
-1. List all messages: `list_messages(project_id)`
-2. Filter for messages with `Fyxer:` in the title
-3. For each Fyxer message, call `get_message(project_id, message_id)` and extract the `fyxer-id` from the YAML frontmatter
-4. Compare against the index — add any missing entries
-5. Update the index document with the complete list
-
-Run reconciliation when:
-- The Fyxer Index document is first created in a project that already has Fyxer messages
-- The user suspects the index is incomplete
-- A duplicate check finds nothing but the user believes a meeting was already posted
-
-## Reconciliation — Orphaned Entries
-
-If an index entry references a message that no longer exists (deleted in Basecamp):
-
-1. Attempt `get_message(project_id, message_id)` for the entry
-2. If 404 → the message was deleted. Remove the entry from the index.
-3. Update the index document
-
-Only run orphan cleanup when explicitly requested by the user. Do not automatically delete index entries.
-
-## Updated Posting Process
-
-The full Fyxer → Basecamp posting process (see `basecamp.md`) now includes index management:
-
-1. **Check index** — find Fyxer Index doc, read it, search for meeting UUID
-2. **Check local cache** — if summary.txt and transcript.txt exist, skip extraction
-3. **Extract from Chrome** — if cache is missing (see `SKILL.md`)
-4. **Build message.txt** — frontmatter + transcript
-5. **Post to Basecamp** — `create_message` → capture message_id from response
-6. **Update index** — append new entry to Fyxer Index document (create doc if needed)
-
-Step 6 is new. If the index update fails after a successful post, warn the user — the message is posted but the index is stale. The user can run reconciliation later to fix it.

package/skills/simpleapps/fyxer/basecamp.md

@@ -1,91 +0,0 @@
-# Fyxer → Basecamp
-
-Post Fyxer meeting recordings as searchable Discussions in Basecamp projects.
-
-## Inputs
-
-- **Fyxer recording URL**: `https://app.fyxer.com/call-recordings/<meeting-uuid>:<calendar-event-id>`
-- **Basecamp project ID**: Target project for the Discussion
-
-## Process
-
-### 1. Check for duplicate
-
-Extract the meeting UUID from the Fyxer URL (the part before the colon).
-
-Find the **Fyxer Index** document in the project: `list_documents(project_id)` → scan for title `Fyxer Index`. If found, `get_document(project_id, document_id)` and search the content for the meeting UUID. If the UUID appears, the meeting has already been posted — inform the user and stop.
-
-If no Fyxer Index document exists, there are no tracked meetings in this project. Proceed with posting.
-
-See `basecamp-index.md` for full index format and reconciliation.
-
-### 2. Check local cache
-
-If `~/.simpleapps/fyxer/<meeting-uuid>/summary.txt` and `transcript.txt` both exist, skip to step 3. Otherwise, follow the Chrome extraction steps in `SKILL.md`.
-
-### 3. Build message.txt
-
-Parse `summary.txt` for frontmatter fields, extract participants (see `SKILL.md` participant extraction), and combine with the full transcript from `transcript.txt`:
-
-```
----
-meeting: SA/ClientName
-date: YYYY-MM-DD
-time: HH:MM-HH:MM
-participants: Person A, Person B, Person C
-topics: Topic One, Topic Two, Topic Three
-fyxer-id: <meeting-uuid>
----
-
-[contents of transcript.txt]
-```
-
-Frontmatter field sources:
-
-| Field | Source |
-|-------|--------|
-| meeting | Meeting title from the page header |
-| date | Recording date |
-| time | Recording time range |
-| participants | Participant dropdown (click to reveal names) |
-| topics | Section headings from the Summary |
-| fyxer-id | Meeting UUID from the URL (before the colon) |
-
-Save as `~/.simpleapps/fyxer/<meeting-uuid>/message.txt`.
-
-### 4. Post to Basecamp
-
-Use `create_message(project_id, subject, content)`:
-
-- **Subject**: `Fyxer: YYYY-MM-DD`
-- **Content**: contents of `message.txt`
-
-Capture the **message_id** from the response.
-
-### 5. Update Fyxer Index
-
-After a successful post, update the Fyxer Index document:
-
-1. If no Fyxer Index document exists, create one: `create_document(project_id, "Fyxer Index", "")`
-2. Read current content: `get_document(project_id, document_id)`
-3. Prepend a new line (newest first): `<meeting-uuid> | <date> | <message-id> | <subject>`
-4. Update: `update_document(project_id, document_id, title="Fyxer Index", content=updated_content)`
-
-If the index update fails after a successful post, warn the user. The message is posted but the index is stale. Run reconciliation later (see `basecamp-index.md`).
-
-## Format Rules
-
-- **Plain text only** — Basecamp prefers plain text over HTML
-- **YAML frontmatter** — machine-parseable so other Claude Code instances can search and parse meeting context
-- **Transcript only in body** — summary and action items belong on relevant Basecamp todos, not in this message
-- **Consistent title** — `Fyxer: YYYY-MM-DD` keeps messages uniform and sortable
-
-## Finding Posted Transcripts
-
-Check the index: `list_documents(project_id)` → find `Fyxer Index` → `get_document`
-View a specific transcript: `get_message(project_id, message_id)` using the message_id from the index
-Browse all messages: `list_messages(project_id)` — Fyxer posts use the title format `Fyxer: YYYY-MM-DD`
-
-## Dependencies
-
-- Basecamp MCP (`create_message`, `create_document`, `update_document`, `list_documents`, `get_document` tools) — see `simpleapps:workflow` skill (`basecamp.md`) for full MCP tool reference

package/skills/simpleapps/workflow/github.md

@@ -1,34 +0,0 @@
-# Basecamp → GitHub Cross-Linking
-
-When a client request in Basecamp needs development work, create a GitHub issue and cross-link them.
-
-## Creating Issues from Basecamp Todos
-
-Before creating an issue, gather context from Basecamp (see `basecamp.md` for full MCP tool reference):
-1. Use `get_todo` to read the Basecamp todo and summarize the client request
-2. Use `list_documents` + `get_document` to find the project's **site-info** document for siteId and domain name. If no site-info document exists, ask the user to create one in Basecamp.
-
-See the `simpleapps:github` skill for `gh` CLI usage and org conventions.
-
-Issue template for Basecamp-linked issues:
-
-```bash
-gh issue create --repo simpleapps-com/<repo> \
-  --title "<brief technical title>" \
-  --body "## Basecamp
-<basecamp_todo_url>
-
-## Client
-<client/project name> — <domain> (siteId: <siteId>)
-
-## Summary
-<technical summary of what needs to be done>
-
-## Acceptance Criteria
-- [ ] <criteria from the Basecamp request>"
-```
-
-## Cross-Linking
-
-- Include the Basecamp todo URL in the GitHub issue body (under a `## Basecamp` heading)
-- After creating the issue, provide the GitHub issue URL to the user so they can add it to the Basecamp todo comments