CtrlK
BlogDocsLog inGet started
Tessl Logo

exa-prod-checklist

Execute Exa production deployment checklist with pre-flight, deploy, and rollback. Use when deploying Exa integrations to production, preparing for launch, or verifying production readiness. Trigger with phrases like "exa production", "deploy exa to prod", "exa go-live", "exa launch checklist", "exa production ready".

76

Quality

96%

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

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.

A highly actionable, well-sequenced deployment checklist with executable code and explicit validation checkpoints. Its main weakness is progressive disclosure: all content is inline in one long file with no reference files to offload detail.

Suggestions

Move the detailed Pre-Deployment Checklist (Security, Code Quality, Performance, Monitoring) into a references file (e.g. references/pre-deployment-checklist.md) and keep SKILL.md as an overview that links to it, improving progressive disclosure.

Extract the Alert Thresholds and Error Handling tables into a references/operations-runbook.md, leaving a short summary inline with a clearly signaled link.

Signal the sibling-skill references more prominently (e.g. a 'Related skills' section near the top) rather than only mentioning them in the final 'Next Steps' line.

DimensionReasoningScore

Conciseness

The body is dense and operational — checkboxes, executable code blocks, and compact tables — with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Provides fully executable, copy-paste-ready guidance: real curl pre-flight checks with `set -euo pipefail`, a TypeScript health-check endpoint, and concrete kubectl rollout/rollback commands.

3 / 3

Workflow Clarity

Clear sequence (Pre-Deployment → Deploy Step 1-3 → Post-Deployment → Rollback) with explicit validation checkpoints (API status check, `npm test`, health endpoint) and a feedback/recovery loop via the rollback procedure.

3 / 3

Progressive Disclosure

Well-organized into clear sections and external links (Exa docs, sibling skills), but the entire ~155-line checklist lives inline in SKILL.md with no bundle/reference files splitting out detail; the under-50-line simple-skill exception does not apply.

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.

A strong, well-structured description that concisely states the skill's purpose, gives an explicit 'Use when' trigger condition, and lists natural trigger phrases a user would actually say. It uses third-person voice and avoids fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'pre-flight, deploy, and rollback' — naming the three distinct phases of the deployment checklist rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Execute Exa production deployment checklist with pre-flight, deploy, and rollback') and when ('Use when deploying Exa integrations to production, preparing for launch, or verifying production readiness'), plus explicit trigger phrases.

3 / 3

Trigger Term Quality

Provides good coverage of natural trigger phrases users would say: 'exa production', 'deploy exa to prod', 'exa go-live', 'exa launch checklist', 'exa production ready'.

3 / 3

Distinctiveness Conflict Risk

Clear niche scoped to Exa production deployment with 'exa'-prefixed triggers, making it unlikely to fire for unrelated 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.