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.
35
Quality
3%
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
7%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 severely underdeveloped, functioning more as a label than a useful skill description. It provides no concrete actions, no natural trigger terms users would actually say, and no guidance on when Claude should select this skill. The repeated trigger term and boilerplate category mention suggest auto-generated content without meaningful customization.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Calculates duration between dates, identifies overlapping periods, validates date ranges, and compares time intervals.'
Include a 'Use when...' clause with natural trigger terms like 'Use when the user asks about date calculations, time period comparisons, duration analysis, or mentions terms like date range, time span, or period overlap.'
Remove the redundant duplicate trigger term and expand with varied natural language users would actually use, such as 'date math', 'time between dates', 'period analysis', or 'calendar calculations'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Date Range Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of analyzing, calculating, comparing, or any specific operations on date ranges. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. It only provides a category label ('Data Analytics') without explaining capabilities or explicit trigger conditions. | 1 / 3 |
Trigger Term Quality | The trigger terms listed are just 'date range analyzer' repeated twice, which is unlikely to match natural user language. Users would more likely say 'analyze dates', 'compare time periods', 'date calculations', or 'time range analysis'. | 1 / 3 |
Distinctiveness Conflict Risk | While 'date range' provides some specificity within the data analytics domain, the lack of concrete actions means it could overlap with other time-series, calendar, or general analytics skills. The category mention helps slightly but is insufficient. | 2 / 3 |
Total | 5 / 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 that provides no actual value. It contains only placeholder text and meta-descriptions about what a skill should do, without any concrete guidance on date range analysis, SQL queries, or data analytics techniques. The content would need to be completely rewritten with actual technical substance.
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 a clear workflow for analyzing date ranges: identify date columns, validate formats, apply filters, aggregate results
Replace all placeholder text with actual technical guidance - every section currently describes what it 'should' do rather than doing it
| 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 is provided. The content only describes what the skill claims to do in vague terms like 'provides step-by-step guidance' without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains zero actual steps for analyzing date ranges. | 1 / 3 |
Progressive Disclosure | The content is a flat template with no meaningful structure. There are no references to detailed materials, examples, or related documentation that would help with date range analysis. | 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
0c08951
- 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.