model-export-helper
Model Export Helper - Auto-activating skill for ML Deployment. Triggers on: model export helper, model export helper Part of the ML Deployment skill category.
Overall
score
20%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill model-export-helperActivation
0%This description is essentially a placeholder with no substantive content. It provides only a skill name and category without explaining what the skill does, what specific actions it performs, or when it should be selected. The trigger terms are redundant repetitions of the skill name rather than natural user language.
Suggestions
Add specific concrete actions the skill performs (e.g., 'Exports trained ML models to deployment formats including ONNX, TensorFlow SavedModel, and TorchScript')
Include a 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user needs to export, convert, or serialize machine learning models for production deployment')
Add relevant keywords and file formats users might mention (e.g., 'model serialization', '.onnx', '.pb', 'inference optimization', 'model conversion')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Model Export Helper' which is a name, not a capability. There's no indication of what the skill actually does (e.g., convert models, serialize weights, export to ONNX). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the vague category 'ML Deployment', and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'model export helper' repeated twice, which is the skill name itself rather than natural keywords users would say. Missing terms like 'export model', 'save model', 'ONNX', 'TensorFlow SavedModel', 'PyTorch export', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'ML Deployment' could overlap with many other ML-related skills. Without specific capabilities or file formats mentioned, it's impossible to distinguish from other model-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
7%This skill is a hollow template with no actual content about model export. It describes capabilities in abstract terms but provides zero concrete guidance, code examples, or workflows for exporting ML models. The skill would be completely unhelpful for anyone actually trying to export a model.
Suggestions
Add concrete code examples for common model export formats (ONNX, TorchScript, SavedModel, etc.) with executable snippets
Define a clear workflow with validation steps: export -> validate -> test inference -> deploy
Remove generic boilerplate sections ('Capabilities', 'Example Triggers') and replace with actual technical content
Include specific commands or API calls for popular frameworks (PyTorch, TensorFlow, scikit-learn)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no specific value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does abstractly ('provides step-by-step guidance') but never actually provides any actionable steps for model export. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for exporting models. No validation checkpoints or sequences are present. | 1 / 3 |
Progressive Disclosure | The content is organized into clear sections with headers, but there are no references to detailed documentation or examples. The structure exists but contains no substantive content to disclose. | 2 / 3 |
Total | 5 / 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
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.