Skip to content
TrustedSkillsbeta
Back to all skills

Responsiveness Check

Checked
jezweb·vlatest·frontend·MIT

This skill analyzes text for immediate clarity and conciseness, ensuring responses are effective and avoid unnecessary verbosity.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jezweb/claude-skills --skill responsiveness-check -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jezweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jezweb/claude-skills at 1260fa7439.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1260fa7439
Manifest
plugins/dev-tools/skills/responsiveness-check/SKILL.md
Scanned
3 files, 317 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The responsiveness-check skill allows AI agents to programmatically verify how web pages render across different screen sizes and devices. It executes automated tests to ensure layouts remain functional and visually correct on mobile, tablet, and desktop interfaces.

When to use it

  • Validate new responsive design implementations before deploying to production environments.
  • Audit existing websites for broken layouts or overlapping elements on specific device widths.
  • Integrate into CI/CD pipelines to automatically flag regression issues in UI rendering.
  • Test complex grid systems or flexbox arrangements that may behave unexpectedly on smaller screens.

Key capabilities

  • Simulates multiple viewport sizes and device types during testing.
  • Detects layout shifts, overflow errors, and broken navigation elements.
  • Provides detailed reports on which specific breakpoints fail validation.
  • Supports custom configuration for testing particular devices or resolutions.

Example prompts

"Run a responsiveness check on my homepage to identify any mobile layout issues." "Test the checkout page across tablet viewports and report any overlapping text blocks." "Automate a full responsive audit of all pages in my documentation site before the next release."

Tips & gotchas

Ensure your website is fully loaded and stable before running responsiveness checks to avoid false positives from loading states. For best results, combine this skill with visual regression testing tools to catch subtle design inconsistencies that automated metrics might miss.