Individual skill
exa-reliability-patterns
Design bounded Exa retries, deadlines, partial-result behavior, and tested fallbacks by endpoint and failure class. Use when operating or reviewing this Exa boundary. Trigger with "Exa reliability patterns", "review Exa reliability patterns", or "fix Exa reliability patterns".
plugins/saas-packs/exa-pack/skills/exa-reliability-patterns/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,916
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- exa Declared skill tag
- design Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,832 bytesSKILL.mdcore · 4,832 bytesreferences/official-docs.mddoc · 1,835 bytes
Read excerpt
# Exa Reliability and Retry Design
## Overview
Design bounded Exa retries, deadlines, partial-result behavior, and tested fallbacks by endpoint and failure class. Treat credentials, queries, retrieved content, generated output, spend, and destructive state as separately governed boundaries.
## Prerequisites
- The target repository, environment, Exa team, product surface, and accountable owner.
- The workload's data classification, latency and freshness promise, cost ceiling, and retention policy.
- Current first-party documentation plus credentials only for a narrowly approved live check.
## Current Contract
Retryability depends on status and operation. Invalid 400, auth, policy, and billing failures require repair; 429 honors Retry-After; documented transient server or overload failures can use capped jitter. Asynchronous creates and destructive calls require identity and state checks before replay.