Model Checkpoint Manager - Auto-activating skill for ML Training. Triggers on: model checkpoint manager, model checkpoint manager Part of the ML Training skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill model-checkpoint-managerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It only states the skill name and category without describing any capabilities, actions, or use cases. The redundant trigger terms and lack of concrete details make it nearly impossible for Claude to appropriately select this skill.
Suggestions
Add specific actions the skill performs, e.g., 'Saves, loads, and manages model checkpoints during training. Handles checkpoint versioning, automatic cleanup of old checkpoints, and training resumption.'
Include a 'Use when...' clause with natural trigger terms like 'save checkpoint', 'resume training', 'load model weights', 'checkpoint interval', '.ckpt files', '.pt files'
Remove the redundant duplicate trigger term and replace with varied natural language users would actually say when needing checkpoint management
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Model Checkpoint Manager') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of saving, loading, managing, versioning, or any specific checkpoint operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section just repeats the skill name rather than describing actual use cases or scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'model checkpoint manager' repeated twice, which is redundant and unlikely to match natural user language. Missing common variations like 'save checkpoint', 'load model', 'resume training', 'checkpoint files', '.ckpt', '.pt' files. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Model Checkpoint Manager' is somewhat specific to ML workflows and wouldn't conflict with general document or code skills. However, without specific actions described, it could overlap with other ML-related skills dealing with model files or training workflows. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is entirely placeholder boilerplate with no actual substance about model checkpoint management. It lacks any concrete code examples, specific commands, workflow steps, or actionable guidance. The content describes what a skill should do without actually doing it.
Suggestions
Add executable code examples for common checkpoint operations (saving checkpoints, loading checkpoints, resuming training) in PyTorch and TensorFlow
Define a clear workflow for checkpoint management including validation steps (e.g., verify checkpoint integrity, test loading before deleting old checkpoints)
Include specific configuration examples for checkpoint frequency, storage paths, and retention policies
Remove all generic boilerplate text and replace with concrete, actionable guidance that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about model checkpoint management. Every section describes what the skill does abstractly rather than providing concrete guidance Claude could use. | 1 / 3 |
Actionability | No concrete code, commands, or specific instructions are provided. The content only describes capabilities in vague terms like 'provides step-by-step guidance' without actually providing any guidance, code examples, or executable content. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, sequences, or validation checkpoints for checkpoint management tasks like saving, loading, resuming training, or managing checkpoint storage. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to detailed documentation, no links to examples, and no structured navigation to more specific information about checkpoint management. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Reviewed
Table of Contents
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.