compression-optimizer
Compression Optimizer - Auto-activating skill for Data Pipelines. Triggers on: compression optimizer, compression optimizer Part of the Data Pipelines skill category.
31
0%
Does it follow best practices?
Impact
85%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/11-data-pipelines/compression-optimizer/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 is an extremely weak description that essentially only restates the skill's name and category without providing any substantive information. It lacks concrete actions, meaningful trigger terms, explicit 'when to use' guidance, and any distinguishing details that would help Claude select it appropriately from a pool of skills.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Configures and optimizes compression algorithms (gzip, snappy, zstd, lz4) for data pipeline stages, tunes compression levels, and benchmarks throughput vs. compression ratio tradeoffs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about compressing data in pipelines, reducing data transfer size, choosing compression codecs, or optimizing storage in ETL/ELT workflows.'
Replace the duplicate trigger term 'compression optimizer, compression optimizer' with varied natural language terms users would actually say, such as 'compress data', 'reduce file size', 'compression ratio', 'gzip', 'snappy', 'pipeline storage optimization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description provides no concrete actions whatsoever. 'Compression Optimizer' is a label, not a description of capabilities. There is no mention of what specific actions this skill performs (e.g., compress files, optimize compression ratios, select algorithms). | 1 / 3 |
Completeness | Neither the 'what' nor the 'when' is meaningfully answered. The description states it's for 'Data Pipelines' but doesn't explain what it does or when Claude should select it beyond the skill's own name as a trigger. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'compression optimizer' repeated twice. These are not natural terms users would say — users are more likely to say 'compress data', 'reduce file size', 'gzip', 'optimize pipeline throughput', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive. 'Compression Optimizer' for 'Data Pipelines' could overlap with any skill related to data processing, file compression, storage optimization, or pipeline performance tuning. | 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 is a placeholder/template skill with no actual content. It contains only generic boilerplate that repeats the phrase 'compression optimizer' without providing any actionable information about compression algorithms, codec selection, pipeline integration, benchmarking, or configuration. It would provide zero value to Claude when handling compression optimization tasks.
Suggestions
Add concrete, executable code examples showing compression optimization (e.g., comparing gzip/snappy/zstd in Spark pipelines with benchmarks and configuration snippets)
Include a decision matrix or workflow for choosing compression codecs based on use case (e.g., columnar storage vs streaming, read-heavy vs write-heavy)
Provide specific configuration examples for common tools (Spark, Kafka, Parquet, Airflow) with compression settings and validation steps
Remove all boilerplate sections (Purpose, When to Use, Example Triggers) and replace with actionable technical content that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler with no substantive information. It explains what the skill does in abstract terms without providing any actual compression optimization knowledge, techniques, or code. Every section restates the same vague concept. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific algorithms, no configuration examples, no compression format comparisons. The content only describes what it would do rather than actually doing it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or any sequenced instructions. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive structure with no references to detailed materials, no links to related files, and no meaningful organization beyond boilerplate headings that all say the same thing. | 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 | |
- Commit
c8a915c
- 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.