pyspark-transformer
Pyspark Transformer - Auto-activating skill for Data Pipelines. Triggers on: pyspark transformer, pyspark transformer Part of the Data Pipelines skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill pyspark-transformerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, essentially serving as a placeholder rather than a functional skill description. It provides no information about what the skill actually does, what PySpark operations it supports, or when Claude should select it. The duplicate trigger term suggests incomplete or rushed authoring.
Suggestions
Add specific capabilities: list concrete PySpark operations like 'Transform DataFrames, apply filters, joins, aggregations, and window functions in PySpark pipelines'
Add a 'Use when...' clause with natural trigger terms: 'Use when the user mentions PySpark, Spark DataFrames, data transformation, ETL pipelines, or .py files with spark operations'
Include common user phrases and file types: 'spark code', 'dataframe operations', 'big data processing', '.parquet files', 'distributed data'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names 'Pyspark Transformer' without describing any concrete actions. There are no verbs or specific capabilities listed - it doesn't explain what transformations, operations, or tasks this skill performs. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond naming itself, and provides no 'when should Claude use it' guidance. The 'Triggers on' section just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'pyspark transformer' repeated twice. Missing natural variations users might say like 'spark dataframe', 'data transformation', 'ETL', 'pipeline processing', or 'PySpark code'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'PySpark' is a specific technology, the term 'transformer' is ambiguous (could mean ML transformers, data transformers, etc.). The 'Data Pipelines' category provides some context but the description lacks enough detail to clearly distinguish from other data processing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is a placeholder template with no actual content. It contains only generic boilerplate describing what a skill should do without providing any PySpark-specific guidance, code examples, or actionable instructions. The content would be identical if you replaced 'pyspark transformer' with any other technology term.
Suggestions
Add executable PySpark transformer code examples showing common patterns (e.g., DataFrame transformations, UDFs, window functions)
Include specific guidance on PySpark transformer best practices such as partition strategies, broadcast joins, and memory optimization
Provide a concrete workflow for building and testing PySpark transformations with validation steps
Replace generic capability descriptions with actual technical content - show don't tell
| 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 zero actionable information. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance whatsoever. The entire skill describes what it does in abstract terms without providing any actual PySpark transformer examples, syntax, or executable instructions. | 1 / 3 |
Workflow Clarity | No workflow is defined. Claims to provide 'step-by-step guidance' but contains zero actual steps. No validation checkpoints, no sequence of operations, nothing actionable for data transformation tasks. | 1 / 3 |
Progressive Disclosure | No structure beyond generic headings. No references to detailed documentation, no links to examples or API references. The 'Related Skills' section mentions a category but provides no navigation to actual 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.