structure-of-complaint

Convert a user review into a JSON complaint graph with typed nodes and relations.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/speplinski/hackathon-opus-47 --skill structure-of-complaint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structure-of-complaint
Source: https://github.com/speplinski/hackathon-opus-47/tree/main/skills/structure-of-complaint
Command: npx skills add https://github.com/speplinski/hackathon-opus-47 --skill structure-of-complaint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts a typed complaint graph from a single user review, enabling auditable analysis of user pain, expectations, and losses.

Core Features & Use Cases

  • Identify 3–7 nodes across the types pain, expectation, triggered_element, workaround, and lost_value, anchored to verbatim quotes from the source review.
  • Map typed relations (triggers, violates_expectation, compensates_for, correlates_with) to produce a traceable graph.
  • Output a JSON object containing nodes and edges suitable for downstream audits and clustering.

Quick Start

Process the provided <user_review> block and output a 3–7 node JSON graph with verbatim quotes.

Frequently Asked Questions about structure-of-complaint

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

FAQPage Schema
How do I extract structured data from a user review for NLP analysis?

To extract structured data from a user review, you can convert the verbatim text into a JSON complaint graph. This process identifies specific pain points and expectations, outputting a network of typed nodes and edges for downstream analysis.

What is a complaint graph and how does it map user pain points?

A complaint graph is a structured JSON representation of a user review that maps typed relationships between core issues. It uses five node types, such as lost value and triggered element, connected by four relation types to trace exactly how a problem impacts the user.

How do I turn verbatim quotes into a typed JSON graph?

You turn verbatim quotes into a typed JSON graph by processing a review payload enclosed in user review tags. The system automatically anchors 3 to 7 generated nodes directly to the exact text from the review, ensuring complete traceability and data extraction accuracy.

Can I use this complaint graph extraction for clustering multiple user reviews?

Yes, the complaint graph extraction outputs a standardized JSON object containing nodes and edges, which is suitable for downstream audits and clustering. By mapping typed relations across multiple reviews, you can systematically analyze aggregated user pain and lost value.

What are the limitations of converting a single review into a complaint graph?

The primary limitation is that the graph extraction operates on a single user review payload at a time rather than batch processing. Additionally, the output is strictly constrained to 3 to 7 nodes and four typed relations, which may oversimplify highly complex user feedback.