Skip to content
TrustedSkillsbeta
Back to all skills

Chrome Extension Ui

Checked
pproenca·vlatest·backend·MIT

Automates Chrome extension UI interactions like clicks, form fills, and data extraction from web pages.

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 pproenca/dot-skills --skill chrome-extension-ui -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

pproenca

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 pproenca/dot-skills at cf93c57cac.

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

Commit
cf93c57cac
Manifest
skills/.experimental/chrome-extension-ui/SKILL.md
Scanned
47 files, 4,205 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 chrome-extension-ui skill enables AI agents to interact with and manipulate the user interface of Chrome browser extensions. It provides direct access to extension elements, allowing agents to read data, trigger actions, or modify states within specific extension contexts.

When to use it

  • Automating repetitive tasks inside popular browser extensions like password managers or ad blockers.
  • Extracting specific UI data from an extension without needing deep backend API knowledge.
  • Triggering extension-specific features programmatically through natural language commands.
  • Debugging or testing extension functionality by simulating user interactions via an AI agent.

Key capabilities

  • Access to Chrome extension DOM elements and event listeners.
  • Ability to execute scripts within the context of installed extensions.
  • Interaction with extension popup, sidebar, and background page UI components.
  • Retrieval of dynamic content rendered by extension interfaces.

Example prompts

  • "Open my password manager extension and find all saved entries for banking sites."
  • "Click the 'Block' button in the ad blocker extension for the current webpage."
  • "Read the latest notification from my task management extension sidebar."

Tips & gotchas

Ensure the target Chrome extension is installed and active on the domain where you are running the agent, as UI access is often restricted to specific contexts. Be aware that dynamic content may require the agent to wait for elements to render before attempting interaction.