ai-feedback-collector

Convert free-form AI tool problem reports into structured feedback reports.

31|6|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill ai-feedback-collector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-feedback-collector
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/ai-feedback-collector
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill ai-feedback-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you convert free-form descriptions of problems with AI tool usage into a structured, ready-to-share feedback report without over-interpreting unclear details.

Core Features & Use Cases

  • Structured issue collection: Extracts tool, scenario, workflow stage, impact, and evidence from the user’s original text.
  • Taxonomy-based classification: Assigns problem category, severity, frequency, and routing-friendly labels using the repository’s label taxonomy guidance.
  • Paste-ready normalization: Produces an objective report template suitable for issue trackers, spreadsheets, chat threads, or internal feedback systems.

Quick Start

Use the ai-feedback-collector skill to convert your description of what went wrong while using an AI tool into a structured feedback report.

Frequently Asked Questions about ai-feedback-collector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert free-form AI tool issue reports into structured feedback?

To convert free-form AI tool issue reports into structured feedback, you submit the raw text to a normalization process that extracts tool, scenario, impact, and evidence. This produces an objective, paste-ready template for downstream triage.

What is taxonomy-based classification for AI feedback collection?

Taxonomy-based classification for AI feedback collection is the process of assigning problem category, severity, and frequency labels to observed behaviors. It separates facts from inferences to optimize routing within issue trackers and internal feedback systems.

How do I report AI workflow issues for coding and data analysis without over-interpreting details?

You report AI workflow issues for coding and data analysis by applying a structured template that extracts explicit fields like workflow stage and impact. This normalizes the report while maintaining a strict separation of facts versus inferences to avoid over-interpretation.

Can I use structured issue reporting for internal AI-assisted workflows across different scenarios?

Yes, you can use structured issue reporting for internal AI-assisted workflows across coding, writing, search, and data analysis scenarios. It normalizes observed behaviors and impacts consistently across various use cases by applying taxonomy labels.

What is the best way to format messy AI issue descriptions for issue trackers and spreadsheets?

The best way to format messy AI issue descriptions for issue trackers and spreadsheets is to apply paste-ready normalization. This converts free-form text into a consistent template with explicit labels, separating facts from inferences for efficient routing.

Does structured feedback generation work without prior knowledge of the repository's label taxonomy?

No, structured feedback generation relies on the repository's label taxonomy guidance to assign problem category, severity, and routing-friendly labels. This taxonomy is required to accurately categorize the extracted facts and impacts for downstream triage.