serpapi-local-dev-loop
Configure SerpApi local development with cached responses and test fixtures. Use when building search integrations, avoiding API calls during development, or setting up reproducible test data from SerpApi. Trigger: "serpapi dev setup", "serpapi local", "test serpapi locally".
Best use case
serpapi-local-dev-loop is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Configure SerpApi local development with cached responses and test fixtures. Use when building search integrations, avoiding API calls during development, or setting up reproducible test data from SerpApi. Trigger: "serpapi dev setup", "serpapi local", "test serpapi locally".
Teams using serpapi-local-dev-loop should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/serpapi-local-dev-loop/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How serpapi-local-dev-loop Compares
| Feature / Agent | serpapi-local-dev-loop | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Configure SerpApi local development with cached responses and test fixtures. Use when building search integrations, avoiding API calls during development, or setting up reproducible test data from SerpApi. Trigger: "serpapi dev setup", "serpapi local", "test serpapi locally".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# SerpApi Local Dev Loop
## Overview
Set up local development for SerpApi with response caching, fixture recording, and offline testing. SerpApi charges per search, so caching results locally is critical for cost-effective development.
## Instructions
### Step 1: Record Real Responses as Fixtures
```python
import serpapi, json, os, hashlib
def record_fixture(params: dict, fixtures_dir="tests/fixtures"):
"""Run a real search and save the response as a fixture file."""
os.makedirs(fixtures_dir, exist_ok=True)
client = serpapi.Client(api_key=os.environ["SERPAPI_API_KEY"])
result = client.search(**params)
# Deterministic filename from params
key = hashlib.md5(json.dumps(params, sort_keys=True).encode()).hexdigest()[:12]
path = os.path.join(fixtures_dir, f"{params['engine']}_{key}.json")
with open(path, "w") as f:
json.dump(dict(result), f, indent=2)
print(f"Recorded: {path}")
# Record fixtures for common queries
record_fixture({"engine": "google", "q": "python tutorial", "num": 5})
record_fixture({"engine": "youtube", "search_query": "react hooks"})
record_fixture({"engine": "bing", "q": "machine learning"})
```
### Step 2: Mock Client for Testing
```python
import json, os
class MockSerpApiClient:
def __init__(self, fixtures_dir="tests/fixtures"):
self.fixtures_dir = fixtures_dir
def search(self, **params):
key = hashlib.md5(json.dumps(params, sort_keys=True).encode()).hexdigest()[:12]
path = os.path.join(self.fixtures_dir, f"{params['engine']}_{key}.json")
if os.path.exists(path):
with open(path) as f:
return json.load(f)
raise FileNotFoundError(f"No fixture for {params}. Run record_fixture() first.")
```
### Step 3: Vitest Mocking (Node.js)
```typescript
// tests/serpapi.test.ts
import { describe, it, expect, vi } from 'vitest';
import { readFileSync } from 'fs';
vi.mock('serpapi', () => ({
getJson: vi.fn(async (params) => {
const fixture = JSON.parse(
readFileSync(`tests/fixtures/google_sample.json`, 'utf-8')
);
return fixture;
}),
}));
describe('Search Service', () => {
it('parses organic results', async () => {
const { getJson } = await import('serpapi');
const result = await getJson({ engine: 'google', q: 'test' });
expect(result.organic_results).toBeDefined();
expect(result.organic_results[0]).toHaveProperty('title');
expect(result.organic_results[0]).toHaveProperty('link');
});
});
```
### Step 4: Environment Separation
```bash
# .env.development (uses real API, low num for cost)
SERPAPI_API_KEY=real-key-here
SERPAPI_DEFAULT_NUM=3
# .env.test (uses fixtures, no API calls)
SERPAPI_API_KEY=not-needed
SERPAPI_USE_FIXTURES=true
```
## Error Handling
| Error | Cause | Solution |
|-------|-------|----------|
| `FileNotFoundError` fixture | Missing fixture | Run `record_fixture()` with real API key |
| Stale fixtures | Search results changed | Re-record periodically |
| `Invalid API key` in dev | Env not loaded | Check `.env.development` loading |
## Resources
- [SerpApi Playground](https://serpapi.com/playground)
- [Vitest Mocking](https://vitest.dev/guide/mocking.html)
## Next Steps
Proceed to `serpapi-sdk-patterns` for production patterns.Related Skills
workhuman-local-dev-loop
Workhuman local dev loop for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman local dev loop".
wispr-local-dev-loop
Wispr Flow local dev loop for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr local dev loop".
windsurf-local-dev-loop
Configure Windsurf local development workflow with Cascade, Previews, and terminal integration. Use when setting up a development environment, configuring Turbo mode, or establishing a fast iteration cycle with Windsurf AI. Trigger with phrases like "windsurf dev setup", "windsurf local development", "windsurf dev environment", "windsurf workflow", "develop with windsurf".
webflow-local-dev-loop
Configure a Webflow local development workflow with TypeScript, hot reload, mocked API tests, and webhook tunneling via ngrok. Use when setting up a development environment, configuring test workflows, or establishing a fast iteration cycle with the Webflow Data API. Trigger with phrases like "webflow dev setup", "webflow local development", "webflow dev environment", "develop with webflow".
vercel-local-dev-loop
Configure Vercel local development with vercel dev, environment variables, and hot reload. Use when setting up a development environment, testing serverless functions locally, or establishing a fast iteration cycle with Vercel. Trigger with phrases like "vercel dev setup", "vercel local development", "vercel dev environment", "develop with vercel locally".
veeva-local-dev-loop
Veeva Vault local dev loop for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva local dev loop".
vastai-local-dev-loop
Configure Vast.ai local development with testing and fast iteration. Use when setting up a development environment, testing instance provisioning, or building a fast iteration cycle for GPU workloads. Trigger with phrases like "vastai dev setup", "vastai local development", "vastai dev environment", "develop with vastai".
twinmind-local-dev-loop
Set up local development workflow with TwinMind API integration. Use when building applications that integrate TwinMind transcription, testing API calls locally, or developing meeting automation tools. Trigger with phrases like "twinmind dev setup", "twinmind local development", "twinmind API testing", "build with twinmind".
together-local-dev-loop
Together AI local dev loop for inference, fine-tuning, and model deployment. Use when working with Together AI's OpenAI-compatible API. Trigger: "together local dev loop".
techsmith-local-dev-loop
TechSmith local dev loop for Snagit COM API and Camtasia automation. Use when working with TechSmith screen capture and video editing automation. Trigger: "techsmith local dev loop".
supabase-local-dev-loop
Configure Supabase local development with the CLI, Docker, and migration workflow. Use when initializing a Supabase project locally, starting the local stack, writing migrations, seeding data, or iterating on schema changes. Trigger with phrases like "supabase local dev", "supabase start", "supabase init", "supabase db reset", "supabase local setup".
stackblitz-local-dev-loop
Configure local development for WebContainer applications with hot reload and testing. Use when building browser-based IDEs, testing WebContainer file operations, or setting up development workflows for WebContainer projects. Trigger: "stackblitz dev setup", "webcontainer local", "test webcontainers locally".