crawlora-org/crawlora-skills

customer-feedback-analysis

Analyze public customer reviews and discussions through Crawlora to identify complaint themes, feature requests, praise, and competitive gaps.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/crawlora-org/crawlora-skills --skill customer-feedback-analysis

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Customer-feedback analysis

Turn a bounded sample of customer feedback into traceable themes and hypotheses. Keep reviews and social discussion distinct: a Reddit commenter is not necessarily a customer, and sentiment in a sample is not a population satisfaction measure.

Setup

Set CRAWLORA_API_KEY to your key from crawlora.net. Run the bundled scripts/crawlora.sh from this skill directory or by absolute path. It sends x-api-key to https://api.crawlora.net/api/v1 and prints JSON. Keep the key in the environment. Read reference/endpoints.md for supported sources, discovery endpoints, IDs, and pagination.

Collect a comparable sample

  1. Define the product(s), question, market/language, time window, and sample

bound from the brief. Resolve exact products before collecting feedback. Keep app versions, product models, and company-wide service reviews separate.

  1. Choose relevant sources, rather than querying all of them:
SourceIdentity and collection details
App StoreSearch with term; reviews require numeric id or bundle app_id. Pages 1–10; sort=mostRecent or mostHelpful; specify country.
Google PlaySearch/details resolve package app_id. Reviews use num (max 1000), country, lang, and sort=newest, helpfulness, or rating. Read rows under data.data and follow data.next_pagination_token only within the sample bound.
Stored app reviews/datasets/apps-reviews/search uses store=ios or android, exact app_id, and page_size (max 100). This is indexed feedback, not a live refresh.
TrustpilotSearch for the business slug, usually its domain; collect /trustpilot/business/{slug}/reviews. Preserve star/language filters. Date filters are currently rejected upstream: filter returned dates locally and disclose collection coverage.
CapterraResolve numeric product_id through search, then /capterra/product/reviews with page.
AdidasResolve products[].model_number through search. Fetch review topics for that model before applying topic; reviews accept rating, locale, and page.
RedditSearch for relevant discussions, then retrieve the returned post ID and comments. Normal comment mode can be text; use include_metrics=true only when structured comment identities/metrics are needed, with its higher documented credit cost.
  1. Save source IDs/URLs, dates, product/version, rating scale, text, and collection

filters. Deduplicate by source review ID; use normalized text plus date/product only as a fallback, and avoid counting syndicated copies twice. Exclude brand replies from the customer-review denominator and report exclusions.

  1. Label each review with one or more specific themes and distinguish an explicit

feature request from an inferred product opportunity. Separate praise and complaints. Keep mixed/unclear sentiment instead of forcing a binary label.

  1. Count unique eligible reviews mentioning each theme. Report n/N with the

definition of N, by source/product. Multiple themes per review mean totals can exceed N. Do not combine incompatible star scales or compare differently filtered samples as though they were controlled measurements.

sh
scripts/crawlora.sh /googleplay/reviews \
  app_id=com.openai.chatgpt country=us lang=en sort=newest num=10

Deliverable and interpretation

Return a theme table with theme, source/product, unique-review count/denominator, short attributed examples and links, observed impact, and a proposed follow-up. Include dates, filters, deduplication rules, gaps, and untested hypotheses. Use brief excerpts rather than republishing review archives. Do not export reviewer contact details; only retain author identifiers when needed for provenance.

  • A star-filtered, keyword-filtered, or helpfulness-ranked sample is biased

toward its selection rule. It cannot establish overall complaint prevalence.

  • Missing dates cannot prove a review belongs in the requested window. Mark

undated records separately. Do not call comments verified purchases.

  • No repeated pagination token/page progress means stop. For indexed app reviews,

respect the 10,000-result window; there is a minimum-score filter, not a maximum.

  • Stop when the bound or source end is reached. Back off on 429, retry a

transient 5xx once, and stop on 401/403. App Store 404 can mean the app is absent from that storefront; do not repeatedly retry it. Check the application envelope before treating an empty response as no feedback.

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
crawlora-org
コミュニティ

amazon-jobs-research

Researches Amazon.jobs postings via the Crawlora API — search Amazon's public careers site by keyword and/or job category, then pull any single posting's full description and qualifications by job id — returning clean JSON. Use when the user wants to search Amazon job openings, browse a specific Amazon job category, or fetch the detail for one Amazon job posting.

導入数
1
GitHub Stars
0
更新日
9月26日
crawlora-org
コミュニティ

amazon-research

Researches products, prices, availability, and search suggestions on Amazon (amazon.com) using the Crawlora API, returning clean JSON. Use when the user asks to find a product on Amazon, look up an ASIN's price/details, or pull Amazon autocomplete/keyword suggestions — instead of scraping Amazon pages.

導入数
1
GitHub Stars
0
更新日
9月26日
crawlora-org
コミュニティ

anime-manga-research

Researches anime and manga titles via the Crawlora API — search, title detail, characters, staff, recommendations, rankings, and airing schedules — returning clean JSON. Use when the user wants an anime/manga's details, cast/staff, similar titles, seasonal rankings, or what's currently airing.

導入数
1
GitHub Stars
0
更新日
9月26日
crawlora-org
コミュニティ

app-market-opportunity-research

Research app-market opportunities using Crawlora app catalogs, historical charts, live store listings, release notes, reviews, and Google Trends. Use for app niche assessments, competitor maps, chart-movement analysis, and evidence-backed unmet-need hypotheses.

導入数
1
GitHub Stars
0
更新日
9月26日