perceptible-experience-extractor

Extract user insights from interview transcripts into a seven-field perceptible experience parameter table.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/MeerkatAIChina/meerkat-skills-activity --skill perceptible-experience-extractor-meerkataichina
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perceptible-experience-extractor
Source: https://github.com/MeerkatAIChina/meerkat-skills-activity/tree/main/skills/perceptible-experience-extractor
Command: npx skills add https://github.com/MeerkatAIChina/meerkat-skills-activity --skill perceptible-experience-extractor-meerkataichina

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw user interview transcripts contain scattered scenarios and needs that are hard to turn into actionable product innovation inputs. This Skill structures any interview transcript into a logically self-consistent table covering category, opportunity, persona, need, benefit, perceptible experience parameter, and counterintuitive user insight. ## Core Features & Use Cases - Seven-Step Extraction Workflow: Reads the full transcript, builds user personas, decomposes scenario-based needs per category, defines benefits, quantifies experience parameters, and closes with counterintuitive insights plus a completeness audit. - Seven-Field Structured Output: Produces a Markdown table with category lifecycle, opportunity gaps, three-dimensional personas, surface vs. deep needs, benefit statements, quantified perceptible experience parameters, and behavioral-paradox insights. - Self-Consistency Checklist: Enforces validation rules such as quantified parameters, deep-need-driven benefits, and anti-cliche insight conclusions before output. - Use Case: Paste a consumer interview transcript about a smart thermos or lipstick product, and receive a row-per-need table that product teams can feed directly into concept definition and technology planning. ## Quick Start Analyze this user interview transcript and output the seven-field perceptible experience parameter table with one row per distinct need.

Frequently Asked Questions about perceptible-experience-extractor

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

FAQPage Schema
How do I turn user interview transcripts into structured product insights?

Provide the full interview transcript as input and the Skill runs a seven-step workflow: extract scenarios, build personas, decompose needs per category, define benefits, quantify experience parameters, derive insights, and audit completeness. The result is a Markdown table with one row per distinct need.

What is a perceptible experience parameter in user research?

A perceptible experience parameter is a quantified, user-perceivable effect metric that expresses how well a deep need is satisfied. It must include a number, time dimension, and sensory description, such as carving integrity staying above 95 percent after 30 days of use.

What input format does this interview analysis require?

It requires the complete text of a user interview transcript. Optional supplementary inputs include product category, target persona, competitor information, and market background, which improve the accuracy of category lifecycle and opportunity judgments.

Can it handle transcripts covering multiple product categories?

Yes. The workflow first detects how many categories appear in the transcript and generates an independent table for each category, ensuring no scenario or need mentioned by the user is omitted.

What are the limitations of transcript-based insight extraction?

The output quality depends on transcript completeness; missing information is inferred from category common sense and marked as derived. It cannot fabricate needs beyond the transcript and is not a substitute for quantitative survey validation.