Generate spectrograms and feature-panel visualizations from audio with the songsee CLI.
86
83%
Does it follow best practices?
Impact
96%
19.20xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is concise and specific about its capabilities, naming concrete actions (spectrograms, feature-panel visualizations) and a specific tool (songsee CLI). Its main weakness is the absence of an explicit 'Use when...' clause and limited trigger term coverage for common user phrasings around audio analysis and visualization.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to visualize audio, generate spectrograms, or analyze audio features.'
Include additional natural trigger terms users might say, such as 'audio analysis', 'frequency visualization', 'mel spectrogram', 'audio features', or 'waveform visualization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Generate spectrograms and feature-panel visualizations from audio' and names the specific tool 'songsee CLI'. These are concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (generate spectrograms and feature-panel visualizations) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'spectrograms', 'audio', and 'songsee CLI', but misses common variations users might say such as 'audio analysis', 'frequency plot', 'waveform', 'mel spectrogram', or 'audio visualization'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche: spectrograms and audio feature visualizations using a specific CLI tool (songsee). Unlikely to conflict with other skills due to the specialized domain and named tool. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, concise skill that efficiently teaches CLI usage for the songsee tool. It provides concrete, executable examples covering all major use cases, with a clean structure that's easy to scan. The content respects Claude's intelligence and wastes no tokens on unnecessary explanation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides new, actionable information. No unnecessary explanations of what spectrograms are or how audio processing works—assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides concrete, copy-paste-ready CLI commands covering the main use cases (basic spectrogram, multi-panel, time slicing, stdin piping). Flag reference is specific with exact option names and valid values. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose CLI tool skill. Each example command is unambiguous and self-contained. No destructive or batch operations requiring validation checkpoints, so the clear single-action examples suffice. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (quick start, common flags, notes) that are easy to scan and navigate. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
e893157
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.