spark-job-creator
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill spark-job-creatorSpark Job Creator - Auto-activating skill for Data Pipelines. Triggers on: spark job creator, spark job creator 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, essentially just restating the skill name without providing any meaningful information about capabilities or usage triggers. It lacks concrete actions, natural user keywords, and explicit guidance on when Claude should select this skill. The redundant trigger terms suggest this may be auto-generated boilerplate.
Suggestions
Add specific capabilities like 'Creates PySpark jobs, configures Spark clusters, generates data transformation scripts, optimizes job parameters'
Include a 'Use when...' clause with natural triggers: 'Use when the user mentions Spark, PySpark, distributed data processing, big data jobs, or needs to create ETL pipelines'
Add file type and technology keywords users would mention: '.py Spark scripts', 'DataFrame operations', 'RDD transformations', 'spark-submit'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Spark Job Creator' without describing any concrete actions. There are no specific capabilities listed like 'creates Spark jobs', 'configures executors', or 'generates PySpark scripts'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when to use' guidance. The 'Triggers on' field just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('spark job creator, spark job creator') and lack natural variations users would say like 'PySpark', 'Spark script', 'data processing job', 'ETL pipeline', or 'distributed computing'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'Spark' is somewhat specific to Apache Spark, the generic 'Data Pipelines' category and lack of detail could cause overlap with other data processing or ETL skills. The term 'job creator' is vague. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It contains only generic placeholder text that describes what a skill should do without providing any concrete guidance for creating Spark jobs. There is no code, no examples, no workflows, and no actionable information whatsoever.
Suggestions
Add executable PySpark code examples showing how to create a basic Spark job (SparkSession initialization, DataFrame operations, job submission)
Include a clear workflow with steps: 1) Configure SparkSession, 2) Define transformations, 3) Test locally, 4) Submit to cluster - with validation at each step
Provide concrete configuration examples (spark-submit commands, cluster configs, common job parameters)
Remove all generic boilerplate text and replace with specific, actionable guidance for Spark job creation patterns
| 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 actionable information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific steps for creating Spark jobs. The content only describes what the skill claims to do without actually providing any executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative structure with no references to detailed materials, no links to examples, and no organization beyond generic section headers that contain no useful 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.