Skip to content
TrustedSkillsbeta
Back to all skills

Component Usage Analytics

Checked
flight505·vlatest·frontend·MIT

Helps with components, analytics as part of data analysis and analytics workflows workflows.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it Component Usage Analytics, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add flight505/storybook-assistant --skill "Component Usage Analytics" -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

flight505

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 flight505/storybook-assistant at 815e6169a7.

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

Commit
815e6169a7
Manifest
skills/component-usage-analytics/SKILL.md
Scanned
1 file, 524 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 analyzes component usage within a Storybook environment. It identifies which components are being used, how frequently they’re utilized, and provides insights into their overall adoption rate. This data helps developers understand the effectiveness of UI libraries and identify areas for optimization or potential deprecation.

When to use it

  • Evaluating new UI component libraries: Determine if a new library is widely adopted by your team before committing resources.
  • Identifying unused components: Discover components that are no longer in use, allowing you to remove them and reduce codebase complexity.
  • Measuring the impact of UI changes: Track how modifications to components affect their usage patterns.
  • Optimizing Storybook setup: Understand which stories are most valuable based on component interaction data.

Key capabilities

  • Component Usage Tracking
  • Adoption Rate Analysis
  • Story Interaction Metrics
  • UI Library Evaluation

Example prompts

  • "Show me the top 5 most used components in my Storybook."
  • "Which components have not been used in the last month?"
  • "Analyze component usage since the latest UI library update."

Tips & gotchas

This skill requires a Storybook environment to be running and properly configured. The accuracy of the data depends on the correct instrumentation within your Storybook setup.