responsive-breakpoint-analyzer
Responsive Breakpoint Analyzer - Auto-activating skill for Frontend Development. Triggers on: responsive breakpoint analyzer, responsive breakpoint analyzer Part of the Frontend Development skill category.
34
Quality
3%
Does it follow best practices?
Impact
90%
1.03xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/responsive-breakpoint-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 essentially a placeholder with no substantive content. It only provides the skill name, a duplicate trigger term, and a category label without explaining what the skill does or when to use it. Claude would have no meaningful information to decide when to select this skill over others.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Analyzes CSS breakpoints, identifies responsive design issues, suggests optimal media query values, audits viewport configurations'
Add a 'Use when...' clause with natural trigger terms like 'Use when working with media queries, responsive layouts, mobile-first design, screen size issues, or CSS @media rules'
Include file type triggers and common user phrases like '.css files', 'breakpoint', 'viewport', 'mobile view', 'tablet layout', 'screen width'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Responsive Breakpoint Analyzer') without describing any concrete actions. There are no verbs indicating what the skill actually does - no 'analyzes', 'identifies', 'generates', or similar action words. | 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 'Use when...' clause or equivalent guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are just the skill name repeated twice ('responsive breakpoint analyzer, responsive breakpoint analyzer'). Missing natural user terms like 'media queries', 'screen sizes', 'mobile layout', 'viewport', 'CSS breakpoints', or '@media'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'Responsive Breakpoint Analyzer' is somewhat specific to a niche (CSS responsive design), but without concrete actions or triggers, it could overlap with general CSS or frontend skills. The category mention 'Frontend Development' is too broad. | 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 entirely meta-content describing what a skill would do rather than providing any actual guidance on responsive breakpoint analysis. It contains zero actionable information about breakpoints, media queries, CSS techniques, or analysis methods. The content is a template placeholder that fails every dimension of the rubric.
Suggestions
Add concrete breakpoint values and media query examples (e.g., common breakpoints like 320px, 768px, 1024px, 1440px with CSS code)
Include executable code showing how to analyze existing breakpoints in a codebase or implement responsive patterns
Provide a clear workflow for auditing breakpoints: identify current breakpoints → analyze usage → recommend consolidation → implement changes
Replace all meta-description text ('This skill provides...', 'Capabilities include...') with actual technical content about responsive design
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about responsive breakpoints. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it claims to do but never actually shows how to analyze breakpoints, what breakpoint values to use, or any executable examples. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The 'Capabilities' section mentions 'step-by-step guidance' but none is actually provided. There are no validation checkpoints or sequences for analyzing responsive breakpoints. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no actual technical content to organize. There are no references to detailed materials, examples, or related documentation that would help with responsive breakpoint 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
994edc4
- 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.