compression-optimizer
Compression Optimizer - Auto-activating skill for Data Pipelines. Triggers on: compression optimizer, compression optimizer Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill compression-optimizerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting primarily of auto-generated boilerplate with the skill name repeated as trigger terms. It provides no information about actual capabilities, supported compression formats, or concrete use cases. Claude would have no meaningful basis to select this skill appropriately.
Suggestions
Add specific actions the skill performs (e.g., 'Selects optimal compression algorithms, compresses data streams, configures gzip/zstd/lz4 settings for pipeline throughput').
Include natural trigger terms users would say: 'compress', 'compression ratio', 'reduce data size', 'gzip', 'streaming compression', 'pipeline optimization'.
Add an explicit 'Use when...' clause describing scenarios: 'Use when optimizing data pipeline throughput, selecting compression algorithms, or when users mention compressing data streams or reducing storage costs.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Compression Optimizer' and category 'Data Pipelines'. There is no explanation of what the skill actually does (e.g., compress files, optimize compression ratios, select algorithms). | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just the skill name repeated. There is no explicit trigger guidance or use case explanation. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'compression optimizer' repeated twice, which is the skill's own name rather than natural user language. Missing common terms users would say like 'compress', 'zip', 'reduce file size', 'gzip', 'data compression'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'compression optimizer' is somewhat specific, the lack of detail about what kind of compression (file, data stream, algorithm selection) and the vague 'Data Pipelines' category could cause overlap with other data processing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely placeholder content with no actual substance. It describes what a compression optimizer skill should do without providing any actual compression optimization guidance, code, algorithms, or techniques. The content is 100% meta-description and 0% actionable instruction.
Suggestions
Add concrete code examples for common compression scenarios (e.g., choosing between gzip/snappy/zstd for different data types, configuring Spark compression codecs)
Include a decision matrix or workflow for selecting compression algorithms based on data characteristics (text vs binary, read-heavy vs write-heavy, storage vs network optimization)
Provide specific commands and configurations for compression in common data pipeline tools (Airflow, Spark, Kafka)
Add validation steps showing how to measure compression ratios and performance tradeoffs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about compression optimization. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific techniques, no algorithms. The skill describes what it claims to do rather than actually instructing how to optimize compression. | 1 / 3 |
Workflow Clarity | No workflow is defined. The content mentions 'step-by-step guidance' but provides none. There are no steps, no validation checkpoints, and no actual process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague marketing-style text with no structure pointing to detailed materials, no references to implementation guides, and no organized navigation to actual compression techniques. | 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.