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 critically weak across all dimensions. It reads like an auto-generated stub with no substantive content—it fails to describe what the skill does, provides no natural trigger terms, and lacks any 'Use when...' guidance. The repeated trigger term 'date range analyzer' adds no value.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Analyzes date ranges in datasets, calculates durations, filters records by time periods, and identifies trends across date intervals.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks about date ranges, time periods, filtering by dates, date comparisons, duration calculations, or temporal analysis.'
Remove the redundant duplicate trigger term and replace with diverse natural keywords users would actually say, such as 'date filter', 'time range', 'between dates', 'date span', 'temporal data'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description says 'Date Range Analyzer' and mentions 'Data Analytics' but provides no concrete actions. There is no indication of what the skill actually does—no verbs describing capabilities like 'analyzes', 'computes', 'filters', etc. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explanation of capabilities and no explicit 'Use when...' clause—only a redundant trigger phrase. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'date range analyzer' repeated twice, which is not a natural phrase users would say. Missing common variations like 'date range', 'date filter', 'time period', 'between dates', 'date analysis', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is extremely generic—'Data Analytics' could overlap with many other skills. Without specific actions or clear scope, it would be nearly impossible to distinguish this from other analytics-related skills. | 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 repeatedly references 'date range analyzer' without ever defining what it does, how to do it, or providing any executable code, SQL queries, or concrete guidance. It fails on every dimension as it contains only boilerplate meta-descriptions rather than actionable instructions.
Suggestions
Add concrete SQL examples for common date range analysis patterns (e.g., filtering by date ranges, calculating rolling averages, comparing periods)
Include executable code snippets for date range operations in SQL and/or Python with specific input/output examples
Define a clear workflow for date range analysis tasks, such as: 1) Identify date columns, 2) Determine range boundaries, 3) Write query, 4) Validate results
Remove all boilerplate sections (When to Use, Example Triggers, Capabilities) and replace with actual technical content that teaches Claude something it doesn't already know
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'date range analyzer' excessively, and provides zero actual technical content or instructions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no code, no commands, no SQL examples, no specific steps for analyzing date ranges. Every section is vague and abstract. | 1 / 3 |
Workflow Clarity | No workflow is defined. The skill claims to provide 'step-by-step guidance' but contains zero steps. There are no sequences, validation checkpoints, or processes described. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no structured sections with real content, and no navigation to supporting files. | 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
c8a915c
- 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.