repo-surveyorUse when Cartograph CLI or MCP is unavailable and you still need Cartograph-style repo orientation, task context, or documentation inputs from manual file su...
Install via ClawdBot CLI:
clawdbot install anthony-maio/repo-surveyorGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 21, 2026
When migrating a legacy monolith to microservices, use Repo Surveyor to identify core entry points and dependency hubs without Cartograph. This helps prioritize refactoring efforts and understand coupling before splitting modules.
For teams onboarding new hires, manually survey the repository to create a concise overview of key files and dependencies. This accelerates familiarity with the codebase when automated tools are unavailable.
Before contributing to an open-source project, use this skill to trace important files and APIs manually. It ensures contributions align with the project's architecture and reduces review cycles.
During production incidents in environments without Cartograph access, quickly survey logs and config files to identify root causes. This manual approach helps triage issues when automated analysis is down.
For regulatory compliance needs, manually extract key files and dependencies to produce audit-ready summaries. This is useful when automated documentation tools are not permitted or integrated.
Offer manual codebase analysis services to clients lacking automated tools. Use Repo Surveyor to provide insights on architecture, technical debt, and migration strategies, charging per project or hourly.
Integrate Repo Surveyor as a fallback feature in development platforms. When primary analysis tools fail, this skill ensures continuous service, reducing downtime and increasing customer retention.
Develop training programs teaching teams how to manually survey repositories for better code understanding. Sell courses or workshops to improve developer productivity and reduce reliance on tools.
💬 Integration Tip
Always check for OpenProse plugin templates first to streamline summaries. Keep manual reads focused on entry points and hubs to avoid time waste.
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.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
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.