customer-research

Identify affected customers and cohorts from GitHub issue labels.

1|6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/fullsend-ai/.fullsend --skill customer-research-fullsend-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: customer-research
Source: https://github.com/fullsend-ai/.fullsend/tree/main/customized/skills/customer-research
Command: npx skills add https://github.com/fullsend-ai/.fullsend --skill customer-research-fullsend-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make better product decisions by connecting issues, feature requests, and onboarding questions to the customers and cohorts most affected, so you can prioritize based on real strategic impact.

Core Features & Use Cases

  • Customer Impact Analysis: Identify whether an issue affects strategic customers such as konflux-ci, redhat-developer, guacsec, RHDH, or TSD.
  • Adoption Blocker Detection: Check issue labels first to confirm whether custom/dev-blocker or custom/tsd-blocker signals an active onboarding blocker.
  • Prioritization Support: Use customer context to assess urgency, Reach, and Impact when triaging bugs, evaluating requests, or planning roadmap work.

Quick Start

Analyze this issue for customer impact, identify any strategic customers involved, and tell me whether it should be prioritized as an adoption blocker.

Frequently Asked Questions about customer-research

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

FAQPage Schema
How do I prioritize GitHub issues based on strategic customer impact?

To prioritize issues based on strategic customer impact, you analyze GitHub issue labels and customer context to identify affected accounts and determine urgency. This connects bugs and feature requests to the specific strategic cohorts experiencing the problem.

What is an adoption blocker in issue triage?

An adoption blocker in issue triage is a critical issue preventing customer onboarding or active usage. You detect it by checking GitHub issue labels for specific signals like custom/dev-blocker or custom/tsd-blocker to confirm its onboarding impact.

How do I assess customer reach and urgency for roadmap planning?

You assess customer reach and urgency for roadmap planning by evaluating which strategic accounts and cohorts are affected by an issue. This involves analyzing GitHub labels and customer context to weigh the broader impact of product decisions.

Does this approach work with specific strategic accounts like konflux-ci and RHDH?

Yes, this approach works with strategic accounts like konflux-ci, redhat-developer, guacsec, RHDH, and TSD. It evaluates issue context to determine if these specific customers are affected and whether the problem blocks their adoption.

Can I use GitHub labels to identify onboarding blockers during issue triage?

Yes, you can use GitHub labels to identify onboarding blockers during issue triage. Checking for custom/dev-blocker or custom/tsd-blocker labels confirms whether an issue actively blocks customer onboarding and requires immediate prioritization.

What is the best way to evaluate customer context for product decisions?

The best way to evaluate customer context for product decisions is to map issues to affected strategic cohorts and assess their urgency. This ensures prioritization reflects real-world adoption blockers and the actual reach of the problem.