@simpleapps-com/augur-skills 0.0.12 → 0.0.13

package/package.json

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

package/skills/simpleapps/augur-api/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: augur-api
+description: Augur API integration via MCP. Covers service discovery, CRUD operations across all 27 Augur microservices, and credential resolution. Use when querying or modifying Augur data (contacts, transactions, inventory, etc.).
+---
+
+# Augur API
+
+MCP server exposing all 27 Augur microservices through 6 generic tools.
+
+## Tools
+
+| Tool | Purpose |
+|------|---------|
+| `augur_discover` | List services or endpoints for a service |
+| `augur_list` | List records (GET collection) |
+| `augur_get` | Get single record by ID |
+| `augur_create` | Create record (POST) |
+| `augur_update` | Update record (PUT) |
+| `augur_delete` | Delete record (DELETE) |
+
+## Usage Pattern
+
+Always start with discovery:
+
+1. `augur_discover()` — lists all available services
+2. `augur_discover(service="<name>")` — lists endpoints for a specific service
+3. Use `augur_list`, `augur_get`, `augur_create`, `augur_update`, `augur_delete` for CRUD
+
+Do NOT hardcode service names or endpoints. Use `augur_discover` to find them at runtime.
+
+## Authentication
+
+Credentials resolve automatically — no setup needed if running from a project directory with a `protected/` folder containing credentials.
+
+Resolution order (first match wins):
+
+1. **Env vars** — `AUGUR_TOKEN` + `AUGUR_SITE_ID`
+2. **Explicit file** — `AUGUR_CREDS_FILE` env var pointing to a JSON file
+3. **Ancestor walk** — walks up from cwd looking for `protected/*.json`
+4. **Default file** — `~/.simpleapps/augur-api.json`
+
+Credentials file format: `{"siteId": "...", "jwt": "..."}`
+
+The ancestor walk means client project directories with `protected/<client>.json` just work.
+
+## When Auth Fails
+
+If tools return authentication errors:
+- Check for `protected/*.json` in the project directory or any ancestor
+- Verify the file contains valid `siteId` and `jwt` keys
+- Fallback: set `AUGUR_TOKEN` and `AUGUR_SITE_ID` env vars

package/skills/simpleapps/github/project-structure.md

@@ -6,11 +6,13 @@ Every project MUST use this layout:
 
 ```
 {project}/
-├── repo/    # Main git repo (simpleapps-com/<name>.git)
-└── wiki/    # GitHub wiki repo (simpleapps-com/<name>.wiki.git)
+├── repo/        # Main git repo (simpleapps-com/<name>.git)
+├── wiki/        # GitHub wiki repo (simpleapps-com/<name>.wiki.git)
+├── wip/         # Work-in-progress files for active tasks (not in git)
+└── protected/   # Secrets and credentials for dev testing (not in git)
 ```
 
-The parent `{project}/` directory is NOT a git repo — it's a local wrapper that keeps the code repo and wiki side-by-side.
+The parent `{project}/` directory is NOT a git repo — it's a local wrapper that keeps the code repo and wiki side-by-side. The `wip/` and `protected/` directories sit outside both git trees so their contents can never be accidentally committed.
 
 ## Why This Pattern
 
@@ -38,8 +40,46 @@ If the wiki repo doesn't exist yet, create it by adding any page via the GitHub
 | Repo README | `repo/README.md` | Minimal — quick start + link to wiki |
 | Repo `.claude/rules/` | `repo/` | Minimal summaries referencing wiki pages |
 | Repo `.claude/CLAUDE.md` | `repo/` | Quick reference + wiki links |
+| Active task context | `wip/` | WIP files for Basecamp todos or GitHub issues |
+| Dev secrets | `protected/` | API keys, tokens, test credentials |
 
-Rule of thumb: if a `.md` file isn't built into the end product, it belongs in the wiki.
+Rule of thumb: if a `.md` file isn't built into the end product, it belongs in the wiki. If it contains secrets or ephemeral task state, it belongs outside both git trees.
+
+## WIP Directory
+
+The `wip/` directory holds work-in-progress files that AI agents create when picking up tasks from Basecamp or GitHub issues. Each file tracks research, plans, and progress for an active task.
+
+### Naming Convention
+
+`{issue-number}-{short-description}.md` — e.g., `14-basecamp-mcp-auto-refresh-oauth.md`
+
+### Lifecycle
+
+1. Agent picks up a Basecamp todo or GitHub issue
+2. Creates a WIP file with research findings and implementation plan
+3. Updates the file as work progresses
+4. File remains after completion as a record of decisions made
+
+### What belongs in WIP
+
+- Research findings and code analysis
+- Detailed implementation plans
+- Decision rationale
+- Test results and verification notes
+
+### What does NOT belong in WIP
+
+- Secrets, credentials, or tokens (use `protected/`)
+- Final documentation (use `wiki/`)
+- Code (use `repo/`)
+
+## Protected Directory
+
+The `protected/` directory stores secrets and credentials needed during development and testing. It sits outside all git trees so nothing can be accidentally committed.
+
+Examples: API keys, OAuth tokens, test credentials, `.env` files for local testing.
+
+MUST NOT be committed to any git repository. MUST NOT be copied into `repo/` or `wiki/`.
 
 ## Referencing Wiki from Repo