CMS Issue Reporting Tool for Openclaw

A comprehensive CLI tool for reporting, tracking, and resolving bugs and feedback within the skill development lifecycle.

spzwin
v1.0.2
Apr 7, 2026
0
302
1

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install cms-report-issue

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install cms-report-issue using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is CMS Issue Reporting Tool?

The cms-report-issue tool is a specialized utility designed to manage the full issue lifecycle for developers working with Openclaw Skills. It acts as a centralized feedback hub, integrating seamlessly with other development tools like cms-create-skill and cms-push-skill to capture errors and improvement suggestions.

This skill ensures that every bug or exception is documented with precision, providing a structured way to handle error outputs from both manual entry and automated pipelines. By standardizing how issues are reported and tracked, it helps maintain the quality and reliability of the broader ecosystem of Openclaw Skills.

CMS Issue Reporting Tool Use Cases

  • Reporting bugs and exceptions encountered during the development of new AI agent capabilities.
  • Capturing real-time script errors by piping stderr directly into the reporting utility.
  • Managing a centralized list of pending improvements and feature requests for specific skills.
  • Tracking the resolution status of reported issues to ensure a closed-loop debugging process.

How CMS Issue Reporting Tool Works

  1. An issue is triggered manually via the CLI or automatically through a redirected pipe from another process.
  2. The report_issue script captures the skill code, version, and error details, submitting them to the tracking system.
  3. Developers use the list_issues script to view current open problems or generate statistics on skill health.
  4. Using authentication from cms-auth-skills, authorized users update issue statuses to 'resolved' or 'closed' after applying fixes.

CMS Issue Reporting Tool Setup

To get started with this reporting tool within your Openclaw Skills environment, ensure you have the necessary dependencies installed:

# Check the help menu for reporting options
python3 cms-report-issue/scripts/issue_report/report_issue.py --help

# Ensure cms-auth-skills is configured for authorized updates
# This is required for using the update_issue.py script

CMS Issue Reporting Tool Data Schema & Taxonomy

The skill organizes reporting data using the following structure to ensure compatibility across Openclaw Skills:

Parameter Requirement Description
--skill-code Required The unique identifier of the skill reporting the issue.
--version Required The specific version of the skill where the error occurred.
--error Optional A string description of the error (supports stdin).
--issue-id Required (Update) The unique ID assigned to the reported issue for tracking.
--status Required (Update) The new state: open, resolved, or closed.

CMS Issue Reporting Tool Advanced Features

  • Stdin Pipeline Support: Capture and report errors dynamically from any bash process.
  • Automated Authentication: Integrates with cms-auth-skills to handle secure state changes without manual token entry.
  • Statistical Reporting: Built-in functionality to aggregate issue data and monitor overall skill performance.
  • GitHub Template Integration: Includes pre-configured YAML templates for standardized bug reports and feature requests.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*