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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill model-export-helper31
Quality
0%
Does it follow best practices?
Impact
83%
1.00xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/08-ml-deployment/model-export-helper/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It only provides a skill name and category without explaining what the skill does, what specific capabilities it offers, or when it should be triggered. The repeated trigger term is the skill's own name, which provides no useful matching criteria.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Exports trained ML models to deployment formats (ONNX, TensorFlow SavedModel, TorchScript), optimizes models for inference, generates serving configurations.'
Add a 'Use when...' clause with natural trigger terms like 'export model', 'deploy model', 'convert to ONNX', 'production deployment', 'model serving', 'inference optimization'.
Include specific file formats, frameworks, or deployment targets to distinguish from other ML-related skills (e.g., 'PyTorch to ONNX', 'Kubernetes deployment', 'edge device export').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only 'Model Export Helper' which is a name, not an action. There's no indication of what the skill actually does (e.g., convert models, export to specific formats, optimize for deployment). | 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. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'model export helper' repeated twice, which is the skill's own name rather than natural keywords users would say. Missing terms like 'export model', 'ONNX', 'TensorFlow SavedModel', 'deploy model', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'ML Deployment' could overlap with many ML-related skills. Without specific actions or file formats mentioned, it would be impossible to distinguish from other ML deployment or model-related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a placeholder template with no actual content. It describes what a model export helper skill would do in abstract terms but provides zero actionable guidance, no code examples, no specific export formats (ONNX, TorchScript, SavedModel, etc.), and no workflows. The entire content could be replaced with actual model export instructions.
Suggestions
Add concrete code examples for common model export formats (e.g., PyTorch to ONNX, TensorFlow SavedModel, scikit-learn to ONNX)
Define a clear workflow with validation steps: export -> validate -> test inference -> deploy
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific export commands and configuration examples
Add a quick-start section with a minimal working example that can be copy-pasted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need and add no actionable value. | 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 guidance, examples, or executable instructions for model export. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The content only describes trigger conditions and vague capabilities without any actual process for model export. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no structure pointing to detailed materials. There are no references to external files, no organized sections with real content, and no navigation to deeper resources. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 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.