Skip to content
Skills Library
Security · Review & audit

serpapi-security-basics

/serpapi-security-basics

Threat-model SerpAPI credentials, query data, result retention, browser exposure, logs, and ZeroTrace tradeoffs. Use when reviewing or hardening a search integration. Trigger with "secure a SerpAPI integration".

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

Threat-model SerpAPI credentials, query data, result retention, browser exposure, logs, and ZeroTrace tradeoffs. Use when reviewing or hardening a search integration. Trigger with "secure a SerpAPI integration".

Triggers from the description

secure a SerpAPI integration

Arguments

/serpapi-security-basics [application] [data-classification]
Original author description

Threat-model SerpAPI credentials, query data, result retention, browser exposure, logs, and ZeroTrace tradeoffs. Use when reviewing or hardening a search integration. Trigger with "secure a SerpAPI integration".

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, 505 words
SKILL.md preview
---
name: serpapi-security-basics
description: 'Threat-model SerpAPI credentials, query data, result retention, browser exposure, logs, and ZeroTrace tradeoffs. Use when reviewing or hardening a search integration. Trigger with "secure a SerpAPI integration".'
argument-hint: "[application] [data-classification]"
allowed-tools: Read, Glob, Grep, WebFetch, Write, Edit
version: 1.6.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags: [saas, serpapi, security, privacy, secrets]
model: inherit
effort: high
compatibility: Designed for Claude Code; key rotation, ZeroTrace enablement, retention changes, and production proxy changes require security and account-owner approval
---
# SerpAPI Security and Privacy Controls

## Overview

Protect the private key and treat queries, parameters, raw results, archive records, fixtures, and telemetry as potentially sensitive data.

## Prerequisites

- Application and data-flow inventory, data classification, threat model, and retention policy
- Account plan and entitlement evidence for any privacy feature
- Owners for secrets, application security, privacy, logging, and incident response

## Tool Discipline

Use `Read`, `Glob`, and `Grep` to inspect secret flow, browser bundles, logs, caches, and fixtures, `WebFetch` to verify current security and retention claims, and `Write` or `Edit` for server-side boundaries, redaction, tests, and evidence.

## Current Contract

SerpAPI requires a private API key and recommends server-side use for web applications. Standard search data is documented as expiring after 31 days. Enterprise ZeroTrace mode uses `zero_trace=true` to skip storing search parameters, files, and metadata, which also removes archive-based debugging; eligibility and exact guarantees must be rechecked against the account contract.

## Authentication

Keep `SERPAPI_KEY` in an approved server-side secret manager. Never ship it in browser or mobile bundles, accept it from end users, include it in URLs that are logged, or return Account API data to unauthenticated clients.

## Instructions

1. Map the key from secret store to client and prove it cannot reach source, client bundles, logs, traces, caches, fixtures, errors, or support exports.
2. Classify queries and results, document permitted purposes, and reject disallowed or unnecessarily sensitive input before search.
3. Expose an application-specific backend endpoint with authenticated callers, input allowlists, output minimization, rate limiting, and abuse monitoring.
4. Strip key-bearing URLs and unneeded raw result fields before persistence; set cache and log retention from policy rather than convenience.
5. Decide whether standard archive/debug behavior or ZeroTrace better matches the data class; do not combine ZeroTrace with a workflow that requires archive replay.
6. Test unauthorized callers, parameter injection, quota abuse, log leakage, fixture leakage, dependency compromise, and key revocation.
7. Present rotation, ZeroTrace, retention, or production-boundary changes for approval and retain a redacted control receipt.

## Approval Boundaries

Do not rotate a key, enable account features, change production retention, expose a proxy, or process a new sensitive data class without named owner approval.

## Output

Return the threat model, secret-flow proof, data classification, proxy controls, retention/ZeroTrace decision, negative-test results, approval record, and incident/rotation owners.

## Error Handling

| Condition | Response |
|---|---|
| Key appears in history or telemetry | Revoke or rotate under incident procedure and purge authorized copies. |
| Browser bundle references the key | Block release and move the call behind an authenticated backend. |
| Sensitive search used standard retention | Notify privacy/security owners and follow the approved deletion process. |
| ZeroTrace search needs archive debugging | Use local redacted evidence; do not assume an archive record exists. |

## Example

```text
key=server-secret-only; callers=authenticated; inputs=allowlisted; output=minimized; standard-retention=31-days; zero-trace=contract-reviewed; leakage-tests=pass
```

## Resources

- [SerpAPI security](https://serpapi.com/security)
- [ZeroTrace Mode](https://serpapi.com/zero-trace-mode)
- [Data retention and deletion](https://serpapi.com/legal#data-retention-and-deletion)

## Next Steps

Schedule a key-leak and public-endpoint abuse drill, then review the controls after any data-class change.

Versions

The database has no other skills named serpapi-security-basics.

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

Database snapshot: 13.11.2026 · package version eee9cee46d8f (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

  • 100mistral-security-basics
    Threat-model Mistral credentials, untrusted content, model output, tools, files, and tenant access. Use when securing or reviewing an integration. Trigger with "secure Mistral", "audit Mistral prompts", or "threat model a Mistral app".
  • 100serpapi-install-auth
    Install an official SerpAPI client, configure the private API key for server-side use, and verify account access without leaking credentials. Use when starting or repairing a SerpAPI integration. Trigger with "configure SerpAPI access".
  • 100security-basics
    Essential security checklist and patterns for web applications. Use when reviewing code for security issues, implementing authentication, or hardening an application. Covers OWASP top 10, input validation, and secure coding practices.
  • 100linear-security-basics
    Secure API key management and OAuth best practices for Linear. Use when setting up authentication securely, implementing OAuth flows, or hardening Linear integrations. Trigger with phrases like "linear security", "linear API key security", "linear OAuth", "secure linear…
  • 90security-reactnative
    Security - React Native 0.87 Best Practices. Use when reviewing security, implementing auth, or hardening code.

Feedback and reports

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