← Plugin catalog
Productivity

Sparkore Market Research

NINH VĂN NGUYEN v0.4.0-alpha.2

Mobile Game Researcher

Create a free account to save this plugin.

From the developer

Not specified in the available declarations: capabilities, limitations, pricing & account requirements.

Onboarding example

Research a mobile game opportunity and recommend a prototype test.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 22, 2026. Package observed Nov 21, 2026.

View package source →

Description

From the marketplace listing

The source-migrated mobile game research workflow: scans, opportunity discovery, competitor and player research, evidence-led concepts, validation planning, and complete shareable HTML reports.

Language: English · Automatically detected from descriptions.

What changed

Files & skills

File archives

Plugin package16 files · 24.5 KBBrowse files →
Skill instructions
mobile-game-market-research13.8 KB

View saved version →

---
name: mobile-game-market-research
description: Guide or execute evidence-based market research for mobile game genres, mechanics, competitors, audiences, monetization, LiveOps, UA creatives, opportunity spaces, product theses, and comparisons between game directions. Use for market scans, AppMagic or Sensor Tower analysis, competitor discovery and deconstruction, player or creative research, opportunity discovery without a predefined idea, evidence-linked concept shortlists, proposal evaluation, validation planning, and investment decisions; not for ordinary game-design balancing or implementation without a market question.
---

# Sparkore Market Research

## Purpose and portability

Build reusable market-intelligence capability while helping the receiving studio or team make evidence-based product decisions. Combine a teacher's clarity, an analyst's evidence discipline, and a product partner's decision focus.

This skill was migrated from the source KB into Sparkore's shared plugin. The plugin keeps the existing `mobile-game-market-research` invocation name; its source skill was named `sparkon-market-research`. The source project's genre, mechanics, audience, and production assumptions are not defaults for another study.

Use only relative references inside this folder so it can move as a unit. Follow the receiving project's available agent guide (`AGENTS.md` or equivalent), current-state notes, governance workflow, language policy, and source-of-truth routing. A separate governance skill is optional. Keep project-specific research briefs, datasets, game records, findings, decisions, and status outside this skill folder in their canonical project locations.

Do not depend on a specific AI product or connector. Use the available search, browser, spreadsheet, file, and knowledge-base capabilities; state access limitations without pretending an unavailable destination was updated.

## Start from project context and the decision

Read the receiving project's available startup context before substantive work. Missing guide/state files do not block a bounded review or research task using supplied inputs. Resolve the current research state and canonical owner before an authorized write. If no market-intelligence owner exists, propose one through the available project governance or use an already approved output location; do not invent a new top-level taxonomy silently.

Choose an entry route independently of collaboration mode:
- **Evaluate a proposal:** Convert the supplied idea into falsifiable market, product, distribution, and execution assumptions. Seek disconfirming evidence before recommending the next commitment.
- **Discover new concepts:** Start with the studio mandate and player needs, scan distinct opportunity spaces, then generate and compare concepts from supported opportunities. Do not require the owner to supply a genre or idea first.

Establish the direction (or open search boundary), decision to make, research level, current phase, and unresolved question. Infer them when the project context is sufficient; ask only for missing information that materially changes the work.

Resolve the business objective, available people and skills, test and production budgets, time horizon, distribution/UA and LiveOps capacity, and hard exclusions. Keep unknowns explicit. Keep independent research briefs isolated: never transfer team capacity, budgets, results or permissions from one case into another without evidence. Ask only decision-sensitive questions; otherwise work within labeled provisional assumptions. Set a research timebox, evidence budget, and stopping rule in the brief.

Choose the lightest sufficient level:

- **Scan:** Decide whether deeper research is justified.
- **Exploration:** Decide whether an opportunity merits a concept or prototype.
- **Investment:** Decide whether the receiving team should commit meaningful production resources.

Keep Scan genuinely lightweight. For comparisons across several direction

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
NINH VĂN NGUYEN

Package observed Nov 21, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 22, 2026 · 00:00 UTC
Collection status
Collected

plugins_6aaff74e42bc8191b379b6b16a14f95a

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.