date-range-analyzer
Date Range Analyzer - Auto-activating skill for Data Analytics. Triggers on: date range analyzer, date range analyzer Part of the Data Analytics skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill date-range-analyzerOverall
score
17%
Does it follow best practices?
Validation for skill structure
Activation
0%This description is severely underdeveloped and fails on all dimensions. It reads like auto-generated boilerplate with no actual content describing what the skill does or when to use it. The repeated trigger term and lack of any concrete capabilities make it nearly useless for skill selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Parses date ranges, calculates durations between dates, identifies overlapping periods, and validates date formats'
Include a 'Use when...' clause with natural trigger terms like 'date range', 'time period', 'between dates', 'start and end date', 'date interval', 'calendar range'
Describe the specific use cases that distinguish this from general analytics skills, e.g., 'Use when analyzing temporal data, filtering by date ranges, or comparing time-based metrics'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Date Range Analyzer') without describing any concrete actions. There are no specific capabilities listed like 'parse dates', 'calculate intervals', or 'compare time periods'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only states the category ('Data Analytics') without explaining functionality or providing explicit usage triggers. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just the skill name repeated twice ('date range analyzer, date range analyzer'). No natural user keywords like 'dates', 'time period', 'between dates', 'date comparison', or 'calendar range' are included. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic - 'Data Analytics skill category' could overlap with dozens of other analytics skills. There's nothing distinguishing this from other date-related or analytics skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%This skill is an empty template with no actual content. It describes meta-information about what a date range analyzer skill should do but provides zero concrete guidance, code examples, SQL queries, or actionable instructions for analyzing date ranges. The entire content is self-referential boilerplate.
Suggestions
Add concrete SQL examples for common date range queries (e.g., filtering by date, calculating date differences, grouping by time periods)
Include specific code snippets for date range analysis in relevant languages/tools (SQL, Python pandas, etc.)
Define what 'date range analyzer' actually means and provide step-by-step workflows for common use cases like comparing periods, identifying trends, or handling timezone issues
Remove the meta-description sections ('When to Use', 'Example Triggers') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely boilerplate with no actual technical substance. It repeats 'date range analyzer' multiple times without providing any concrete information about what it does or how to use it. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The content only describes what the skill claims to do ('provides step-by-step guidance', 'generates production-ready code') without actually providing any of it. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for analyzing date ranges. | 1 / 3 |
Progressive Disclosure | No meaningful structure or references to additional resources. The sections are organizational headers with no substantive content beneath them. | 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.