fix-build-agentops-analyze-ciAnalyze failed GitHub Action jobs for a pull request.
Install via ClawdBot CLI:
clawdbot install wu-uk/fix-build-agentops-analyze-ciGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/mlflow/mlflow/pull/19601Audited Apr 17, 2026 · audit v1.0
Generated Sep 9, 2026
Developers can quickly identify why a pull request's CI failed by running a single command with the PR URL. This tool summarizes root causes, error messages, and relevant log snippets, saving time compared to manual log inspection.
Teams struggling with intermittent test failures can use the skill to analyze failed job logs across multiple runs. It pinpoints failing test names and provides context, helping to stabilize the test suite.
Engineering managers can run the skill with the --debug flag to obtain token and cost information for CI analysis. This aids in monitoring tooling expenses and understanding resource utilization during debugging.
New developers can leverage the skill to independently diagnose CI failures without deep knowledge of the pipeline. This accelerates learning and reduces dependency on senior engineers for mundane debugging.
Deploy this skill within an engineering organization to reduce time spent on CI failure analysis. It enhances developer efficiency and accelerates feature delivery, indirectly increasing business agility.
Package the skill as part of a broader CI analytics platform offered to external development teams. Users subscribe to have AI-generated failure summaries integrated with their GitHub Actions.
Offer consulting services that use the skill to audit client CI systems, identify recurring failures, and recommend improvements. The tool streamlines the diagnostic phase of consulting engagements.
💬 Integration Tip
Invoke the skill via command line using 'uv run skills analyze-ci' with either a PR URL or specific job URLs. Ensure GitHub authentication is set up (via gh auth or GITHUB_TOKEN) for seamless integration.
Scored May 31, 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.