Skip to content
Skills Library
DevOps & cloud · Tool integration

serpapi-deploy-integration

/serpapi-deploy-integration

Deploy a server-side SerpAPI gateway with secret isolation, input policy, capacity controls, canary evidence, and rollback. Use when promoting a search integration. Trigger with "deploy a SerpAPI gateway".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
3
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Deploy a server-side SerpAPI gateway with secret isolation, input policy, capacity controls, canary evidence, and rollback. Use when promoting a search integration. Trigger with "deploy a SerpAPI gateway".

Triggers from the description

deploy a SerpAPI gateway

Arguments

/serpapi-deploy-integration [platform] [environment] [route]
Original author description

Deploy a server-side SerpAPI gateway with secret isolation, input policy, capacity controls, canary evidence, and rollback. Use when promoting a search integration. Trigger with "deploy a SerpAPI gateway".

How it works

  1. Overview
  2. Prerequisites
  3. Tool Discipline
  4. Current Contract
  5. Authentication
  6. Instructions
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Example
Original SKILL.md headings · 67 lines, 439 words
SKILL.md preview
---
name: serpapi-deploy-integration
description: 'Deploy a server-side SerpAPI gateway with secret isolation, input policy, capacity controls, canary evidence, and rollback. Use when promoting a search integration. Trigger with "deploy a SerpAPI gateway".'
argument-hint: "[platform] [environment] [route]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [saas, serpapi, deployment, gateway, canary]
model: inherit
effort: high
compatibility: Designed for Claude Code; deployment, secret, routing, and production search changes require explicit platform and account-owner approval
---
# SerpAPI Gateway Deployment

## Overview

Promote a narrow backend gateway through preview, canary, reconciliation, and rollback without exposing the SerpAPI key or an open search proxy.

## Prerequisites

- A fixture-tested gateway, deployment owner, route, caller identity, and rollback target
- Approved secret manager, data classification, SLO, capacity budget, and observability
- Platform-specific release and health-check conventions

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect application and infrastructure changes, `WebFetch` to verify current SerpAPI contracts, and `Write` or `Edit` for deployment configuration, policies, probes, tests, and redacted receipts.

## Current Contract

SerpAPI search calls require a private key and engine-specific parameters. Account capacity is discoverable through Account API. Public browser clients should call an authenticated application backend rather than SerpAPI directly.

## Authentication

Inject `SERPAPI_KEY` from the target platform's server-side secret store. Authenticate gateway callers separately, validate their authorization to the requested use case, and never return vendor account or credential data.

## Instructions

1. Review the deploy diff, dependency lock, secret references, route exposure, caller authentication, input allowlist, output projection, and data retention.
2. Define readiness without a billable search; expose only internal health and configuration status, not Account API details.
3. Set finite client and request timeouts, concurrency/admission limits, cache policy, retry budget, and maximum pagination.
4. Deploy to an isolated preview with no production key and run fixture, authorization, abuse, redaction, and rollback tests.
5. Present the production mutation, live-search budget, monitoring, owner, and exact rollback command for approval.
6. Deploy a small canary, execute one approved harmless search, and reconcile status, search ID, latency, errors, and capacity.
7. Promote gradually only while SLO, correctness, privacy, and allowance thresholds hold; otherwise roll back immediately.

## Approval Boundaries

Do not create or change a production secret, public route, caller policy, traffic allocation, or live canary without named approval.

## Output

Return the deploy diff, access and secret model, preview tests, canary receipt, capacity and SLO evidence, promotion decision, rollback proof, and owners.

## Error Handling

| Condition | Response |
|---|---|
| Key appears in client assets | Block and rotate under incident procedure. |
| Gateway accepts arbitrary parameters | Fail the release and enforce a use-case allowlist. |
| Canary breaches errors, latency, or capacity | Roll back and preserve redacted search IDs. |
| Health endpoint leaks account facts | Remove the fields before exposure. |

## Example

```text
environment=production; callers=authenticated; key=server-secret; preview=pass; canary_searches=1; capacity=healthy; promotion=approved; rollback=verified
```

## Resources

- [SerpAPI error guide for web applications](https://serpapi.com/blog/fix-serpapi-errors-guide/)
- [Account API](https://serpapi.com/account-api)
- [SerpAPI security](https://serpapi.com/security)

## Next Steps

Observe a complete workload cycle and rehearse rollback and key rotation with the owning teams.

Versions

The database has no other skills named serpapi-deploy-integration.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 562233ab2397 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100serpapi-ci-integration
    Gate SerpAPI code with sanitized fixtures and isolate optional live searches behind trusted CI environments and allowance controls. Use when adding integration tests to automation. Trigger with "add SerpAPI CI".
  • 100mistral-deploy-integration
    Deploy a Mistral-backed service with secret isolation, bounded concurrency, health semantics, canary evidence, and rollback. Use when preparing runtime delivery. Trigger with "deploy a Mistral app", "configure Mistral production", or "canary a Mistral service".
  • 90infra-stack-deploy
    Deploys one environment's stack through the project's own deploy entrypoint with a check before and after and the rollback path ready, never by hand on the host. Use when an environment needs a deploy outside its normal pipeline, or to drive a failed one to a known state.
  • 100aliyun-fullstack-deploy
    Deploy full-stack apps to user-authorized Alibaba Cloud ECS or comparable Linux VPS hosts with preflight, canary verification, and rollback. Use for production deployment and recovery; never purchase infrastructure or mutate an unauthorized host.
  • 100deploy
    Post-merge deployment workflow covering feature flags, canary/blue-green rollout, smoke-test verification, and rollback triggers. Use after a PR is merged and you need to ship it safely to production. Trigger on "deploy", "roll out", "canary", "feature flag", "rollback".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.