Skills

Provider Research

Research every provider behind Pipecat's services for new models and API affordances...

Install

npx skills add pipecat-ai/pipecat --skill provider-research -g -a claude-code -y
Repository
pipecat-ai/pipecat17k
Category
Writing
Updated
3d ago
License
BSD-2-Clause
Context cost
Mediumabout 1,932 tokens
Runs scripts
No, instructions only

What it does

Research every provider behind Pipecat's services for new models and API affordances, writing per-service reports and local branches for clear-cut updates; publishing is scripts/provider-watch/publish.py's job, run outside this skill

Run a provider-research sweep: one researcher subagent per service unit, a concise dated report per unit, and a committed branch for every change a researcher is confident about. Everything stays local, this skill publishes nothing. Pushing reports, opening draft PRs on pipecat and filing the digest issue are scripts/provider-watch/publish.py's job, run after the research by whoever invoked it; the run ends by printing the commands. You are the orchestrator; the research itself happens in provider-watch-researcher subagents following RESEARCH_GUIDE.md.

Arguments

/provider-research [--only a,b] [--date YYYY-MM-DD] [--limit N] [--concurrency N]
  • --only a,b, providers or unit ids (openai, deepgram/stt). Default: every unit.
  • --date YYYY-MM-DD, the run date. Defaults to today; separate runs over disjoint --only slices with the same date compose into one sweep.
  • --limit N, research only the first N selected units (deterministic order). For test runs.
  • --concurrency N, researchers per batch. Default 6; use 1 for a linear test run.

Examples:

  • /provider-research --only deepgram,groq --limit 2 --concurrency 1, smoke test
  • /provider-research --only groq, exercise the branch path; review the branch with the command the report prints

Instructions

Step 1: Resolve paths and prerequisites

Read the whole SKILL.md on GitHub

More in Writing