CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-security-basics

Secure Exa API keys, implement content moderation, and manage domain restrictions. Use when securing API keys, auditing Exa security configuration, or implementing content safety filtering. Trigger with phrases like "exa security", "exa secrets", "secure exa", "exa API key security", "exa content moderation".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A highly actionable, well-sequenced security skill with executable code and validation checkpoints, including a verify-before-revoke rotation loop. It loses points for redundancy between the steps, checklist, and error table, and for keeping all detail inline rather than offloading some to reference files.

Suggestions

Collapse the Security Checklist and Error Handling table or move them to a reference file, since they restate mitigations already shown in Steps 1-5.

Move the longer worked examples (Git history scan, key rotation procedure) into a separate references/ file linked from a brief Examples section to improve progressive disclosure.

Trim obvious inline code comments (e.g. '// filter unsafe content from results', '// never return results from these') that restate the surrounding instruction.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code, but the Security Checklist and Error Handling table restate mitigations already covered in the steps (e.g. moderation: true, query sanitization, domain allowlists), adding redundancy that could be tightened.

2 / 3

Actionability

It provides complete, copy-paste-ready TypeScript and bash (environment setup, secure client creation, domain filtering, sanitization, key rotation curl), matching the anchor for fully executable, specific examples.

3 / 3

Workflow Clarity

Steps 1-5 are clearly sequenced, Step 1 includes key validation, the rotation procedure verifies the new key before revoking the old one, and a checklist guides the overall process — an explicit validate-before-destructive feedback loop.

3 / 3

Progressive Disclosure

The file is well-sectioned but monolithic at ~185 lines with no bundle reference files; detailed code examples, the error table, and rotation procedure are all inline rather than split into one-level-deep references, so organization is good but not appropriately distributed.

2 / 3

Total

10

/

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.

A strong, third-person description that clearly states capabilities, provides an explicit Use-when clause, and lists natural trigger phrases scoped to Exa security. It is concise and free of fluff.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Secure Exa API keys, implement content moderation, and manage domain restrictions' — matching the anchor for naming several specific actions rather than vague language.

3 / 3

Completeness

It explicitly answers both what (secure keys, content moderation, domain restrictions) and when ('Use when securing API keys, auditing Exa security configuration, or implementing content safety filtering'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

It enumerates natural trigger phrases a user would actually say ('exa security', 'exa secrets', 'secure exa', 'exa API key security', 'exa content moderation'), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The Exa-specific qualifier and security-scoped triggers carve a clear niche unlikely to fire for unrelated skills, distinguishing it from generic API or security skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.