time-series-decomposer
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill time-series-decomposerTime Series Decomposer - Auto-activating skill for Data Analytics. Triggers on: time series decomposer, time series decomposer Part of the Data Analytics 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 explaining what it actually does or when to use it. It lacks concrete actions, natural trigger terms, and explicit usage guidance. The only slight positive is that 'time series decomposer' is a somewhat specific domain term.
Suggestions
Add specific capabilities like 'Decomposes time series data into trend, seasonal, and residual components using STL or classical decomposition methods'
Include a 'Use when...' clause with natural triggers such as 'Use when analyzing seasonal patterns, extracting trends from temporal data, or when user mentions decomposition, seasonality, or time series components'
Add common user terms and file types: 'time series analysis', 'seasonal adjustment', 'trend analysis', 'cyclical patterns', 'temporal data', '.csv with dates'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Time Series Decomposer') without describing any concrete actions. There are no specific capabilities listed like 'decompose trends', 'extract seasonality', or 'identify cyclical patterns'. | 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. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('time series decomposer, time series decomposer'). Missing natural user terms like 'seasonal analysis', 'trend extraction', 'decomposition', 'STL', or 'forecast components'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'time series decomposer' is fairly specific to a niche domain, which provides some distinctiveness. However, without clear capability descriptions, it could overlap with general time series or forecasting skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual substance about time series decomposition. It contains no executable code, no specific techniques (STL, classical decomposition, X-11), no examples, and no actionable guidance. The entire content could apply to virtually any skill by swapping the name.
Suggestions
Add executable Python code examples using statsmodels.tsa.seasonal_decompose() or STL decomposition with actual data
Include specific workflow steps: 1) Check stationarity, 2) Choose decomposition method (additive vs multiplicative), 3) Extract components, 4) Validate residuals
Provide concrete examples showing input time series data and expected decomposed output (trend, seasonal, residual components)
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with actual technical content about decomposition methods and when to use each
| 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 information about time series decomposition. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no commands, no specific methods (STL, seasonal decomposition, etc.), no examples of actual decomposition. The content describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. Time series decomposition involves specific steps (trend extraction, seasonality identification, residual analysis) but none are mentioned or sequenced. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no structure pointing to detailed materials. References to 'Related Skills' and tags provide no actual navigation to 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.