exa-policy-guardrails
Implement content policy enforcement, domain filtering, and usage guardrails for Exa. Use when setting up content safety rules, restricting search domains, or enforcing query and budget policies for Exa integrations. Trigger with phrases like "exa policy", "exa content filter", "exa guardrails", "exa domain allowlist", "exa content moderation".
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly defines its scope (Exa-specific content policy and guardrails), provides explicit 'Use when' guidance, and includes natural trigger phrases. It uses proper third-person voice throughout and is concise without being vague. The Exa-specific framing makes it highly distinctive among potentially competing skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'content policy enforcement', 'domain filtering', 'usage guardrails', 'restricting search domains', 'enforcing query and budget policies'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (content policy enforcement, domain filtering, usage guardrails for Exa) and 'when' (explicit 'Use when' clause with specific scenarios, plus a 'Trigger with phrases like' section). | 3 / 3 |
Trigger Term Quality | Includes a rich set of natural trigger terms: 'exa policy', 'exa content filter', 'exa guardrails', 'exa domain allowlist', 'exa content moderation'. These are terms users would naturally use, and the Exa-specific prefix helps with precision. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the Exa-specific scope combined with the policy/guardrails niche. The trigger terms are all prefixed with 'exa', making conflicts with generic content moderation or other API skills unlikely. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with fully executable TypeScript code covering domain filtering, query sanitization, freshness policies, and budget enforcement for Exa integrations. Its main weakness is the lack of validation/verification steps—there's no guidance on testing that policies work correctly or recovering from misconfigurations. Minor conciseness improvements could be made by trimming the overview and shortening example domain lists.
Suggestions
Add a validation step showing how to test policy enforcement (e.g., a quick smoke test that verifies blocked patterns reject known-bad queries and domain filters work as expected).
Add error recovery guidance for false positives in query blocking—the error table mentions it but the workflow doesn't show how to debug or adjust patterns.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary elements like the Prerequisites section (Redis mention is vague), and the domain lists could be shorter placeholder examples. The overview paragraph explaining what Exa does is borderline unnecessary context. | 2 / 3 |
Actionability | All code examples are fully executable TypeScript with concrete implementations—domain filtering, query validation with regex patterns, freshness policies, budget enforcement, and a combined orchestration function. Everything is copy-paste ready with real Exa API calls. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (1-5) building toward the combined enforcement function, but there are no validation checkpoints or feedback loops. For a policy enforcement system that blocks queries and enforces quotas, there's no guidance on testing policies, verifying blocked patterns work correctly, or handling edge cases in production. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, an error handling table for quick reference, external resource links, and cross-references to related skills (exa-architecture-variants, exa-cost-tuning). The inline content is appropriately scoped without being monolithic. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Commit
c8a915c
- Reviewed
Table of Contents
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.