CtrlK
BlogDocsLog inGet started
Tessl Logo

evaluate-environments

Run and evaluate verifiers tasksets. Set up the necessary config files and observe the runs and their results.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/evaluate-environments/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

88%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 highly actionable with executable commands, a clearly sequenced validation-gated workflow, and good sectioning. It is efficient but has minor trim opportunities and could lean on reference files for some detail.

DimensionReasoningScore

Conciseness

The body is dense and operational with executable commands and minimal padding, though a few editorializing lines (e.g. 'This is one of the most important settings, so make sure to find the correct values') could be trimmed.

4 / 5

Actionability

Extensive copy-paste-ready bash and TOML examples cover the common evaluation cases concretely, from dry-run and small runs to retries, TOML config, and resume.

5 / 5

Workflow Clarity

The numbered core workflow has explicit validation checkpoints (dry-run config resolution, gold validation, small run before scaling) plus error-recovery feedback via retries and resume, matching the batch-operation expectation.

5 / 5

Progressive Disclosure

Content is organized into clearly labeled sections and offloads implementation detail to concrete source paths in the codebase, though the ~200-line body could arguably split some detail into reference files.

4 / 5

Total

18

/

20

Passed

Description

53%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 states a clear 'what' for a specific niche but lacks an explicit 'Use when' trigger clause, capping completeness. Trigger-term coverage is adequate but not comprehensive.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when reproducing taskset results or evaluating a model/harness combination on a taskset').

Expand natural trigger terms with synonyms users might say, such as 'reproduce results', 'run an evaluation', 'benchmark a taskset'.

Sharpen the concrete actions beyond generic phrasing like 'set up the necessary config files' and 'observe the runs and their results'.

DimensionReasoningScore

Specificity

Names the domain ('verifiers tasksets') and lists a few concrete actions ('Run and evaluate', 'Set up the necessary config files', 'observe the runs and their results'), but the actions are somewhat generic and coverage is not comprehensive.

3 / 5

Completeness

The 'what' is clear but there is no 'Use when...' trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural phrases like 'Run and evaluate verifiers tasksets' and 'observe the runs and their results', but misses common variations and synonyms users might say.

3 / 5

Distinctiveness Conflict Risk

The 'verifiers tasksets' niche is fairly specific and distinct, with only minor overlap risk against closely related evaluation skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
PrimeIntellect-ai/verifiers
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.