A professional utility that transforms vague bug descriptions into structured, actionable reports with reproduction steps and severity levels.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install bug-report-pro
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install bug-report-pro using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The bug-report skill is a cornerstone of efficient development workflows within the ecosystem of Openclaw Skills. It solves the perennial problem of incomplete or vague issue reports by providing a structured framework that guides the transformation of a simple observation into a comprehensive technical document. By using these Openclaw Skills, teams can ensure that every bug reported contains the necessary context—such as environment details, expected behavior, and priority levels—required for immediate engineering action.
This tool is designed to save time for both reporters and developers. It uses logic to classify severity based on system impact and suggests specific investigation areas like input validation or race conditions based on the bug pattern. Integrating this into your daily routine ensures that Openclaw Skills maintain high documentation standards across your entire project lifecycle.
To deploy this skill within your environment, ensure you have the agent configured to recognize Openclaw Skills. You can then use the following commands to generate reports directly from your CLI.
# Standard usage from a description
bug-report "login page crashes when I use special characters in password"
# Advanced usage with environment and frequency context
bug-report "API returns 500 on large file uploads" --component "upload-service" --env "production" --frequency "always"
The skill organizes metadata into a taxonomy designed for high searchability and developer clarity. Openclaw Skills use the following data structure:
| Attribute | Description | Values |
|---|---|---|
| Title | Concise summary of the defect | String (max 80 chars) |
| Severity | Impact on system functionality | Critical, High, Medium, Low |
| Priority | Urgency of the fix | P0 (Immediate) to P3 (Backlog) |
| Environment | Where the bug was observed | production, staging, dev, local |
| Pattern | Categorization of the failure | Crash, 500 Error, UI Glitch, etc. |
All generated data is portable across Openclaw Skills and can be exported as raw JSON for database ingestion or formatted Markdown for documentation.
Loading
A comprehensive testing framework designed to probe AI agents for emergent properties, self-awareness, and cognitive capabilities beyond their explicit training.

A comprehensive CLI-based skill for searching, downloading, and publishing illustrations and manga on the Pixiv platform.

A physical-layer hex auditing tool that detects hidden binary data, control characters, and encoding-based attacks in file packages.

A powerful browser automation skill for managing social media platforms through persistent, authenticated sessions.

A specialized headless browser CLI that uses accessibility trees and reference-based selection for reliable AI-driven web automation.

A mandatory discovery system for Claude Code that enables token-efficient lazy loading of specialized agents.








































