code-statsVisualizes repository complexity by counting files, lines of code, and grouping by extension. Use to assess project size or growth.
Install via ClawdBot CLI:
clawdbot install autogame-17/code-statsGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 1, 2026
Maintainers can run the skill on their repository to track growth in file count and lines of code over time, helping identify when a project is becoming overly complex or needs refactoring. This aids in planning sprints and allocating resources for code maintenance.
Freelancers can use the skill to quickly gauge the size of a client's codebase before providing a quote, ensuring estimates are based on tangible metrics like file and line counts. This reduces risk of underestimating work and improves project scoping accuracy.
Instructors in coding bootcamps or universities can analyze student submissions to assess complexity and adherence to guidelines, using the breakdown by extension to check for proper file organization. This provides objective metrics for grading and feedback.
During tech company acquisitions, analysts can run the skill on target codebases to evaluate asset size and complexity, informing valuation decisions based on metrics like total lines of code and file distribution. This helps identify potential technical debt or integration challenges.
Integrate the skill into a cloud-based dashboard where teams upload repositories to visualize trends in code growth and complexity over time. Charge a monthly subscription based on the number of repositories or users, targeting development teams needing continuous monitoring.
Offer the skill as part of a broader consulting package for code audits, where experts use the metrics to provide recommendations on refactoring or optimization. Clients pay a one-time or retainer fee for detailed reports and actionable insights.
Provide a free version of the skill for individual developers to use locally, with a paid upgrade that includes advanced features like historical comparisons, team collaboration, and integration with CI/CD pipelines. Monetize through premium licenses or enterprise plans.
💬 Integration Tip
Install the skill via npm or a package manager, then run it from the command line with an optional path argument; it outputs JSON for easy parsing into other tools or dashboards.
Scored Apr 19, 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.