Skip to content
TrustedSkillsbeta
Back to all skills

Ui Testing

Checked
alinaqi·vlatest·frontend·MIT

Helps with UI components, testing as part of testing, debugging, and quality assurance workflows.

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 alinaqi/maggy --skill ui-testing -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

alinaqi

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 alinaqi/claude-bootstrap at 72a456e6cc.

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

Commit
72a456e6cc
Manifest
skills/ui-testing/SKILL.md
Scanned
1 file, 165 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

What it does

This skill, "Ui Testing," helps AI agents quickly verify that generated UI components meet accessibility standards. It provides a checklist and guidance for ensuring visual elements are clear, usable, and compliant with common web accessibility guidelines. The tool focuses on aspects like button visibility, color contrast, touch target size, state indicators (hover, pressed, focus, disabled, loading), and responsiveness across different screen sizes.

When to use it

  • After creating new UI components to ensure they meet basic accessibility requirements.
  • Before releasing any UI changes to catch potential issues early in the development process.
  • When debugging visual inconsistencies or usability problems with existing UI elements.
  • To verify dark mode compatibility, ensuring readability and visibility of key elements.
  • During responsive design checks to confirm content remains readable at various breakpoints.

Key capabilities

  • Visibility Check: Ensures buttons have visible backgrounds or borders, and text has sufficient contrast against its background.
  • Touch/Click Targets: Verifies adequate size (minimum 44px height for buttons, 44x44px for icons) and spacing between clickable elements.
  • States Verification: Checks for visibility of hover, pressed, focus, disabled, and loading states.
  • Dark Mode Compliance: Validates text readability, border visibility, and avoidance of problematic color combinations in dark mode.
  • Responsive Design Check: Ensures no horizontal scrolling on mobile devices (320px width) and content remains readable across different screen sizes.

Example prompts

  • "Run a UI accessibility check on this component."
  • "Verify the contrast ratio for this button's text color."
  • "Check if this element has a visible focus ring."
  • "Is this touch target large enough?"

Tips & gotchas

  • This skill requires loading either ui-web.md or ui-mobile.md to function correctly.
  • The tool relies on visual inspection and may require manual review of results alongside automated checks using browser developer tools or online contrast checkers.
  • Pay close attention to Tailwind CSS color combinations, as some shades (like gray-400 and gray-500) can easily lead to accessibility issues.