Skip to content
TrustedSkillsbeta
Back to all skills

Extension Anti Patterns

Checked
arustydev·vlatest·backend·AGPL-3.0

Identifies and suggests fixes for common code extension pitfalls like tight coupling and feature bloat.

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 arustydev/agents --skill extension-anti-patterns -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

arustydev

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 arustydev/ai at 70b280c5bc.

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

Commit
70b280c5bc
Manifest
content/plugins/web/browser-extension-dev/skills/extension-anti-patterns/SKILL.md
Scanned
1 file, 389 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 helps identify and avoid common pitfalls when developing browser extensions. It analyzes code or descriptions of extension functionality to highlight potential anti-patterns related to security, performance, or user experience. The goal is to improve the quality and maintainability of browser extensions by proactively addressing these issues.

When to use it

  • During Extension Development: Before committing code, use this skill to review your work for common extension design flaws.
  • Code Reviews: Integrate this into code review processes to ensure new features don't introduce anti-patterns.
  • Refactoring Existing Extensions: Identify areas in older extensions that could benefit from improved architecture and reduced risk.
  • Learning Extension Development: New developers can use it to understand best practices and avoid common mistakes.

Key capabilities

  • Identifies potential security vulnerabilities in extension code.
  • Flags performance bottlenecks related to extension functionality.
  • Highlights usability issues stemming from poor design choices in extensions.
  • Provides suggestions for alternative approaches to achieve desired functionality.

Example prompts

  • "Analyze this extension manifest and background script for anti-patterns."
  • "I'm building a browser extension that [brief description of functionality]. Are there any potential pitfalls I should be aware of?"
  • "Review the following code snippet for common security vulnerabilities in browser extensions: [code snippet]"

Tips & gotchas

This skill is most effective when provided with specific code or detailed descriptions of extension behavior. It's not a substitute for thorough testing and manual review, but can act as an early warning system for potential problems.