mcp devtools

    1

    Audit frontend accessibility, analyze JS bundle sizes, document React props, and run Lighthouse performance reports.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    mcp devtools

    Example session with this skill installed

    Analyze my React bundle using the stats.json file in the build directory. Check for duplicate packages and large modules.

    • Read your context and instructions
    • Compiled the mcp devtools

    I have analyzed the stats.json file in your build directory. The analysis identified two critical duplicate packages and three modules contributing to over 40% of the total bundle size.

    Bundle Analysis Report

    Duplicate Packages

    PackageVersions FoundEstimated ImpactSuggested Action
    lodash4.17.15, 4.17.2172KBRun npm dedupe or update root dependencies.
    date-fns2.28.0, 2.29.345KBAlign versions in package.json.

    Top Bundle Contributors

    Module PathSize (Gzipped)% of TotalRecommendation
    ./node_modules/chart.js154KB18.2%Use dynamic imports (React.lazy).
    ./node_modules/moment98KB11.5%Replace with dayjs or date-fns.
    ./src/components/HeavyDataGrid85KB10.1%Code-split at the route level.

    Next steps

    1. Run npm dedupe to resolve the minor version mismatch in lodash.
    2. Implement dynamic imports for the HeavyDataGrid component to reduce initial load time.
    3. Review package.json to lock date-fns to a single version across all workspaces.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Frontend performance and quality issues often remain hidden until they impact users. This skill provides a focused toolkit to audit accessibility, analyze JavaScript bundle bloat, document React component APIs, and run Lighthouse performance reports.

    What it does

    • Audit accessibility identifies WCAG 2.1 AA violations across entire pages or specific selectors.
    • Analyze bundle size identifies large modules and duplicate packages causing bundle bloat.
    • Document components scans React directories to generate prop tables with types and requirements.
    • Run Lighthouse reports measures Core Web Vitals, SEO, and performance opportunities.

    How it works

    1. Identify the goal by selecting the specific tool needed for accessibility, bundles, documentation, or performance.
    2. Execute the audit using commands like audit_accessibility, analyze_bundle, or scan_components.
    3. Review the analysis to see high-level summaries and tool-specific evidence.
    4. Implement remediation following the generated actionable steps and fix instructions.

    Frameworks & tools

    Works with React, TypeScript, Webpack, and Vite. Specifically requires stats.json for bundle analysis and tsconfig.json for component documentation.

    Why this beats prompting it yourself

    Generic LLMs cannot inspect your actual build artifacts or live DOM structure. This skill integrates directly with specific MCP tools to extract real data from your bundles and source code, providing evidence-based fixes instead of guesses.

    Use cases

    • Reduce bundle size by finding and removing duplicate package versions in your build.
    • Fix accessibility by identifying specific elements missing ARIA labels or proper contrast.
    • Automate documentation by generating prop tables for a shared UI library.
    • Optimize Core Web Vitals by identifying high-impact performance opportunities for LCP and CLS.

    Known limitations

    Bundle analysis requires a pre-generated stats.json file. Component documentation works best with .tsx files and a valid tsconfig.json.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    Requires stats.json for bundle analysis. Component documentation works best with .tsx files and requires tsconfig.json.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 18 days ago

    • Free with an Agensi account

    Software
    webpackNode.jsLighthouse Audit MCPPlaywrightvite@modelcontextprotocol/inspector

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Browser
    Network Access
    Environment Variables
    Listed18 days ago

    What's inside

    Frequently Asked Questions

    This skill audits accessibility (WCAG 2.1), analyzes bundle sizes for bloat, generates React component prop documentation, and runs comprehensive Lighthouse performance reports.

    The skill is optimized for React and TypeScript environments using Webpack or Vite; bundle analysis requires a stats.json file, while component scanning requires a valid tsconfig.json.

    Unlike standard LLM prompting, this skill interacts directly with your build artifacts and live DOM to provide evidence-based data rather than making guesses about your code.

    Yes, this skill is designed to work with any AI agent or platform that supports the Model Context Protocol (MCP), allowing you to trigger audits through natural language commands.

    You will receive the full MCP server integration, enabling tools like audit_accessibility, analyze_bundle, and scan_components for use within your AI development environment.

    Currently, bundle analysis requires a pre-generated stats.json file from your build tool, and component documentation is specifically tailored for .tsx files.

    New in Frontend & Web Apps

    Free