phy-bundle-size-auditJavaScript bundle size auditor and budget enforcer. Parses webpack stats JSON, Vite bundle report, Rollup output, or Next.js build output to identify largest...
Install via ClawdBot CLI:
clawdbot install phy041/phy-bundle-size-auditGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://canlah.aiAudited Sep 16, 2026 · audit v1.0
Generated Oct 5, 2026
A frontend platform team wires the skill into their GitHub Actions pipeline to fail PRs that push any initial JS chunk over 500KB. The skill parses webpack stats JSON from each build and posts a per-chunk size summary as a PR annotation.
A growth engineer investigates a sudden Lighthouse regression after adding analytics and a carousel library. The skill parses the .next/ directory, ranks chunks by size, and pinpoints the offending package.
A component library maintainer audits the Rollup output before publishing a new major version. The skill detects treeshaking failures in side-effectful imports and suggests export restructuring.
An engineering team modernizing a legacy CRA app uses the skill to baseline current bundle sizes before migrating to Vite. They track chunk-level deltas across both builds.
A startup shipping a Progressive Web App enforces strict chunk budgets to keep first-load under 200KB on 3G. The skill detects duplicate dependencies across lazy-loaded routes and flags chunks breaching the budget.
Offer the skill as part of a paid CLI or dashboard that tracks bundle size trends across repos and posts weekly regression reports.
Bundle the skill into a CI platform's marketplace as a premium check that blocks merges on budget violations with detailed annotations.
Use the skill as the diagnostic engine for paid frontend performance audits delivered to enterprise clients.
💬 Integration Tip
Run a build first so the skill has artifacts to parse, then wire the --ci-config output into your pipeline's fail gate to automate enforcement.
Scored Sep 16, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.