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.
33
0%
Does it follow best practices?
Impact
95%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/12-data-analytics/date-range-analyzer/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be nearly impossible for Claude to correctly choose this skill from a pool of alternatives.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Analyzes data across date ranges, compares time periods, identifies trends, and filters datasets by start/end dates.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to filter data by dates, compare time periods, analyze trends over time, or work with date ranges in datasets.'
Include natural keyword variations users would actually say, such as 'date filter', 'time period', 'between dates', 'date comparison', 'temporal analysis', 'start date', 'end date'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Data Analytics') and a tool name ('Date Range Analyzer') but provides no concrete actions. There is no indication of what the skill actually does—no verbs like 'analyze', 'filter', 'compare', or 'aggregate' are present. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' clause is limited to a redundant trigger phrase. There is no explicit 'Use when...' guidance or meaningful explanation of functionality. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'date range analyzer' repeated twice. These are not natural phrases users would say; users are more likely to say things like 'filter by date', 'date range', 'between dates', 'time period analysis', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Data Analytics' could overlap with countless other skills, and 'date range analyzer' without specifics about what it analyzes or produces makes it indistinguishable from any date-related analytics skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It contains only generic boilerplate descriptions that could apply to any skill topic, with no actual guidance on date range analysis, no SQL examples, no code, and no concrete techniques. It provides zero value beyond what the skill's title alone conveys.
Suggestions
Add concrete, executable SQL examples for common date range patterns (e.g., rolling windows, YoY comparisons, fiscal quarters, date binning) that Claude can directly use.
Include a clear workflow for date range analysis tasks: identify date columns → determine granularity → write query → validate results with sample output.
Remove all generic boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content like a quick-reference table of date functions across SQL dialects.
Add specific examples with input/output pairs showing how to analyze date ranges for common business intelligence scenarios (e.g., cohort analysis, seasonality detection).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no domain-specific information about date range analysis, and every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no SQL queries, no code examples, no specific commands, no date range patterns, no functions. The skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or sequence of any kind is provided. There are no validation checkpoints, no process to follow, and no actionable procedure for analyzing date ranges. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no separation of overview from detail. There are no bundle files to reference either. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.