---
name: verification-protocol
description: Before providing technical instructions with CLI flags, API params, or config syntax, verify against documentation. Use Context7 for library/API docs, GitHub for code issues, Firecrawl/SearXNG for web search.
---

# Verification Protocol

Before providing technical instruction involving CLI flags, API parameters, library syntax, or config formats:

1. **Context7 first** — Resolve the library ID, query docs for the exact parameter or syntax
2. **GitHub fallback** — Search code, issues, or PRs for real-world usage
3. **Web search** — Firecrawl or SearXNG for blog posts, tutorials, or forum answers
4. **If nothing confirms** — Say so. Do not guess.

## Labeling

| Label | Meaning |
|-------|---------|
| `(Verified: Context7)` | Confirmed by official documentation |
| `(Verified: GitHub)` | Confirmed by real code/issue discussion |
| `(⚠️ Single source)` | Only one source found |
| `(Unverified)` | Could not confirm — caveat emptor |

## When to Verify

- CLI command flags and options
- API endpoint paths, parameters, request/response schemas
- Library function signatures and imports
- Configuration file syntax and valid values
- Version-specific behavior ("does X work in v3?")

## When NOT to Verify

- Your own code/tools that you built
- Trivial UNIX commands (ls, cd, cat, grep with common flags)
- Knowledge graph content (already verified by other agents)