tensorboard-visualizer
Tensorboard Visualizer - Auto-activating skill for ML Training. Triggers on: tensorboard visualizer, tensorboard visualizer Part of the ML Training skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill tensorboard-visualizerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, functioning more as a label than a useful skill description. It lacks any concrete actions, meaningful trigger terms, or guidance on when to use the skill. The repeated trigger term and absence of capability details would make it difficult for Claude to appropriately select this skill from a larger skill set.
Suggestions
Add specific actions the skill performs, e.g., 'Launches TensorBoard to visualize training metrics, loss curves, model graphs, and embedding projections.'
Include a 'Use when...' clause with natural trigger terms like 'visualize training', 'see loss curves', 'training metrics', 'model performance graphs', 'TensorBoard', 'training progress'.
Add file/context triggers such as 'when working with TensorFlow/PyTorch training logs', 'event files', or 'runs directories'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the tool ('Tensorboard Visualizer') and category ('ML Training') but provides no concrete actions. It doesn't describe what the skill actually does - no verbs like 'visualize', 'plot', 'analyze', or specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' (no actions described) and 'when should Claude use it' (no explicit use-when clause). The trigger terms are just the skill name repeated, not meaningful guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'tensorboard visualizer' repeated twice. Missing natural variations users would say like 'training metrics', 'loss curves', 'training logs', 'visualize training', 'tensorboard', or 'TensorBoard'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Tensorboard' provides some specificity to a particular tool, which helps distinguish it from generic ML skills. However, the vague 'ML Training' category could overlap with other training-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder with no actionable content. It describes what a TensorBoard visualizer skill would do but provides zero actual guidance, code examples, or specific instructions. The entire content could be replaced with a single sentence and would convey the same (lack of) information.
Suggestions
Add executable Python code showing how to launch TensorBoard and log basic metrics (e.g., `from torch.utils.tensorboard import SummaryWriter`)
Include specific examples of logging scalars, histograms, images, and graphs with actual code snippets
Provide a clear workflow: 1) Set up logging directory, 2) Initialize writer, 3) Log metrics during training, 4) Launch TensorBoard server, 5) Navigate the UI
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with concrete, actionable content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about TensorBoard. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude already understands. | 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 using TensorBoard. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The content only describes trigger conditions and vague capabilities without any actual sequence of actions for visualizing data in TensorBoard. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed documentation, examples, or related files. There's nothing to disclose progressively because there's no substantive content. | 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
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.