voc-source-callslisted

# /voc-source-calls — Pull Call Transcripts Wraps `scripts/fetch-calls.js`. The script does the network work; this skill handles argument resolution, verifies the result, and tells you plainly when the data came back incomplete. ## Requires | What | Value | |---|---| | Env vars | `CALL_PROVIDER`, `CALL_API_KEY`, `CALL_API_SECRET` (provider-dependent), `CALL_API_BASE` | | Optional | `INTERNAL_EMAIL_DOMAINS` — comma-separated, used to label speakers internal vs external when your provider does not | | Node | 18+ (uses global `fetch`) | | Cost | Free. Call-recorder APIs are included in your existing subscription. | If `.env` is missing or a variable is unset, the script exits with the exact list of what is missing. Do not try to work around it by asking the user to paste a key into chat — tell them which variable to set in `.env`. ## Run it ```bash node scripts/fetch-calls.js --window 7d ``` Other forms: | Command | Use | |---|---| | `--window 30d` | Wider backfill | | `--from 2026-01-01 --to 2026-01-07` | Exact range | | `--dry-run` | List what would be pulled, write nothing. **Always do this first on a new setup.** | Calls already on disk are skipped before any transcript request is spent on them, so re-running an overlapping window is cheap and safe. ## After the run — verify, do not assume Read the JSON index at `outputs/calls/index-<to-date>.json` and check three things before reporting success: 1. **`totalFound` is plausible.** Zero on a week your team was sell