CtrlK
BlogDocsLog inGet started
Tessl Logo

eagle3-review-logs

Review EAGLE3 pipeline experiment logs from the launcher's experiments/ directory. Summarizes pass/fail status for all 4 tasks, diagnoses failures with root causes and fixes, and flags warnings. Use when the user asks to review job logs, check experiment results, or diagnose why a specific task failed.

79

Quality

100%

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

100%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, token-efficient skill body that gives executable commands, a clear sequenced workflow with a checkpoint, and a useful output template plus benign-pattern table. It assumes Claude's competence and stays appropriately self-contained.

DimensionReasoningScore

Conciseness

Lean and efficient with no explanations of concepts Claude already knows (no primers on pipelines, Slurm, or CUDA); every line earns its place, e.g. 'errors surface at the end' justifies the tail-based read. Not score 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Provides fully executable commands — the find/tail log-reading loop, the ls discovery one-liner, and the uv re-run invocation — that are copy-paste ready; the only placeholder (<exp_id>) is justified because Step 0 shows how to discover it. Not score 2 because the guidance is concrete rather than pseudocode.

3 / 3

Workflow Clarity

A clear numbered sequence (Step 0–4) with a conditional checkpoint ('If no experiments exist, ask the user') and a concrete analysis checklist in Step 2; this is a read-only diagnosis task so the destructive/batch feedback-loop cap does not apply. Not score 2 because checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

No bundle files exist and the body is self-contained, single-purpose, and well-organized into clear sections with nothing that needs splitting out (the benign-patterns table is short and useful inline); per the simple-skills note, well-organized content scores 3 without external references. Not score 2 because organization is clear and there are no nested or poorly-signaled references.

3 / 3

Total

12

/

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, third-person description that pairs a precise capability statement with an explicit 'Use when...' trigger clause covering natural user phrasings. It is specific, complete, and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Summarizes pass/fail status for all 4 tasks', 'diagnoses failures with root causes and fixes', 'flags warnings' — matching the score-3 anchor for multiple specific concrete actions; not score 2 because it goes beyond naming a domain plus some actions.

3 / 3

Completeness

Explicitly answers both what (review/summarize/diagnose/flag) and when ('Use when the user asks to review job logs, check experiment results, or diagnose why a specific task failed'); not score 2 because the 'when' is explicit, not merely implied.

3 / 3

Trigger Term Quality

Natural user phrasings — 'review job logs', 'check experiment results', 'diagnose why a specific task failed' — give good coverage of terms a user would actually say; not score 2 because common variations are present rather than missing.

3 / 3

Distinctiveness Conflict Risk

A clear niche (EAGLE3 pipeline experiment logs) with distinct triggers makes it unlikely to fire for unrelated skills, matching the score-3 anchor; not score 2 because it is not merely 'somewhat specific' but sharply scoped.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
NVIDIA/Model-Optimizer
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.