spark-sql-optimizer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill spark-sql-optimizerSpark Sql Optimizer - Auto-activating skill for Data Pipelines. Triggers on: spark sql optimizer, spark sql optimizer Part of the Data Pipelines skill category.
Overall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting only of a title, redundant trigger terms, and a category label. It provides no information about what the skill actually does or when it should be used, making it nearly impossible for Claude to make informed decisions about selecting this skill from a larger pool.
Suggestions
Add specific capabilities the skill provides, such as 'Analyzes Spark SQL execution plans, identifies performance bottlenecks, suggests query rewrites, and recommends partition strategies'
Add a 'Use when...' clause with natural trigger terms like 'Use when optimizing Spark SQL queries, troubleshooting slow jobs, analyzing execution plans, or improving query performance'
Include varied trigger terms users would naturally say: 'slow spark query', 'optimize SQL', 'query tuning', 'execution plan', 'spark performance', 'catalyst optimizer'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions - only the name 'Spark Sql Optimizer' and category 'Data Pipelines'. There are no specific capabilities listed like 'optimizes queries', 'analyzes execution plans', or 'rewrites inefficient joins'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no 'Use when...' clause or equivalent guidance for when Claude should select this skill. Both what and when are essentially missing. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'spark sql optimizer' repeated twice, which is redundant. Missing natural variations users would say like 'slow spark query', 'optimize SQL', 'query performance', 'execution plan', or 'spark tuning'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Spark SQL' provides some specificity that distinguishes it from generic data or SQL skills, but 'Data Pipelines' is broad and could overlap with ETL, data transformation, or other pipeline-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is essentially a placeholder template with no actual content about Spark SQL optimization. It contains only generic boilerplate describing what a skill should do without providing any concrete guidance, code examples, optimization techniques, or actionable instructions for working with Spark SQL.
Suggestions
Add concrete Spark SQL optimization examples with executable code (e.g., using EXPLAIN, partition pruning, broadcast joins, caching strategies)
Include specific optimization techniques with before/after query examples showing performance improvements
Define a clear workflow for analyzing and optimizing Spark SQL queries with validation steps (e.g., check execution plan, identify bottlenecks, apply optimization, verify improvement)
Remove all generic boilerplate text and replace with actual Spark SQL optimization content that Claude doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual Spark SQL optimization content. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no specific optimization techniques, no actual Spark SQL commands or configurations. The skill describes what it claims to do rather than providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for optimizing Spark SQL queries, no validation checkpoints, and no process to follow. The content is entirely meta-description without any actual procedure. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. There are no references to additional documentation, examples, or advanced topics - just empty claims about capabilities. | 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.