window-function-generator
Window Function Generator - Auto-activating skill for Data Analytics. Triggers on: window function generator, window function generator Part of the Data Analytics skill category.
36
3%
Does it follow best practices?
Impact
97%
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/window-function-generator/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 extremely weak — it is essentially a title repeated with boilerplate category metadata. It lacks concrete actions, natural trigger terms users would say, and any explicit guidance on when to activate. It would be nearly indistinguishable from other data analytics skills in a multi-skill environment.
Suggestions
Add specific concrete actions such as 'Generates SQL window functions including ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD, running totals, and cumulative aggregations using OVER and PARTITION BY clauses.'
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about SQL window functions, ranking queries, running totals, partitioned aggregations, or OVER clauses.'
Include natural trigger terms users would say: 'window function', 'ROW_NUMBER', 'RANK', 'PARTITION BY', 'running total', 'cumulative sum', 'SQL analytics', 'OVER clause', 'LAG/LEAD'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names 'window function generator' but does not describe any concrete actions like generating SQL window functions, creating PARTITION BY clauses, or building ranking/aggregation queries. It is essentially just a label repeated. | 1 / 3 |
Completeness | The description fails to clearly answer 'what does this do' beyond the name itself, and there is no explicit 'Use when...' clause or equivalent guidance on when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger terms are 'window function generator' repeated twice. It misses natural user terms like 'ROW_NUMBER', 'RANK', 'PARTITION BY', 'running total', 'cumulative sum', 'SQL analytics', 'LAG', 'LEAD', or 'OVER clause'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'window function' is somewhat specific to SQL analytics, which provides some distinctiveness, but the vague 'Data Analytics' category and lack of concrete triggers could cause overlap with other SQL or analytics skills. | 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 with no substantive content. It contains zero actionable information about SQL window functions—no syntax examples, no patterns (ROW_NUMBER, RANK, LAG/LEAD, etc.), no partition/order clauses, and no executable code. Every section is generic boilerplate that could apply to any topic.
Suggestions
Add concrete, executable SQL examples for common window functions (ROW_NUMBER, RANK, DENSE_RANK, LAG, LEAD, SUM OVER, etc.) with realistic sample data and expected output.
Include a quick-reference section showing window function syntax: `function_name() OVER (PARTITION BY col ORDER BY col ROWS/RANGE ...)` with clear explanations of frame specifications.
Provide a decision guide or table mapping common analytics tasks (running totals, rankings, moving averages, gap detection) to the appropriate window function pattern.
Remove all generic boilerplate ('This skill activates automatically when...', 'Provides step-by-step guidance...') and replace with actual technical content that Claude doesn't already know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'window function generator' excessively, and provides zero actual technical content about SQL window functions. | 1 / 3 |
Actionability | There is no concrete guidance whatsoever—no SQL examples, no window function syntax, no executable code, no specific commands. The skill describes what it could do rather than instructing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill merely lists vague capabilities like 'provides step-by-step guidance' without actually providing any steps or validation checkpoints. | 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
4dee593
- 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.