CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/evidently-monitoring

Use for any question or task about data drift or quality monitoring for a production ML model, including a fired drift alert and metrics such as precision that degrade slowly unnoticed: Evidently reports with tests for data drift, target drift and performance regression as a CI gate or scheduled job, and a playbook to pick rollback, retrain, quarantine or alert re-tuning.

Quality

91%

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

Overview
Quality
Evals
Security
Files

Quality

Content

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

Highly actionable, executable content with a clearly sequenced workflow and real validation/feedback loops. The main gaps are token efficiency (marketing quote and duplicated gate snippet) and the absence of any progressive disclosure: everything, including the substantial triage playbook, lives inline in one long SKILL.md.

Suggestions

Move the Step 7 triage playbook (signal classification table, root-cause hypothesis ranking, triage discipline) into a references/triage.md file and keep a short summary plus link in SKILL.md, so the body works as an overview.

Delete the duplicated gated-Report code in the Worked example (identical to Step 4) and replace it with a one-line reference back to Step 4, keeping only the narrative outcome.

Drop the marketing quote ("40+ million downloads", "100+ evaluation metrics") from the intro; the metadata version and the install link already orient the reader.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens (Evidently-specific gotchas like ID-column drift, default PSI/JS thresholds, probas_threshold mapping), but the marketing quote ("open-source Python library with over 40+ million downloads... 100+ evaluation metrics") and the near-duplicate CI-gate code block in the Worked example versus Step 4 could be trimmed — minor over-explanation matching the 4 anchor, not the 5.

4 / 5

Actionability

Every phase has copy-paste-ready executable code: pip install, DataDefinition with Dataset.from_pandas, gated Report with include_tests=True and result.dict()["tests"] FAIL/ERROR filtering, BinaryClassification mapping with probas_threshold, a daily scheduled job, and a complete worked example — fully executable and covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

Steps 1–7 are explicitly sequenced with a numbered "How to use" map, validation is present (gate raises SystemExit on FAIL/ERROR, re-run after fix shown in the worked example, "re-run the report before returning the model to live traffic"), and the triage-discipline bullets act as a checklist — clear sequence with explicit validation, feedback loops, and a checklist, matching the 5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), and the full manual — including the ~60-line Step 7 triage playbook, the worked example, and the anti-patterns table — is inlined in a ~340-line SKILL.md. Content that should be separate files is inline, matching the 3 anchor; it is not 4 because the skill is a monolithic single file rather than an overview pointing to detailed materials, and not 2 because section structure is clear and references (Evidently docs URLs) are well-signaled and one level deep.

3 / 5

Total

17

/

20

Passed

Description

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

A strong description that explicitly covers both what the skill does and when to use it, with concrete trigger phrases and a clearly distinct niche. The only weakness is trigger-term coverage: a few natural synonyms (e.g., "model monitoring") are absent.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: "Evidently reports with tests for data drift, target drift and performance regression as a CI gate or scheduled job" plus "a playbook to pick rollback, retrain, quarantine or alert re-tuning" — comprehensive coverage rather than a few actions with gaps, so it matches the 5 anchor and not the 4 anchor.

5 / 5

Completeness

Both what and when are explicit: the what names drift/target/performance tests, CI gate, scheduled job, and a triage playbook; the when opens with "Use for any question or task about data drift or quality monitoring for a production ML model, including a fired drift alert" — concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

Natural phrases like "data drift", "quality monitoring", "production ML model", "fired drift alert", and "precision that degrade slowly" are present, but common variations users would say (e.g., "model monitoring", "model performance", "retraining") are missing, matching the 'good keyword coverage; a few natural terms missing' anchor rather than the 5.

4 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — Evidently-based drift/quality monitoring for production ML models with named triggers ("data drift", "drift alert", "precision") — giving a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

19

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

On this page