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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill responsive-breakpoint-analyzerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that only states the skill name and category without explaining what the skill does or when to use it. It lacks any concrete actions, natural trigger terms users would say, and explicit usage guidance. The description would be nearly useless for Claude to distinguish this skill from others in a large skill library.
Suggestions
Add specific actions the skill performs, e.g., 'Analyzes CSS breakpoints, identifies responsive design issues, suggests optimal media query values, audits viewport coverage'
Include a 'Use when...' clause with natural trigger terms like 'Use when working with responsive design, media queries, mobile layouts, screen sizes, viewport issues, or CSS breakpoints'
Add file type triggers and common user phrases like '.css files', 'mobile-first', 'tablet view', '@media queries', 'responsive issues'
| 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 mention of analyzing, detecting, suggesting, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. There is no 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the skill name repeated twice ('responsive breakpoint analyzer'). Missing natural user terms like 'media queries', 'mobile', 'tablet', 'screen sizes', '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%This skill is essentially a placeholder template with no actual content about responsive breakpoint analysis. It contains only generic meta-descriptions of what a skill should do without any specific guidance, code examples, breakpoint values, CSS patterns, or actionable instructions for analyzing or implementing responsive breakpoints.
Suggestions
Add concrete breakpoint values and CSS examples (e.g., common breakpoints like 320px, 768px, 1024px, 1440px with media query syntax)
Include executable code showing how to analyze existing breakpoints in a codebase or implement a responsive breakpoint system
Provide a clear workflow for auditing breakpoints: identify current breakpoints → analyze usage patterns → recommend consolidation → implement changes
Replace generic capability descriptions with specific techniques like container queries, CSS custom properties for breakpoints, or tools for breakpoint visualization
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about responsive breakpoints. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or specific guidance is provided. The skill describes what it does in abstract terms but never shows how to actually 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 provides none. There's no sequence, no validation, and no actual process described. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no meaningful structure. It mentions 'Related Skills' but provides no actual references to detailed materials, examples, or documentation. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.