evergreen

Evergreen CI infrastructure, configuration validation. Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix.

Quality

83%

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

78%Weight 40%Scale 1-5

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

The body is a concise, well-structured, single-purpose skill with executable commands and an explicit validation checkpoint. The main gap is the absence of an explicit failure/feedback loop after validation or patch builds.

Dimension	Reasoning	Score
Conciseness	The body is lean and mostly assumes competence, with minor over-explanation such as 'This uploads your uncommitted and committed local changes as a patch build on Evergreen...' and slight H1/H2 title redundancy. It is not a 5 because a couple of sentences restate what the command does, and not a 3 because there is no padding of concepts Claude already knows.	4 / 5
Actionability	Provides two concrete, copy-paste commands ('evergreen validate .evergreen/.evg.yml', 'evergreen patch -u') covering the main operations. It is not a 5 because there is no guidance on interpreting patch-build results or handling validation output, and not a 3 because the commands are executable rather than pseudocode.	4 / 5
Workflow Clarity	Clear sequence with an explicit local validation checkpoint before submitting, plus a patch-build test step before merging. The destructive/batch cap at 3 does not apply because validation is present; it is not a 5 because no explicit feedback loop (validate -> fix -> re-validate) is documented.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references and well-organized sections (overview, validating, patch build), qualifying for the simple-skill exception. It is not a 4 because no organization gaps are present given the skill's scope.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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 is strong: it states concrete capabilities and provides an explicit, well-triggered 'Use when' clause tied to a distinct internal CI niche. Minor gaps in action coverage and synonym breadth keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the Evergreen CI domain plus several concrete actions ('configuration validation', 'modifying .evergreen/ config', 'preparing to submit changes', 'understanding the Evergreen test matrix'), with minor gaps such as omitting patch builds. It is not a 5 because coverage is not comprehensive, and not a 3 because more than 1-2 specific actions are listed.	4 / 5
Completeness	Explicitly answers both 'what' ('Evergreen CI infrastructure, configuration validation') and 'when' ('Use when modifying .evergreen/ config, preparing to submit changes or understanding the Evergreen test matrix') with concrete trigger phrases. It is not a 4 because the 'when' is fully explicit and specific rather than merely adequate.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('modifying .evergreen/ config', 'preparing to submit changes', 'Evergreen test matrix') with good coverage. It is not a 5 because synonyms and file extensions are missing, and not a 3 because several relevant natural terms are present rather than just one or two generic keywords.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (MongoDB's internal Evergreen CI) with distinct triggers (.evergreen config, test matrix) and minimal conflict risk. It is not a 4 because there is essentially no overlap with unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: mongodb/mongo-java-driver
Path: .agents/skills/evergreen/SKILL.md
Commit: 9af9be1

Reviewed: 13 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.