exa-reliability-patterns

Implement Exa reliability patterns: query fallback chains, circuit breakers, and graceful degradation. Use when building fault-tolerant Exa integrations, implementing fallback strategies, or adding resilience to production search services. Trigger with phrases like "exa reliability", "exa circuit breaker", "exa fallback", "exa resilience", "exa graceful degradation".

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and concise with a clear sequenced structure and built-in error-recovery feedback, but it is a monolithic single-file skill with no bundle references for progressive disclosure.

Suggestions

Move the longer pattern implementations (e.g. circuit breaker, graceful degradation) into separate reference files under references/ and link to them from short summary sections in SKILL.md to enable one-level-deep progressive disclosure.

Add a brief "Quick start" section at the top showing the minimal resilientSearch usage, then point to the detailed Step sections for the full patterns.

If the five patterns are meant to be combined, add an explicit integration example or ordering note clarifying which patterns compose (e.g. degradableSearch wraps searchWithRetry + circuitBreaker).

Dimension	Reasoning	Score
Conciseness	The body is lean executable TypeScript with minimal, purposeful comments and no padding about concepts Claude already knows; the one-line Overview surfaces only Exa-specific failure modes (10 QPS default, crawl blocks) that earn their place.	3 / 3
Actionability	Five complete, copy-paste-ready code blocks (fallback chain, retry/backoff, circuit breaker class, degradation, quality monitor) provide fully executable guidance rather than pseudocode.	3 / 3
Workflow Clarity	Patterns are presented as a clearly numbered Step 1–5 sequence, and the error-handling table plus Step 5 quality monitor supply explicit error-recovery feedback loops.	3 / 3
Progressive Disclosure	All ~240 lines of pattern content live inline in a single file with no references/ scripts/ assets/ bundle; the only navigation is "Next Steps" pointers to sibling skills, so content that could be split into one-level-deep reference files is not.	2 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description cleanly answers what the skill does and when to use it, with concrete named patterns and natural-language trigger phrases in third-person voice. It is concise, specific, and low-conflict.

Dimension	Reasoning	Score
Specificity	"Implement Exa reliability patterns: query fallback chains, circuit breakers, and graceful degradation" lists multiple specific concrete actions, matching the score-3 anchor rather than the single-action score-2 example.	3 / 3
Completeness	It states both what ("Implement Exa reliability patterns...") and when via an explicit "Use when building fault-tolerant Exa integrations..." clause, satisfying the score-3 requirement for explicit triggers.	3 / 3
Trigger Term Quality	Explicit trigger phrases — "exa reliability", "exa circuit breaker", "exa fallback", "exa resilience", "exa graceful degradation" — give good coverage of natural terms a user would say, beyond the partial-coverage score-2 anchor.	3 / 3
Distinctiveness Conflict Risk	The Exa-specific niche and narrowly scoped "exa ..." triggers make it unlikely to fire for unrelated skills, matching the clear-niche score-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/saas-packs/exa-pack/skills/exa-reliability-patterns/SKILL.md
Commit: 4c47e33

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.