Skip to content
TrustedSkillsbeta
Back to all skills

Ui Library Usage Auditor

Checked
hopeoverture·vlatest·frontend

Helps with UI components, libraries as part of agent workflows 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 hopeoverture/worldbuilding-app-skills --skill ui-library-usage-auditor -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

hopeoverture

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 hopeoverture/worldbuilding-app-skills at 1263b3fb00.

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

Commit
1263b3fb00
Manifest
skills/ui-components/ui-library-usage-auditor/SKILL.md
Scanned
4 files, 1,838 lines
Copies in repo
2 — all of them scanned
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 analyzes a codebase to identify instances where UI components are being used from a specified UI library. It can detect inconsistencies in component usage, such as deprecated components or incorrect styling approaches. The tool helps ensure adherence to the defined UI library standards and promotes code maintainability.

When to use it

  • Code Reviews: Integrate into automated code review processes to proactively identify UI library violations.
  • Refactoring Projects: Quickly assess the extent of usage for a particular UI component before refactoring or migrating to a new version.
  • Onboarding New Developers: Ensure new team members are using components correctly and consistently with established standards.
  • Maintaining Design Systems: Regularly audit codebases to verify adherence to evolving design system guidelines.

Key capabilities

  • UI library usage detection
  • Identification of deprecated components
  • Detection of inconsistent styling approaches
  • Codebase analysis

Example prompts

  • "Analyze this codebase for UI component usage from the 'Material UI' library."
  • "Find all instances where the 'Button' component is used outside of its approved context."
  • "Generate a report detailing inconsistencies in how the 'Input' component is styled across this project."

Tips & gotchas

The skill requires access to the codebase being analyzed. Ensure the UI library’s documentation or configuration file is provided for accurate detection and assessment.