exa-ci-integration

Configure Exa CI/CD integration with GitHub Actions and automated testing. Use when setting up automated testing for Exa integrations, configuring CI pipelines, or adding Exa health checks to builds. Trigger with phrases like "exa CI", "exa GitHub Actions", "exa automated tests", "CI exa", "exa pipeline".

Quality

85%

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

70%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 well-structured, highly actionable skill with executable code and clear step sequencing. It loses points for missing validation/feedback checkpoints in release-related operations and for not leveraging progressive disclosure via separate reference files.

Suggestions

Add an explicit validation checkpoint in the release gate (e.g. run a dry-run or verify secrets before `npm publish`) with a fix-and-retry loop, which would lift workflow_clarity.

Move the full integration test suite and the error-handling table into a referenced file (e.g. references/INTEGRATION_TESTS.md) so SKILL.md stays a lean overview, improving progressive_disclosure and conciseness.

Trim the duplicate GitHub Actions job scaffolding between the two workflow blocks to reduce redundancy and improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete, relevant code and tables, but includes some redundancy (e.g. two near-duplicate GitHub Actions workflow blocks) and minor explanatory padding like the 'Skip integration tests on forks' table row that restates inline comments.	2 / 3
Actionability	Provides fully executable code: a complete GitHub Actions workflow, real `gh secret set` commands, and a complete vitest integration test suite — copy-paste ready with specific values.	3 / 3
Workflow Clarity	Steps are sequenced (Steps 1–4) but there are no explicit validation checkpoints or feedback loops for the destructive/batch-adjacent operations (secrets config, release gate publishing), which the rubric caps at 2 for missing validation.	2 / 3
Progressive Disclosure	Reasonably organized with clear sections, but no bundle/reference files exist and the inline error-handling table plus a second full workflow could be split into references; navigation signals like 'Next Steps' point to an external skill without local reference files.	2 / 3
	Total	9 / 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, specific description with concrete capabilities, an explicit 'Use when' clause, and natural trigger phrases scoped to the Exa CI/CD niche. It is written in third person and clearly distinguishes itself from adjacent skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'automated testing', 'CI pipelines', 'Exa health checks', and 'GitHub Actions' integration — clearly concrete rather than vague.	3 / 3
Completeness	Clearly answers 'what' (configure Exa CI/CD with GitHub Actions and automated testing) and 'when' via the explicit 'Use when setting up...' clause plus trigger phrases.	3 / 3
Trigger Term Quality	Explicit trigger phrases like 'exa CI', 'exa GitHub Actions', 'exa automated tests', 'CI exa', 'exa pipeline' are natural terms a user would say in this domain.	3 / 3
Distinctiveness Conflict Risk	The Exa-specific triggers and GitHub Actions/CI focus create a clear niche unlikely to fire for unrelated skills.	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-ci-integration/SKILL.md
Commit: 4c47e33

Reviewed: 1 day 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.