Agent skill

research-gap-analyzer

プロジェクト プロジェクトの機能(docs/features/)とリサーチ(docs/research/)文書を分析し、高収益/高LTV/低離脱達成のためのリサーチギャップを識別し、欠落したP0/P1リサーチを自動実行する。

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill research-gap-analyzer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 22 KB
Bundled scripts: none
Path: skills/analysis/research-gap-analyzer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

The skill performs a runtime scan of project feature documents (docs/features/) and research documents (docs/research/), then identifies research gaps that block achieving high revenue, high LTV, and low churn. It maps KPI targets to required research and prioritizes gaps, automatically initiating deep research for P0/P1 gaps. It registers work in assets/research-status.json, runs a deep-research workflow via providers (openai or google) with a structured markdown request, and saves results with automatically generated frontmatter metadata. It then updates the status and can trigger manifest regeneration via a Bash script.

How it works

  1. Step 1: Runtime Scan
    • Scan docs/features//PRD-.md for features.
    • Scan docs/research/*.md for existing research.
    • Do not rely on hard-coded feature lists; always scan latest.
  2. Step 2: KPI-Feature-Research Mapping
    • Refer to references/kpi-targets.md to derive necessary research per KPI, mapping to required research items.
  3. Step 3: Gap Identification
    • Evaluate research quality with a color/icon scheme (none, concept, complete, update needed).
    • Apply a quality checklist (Executive Summary, quantitative data, Action Items, Japan-First alignment).
  4. Step 4: Prioritization
    • Use ROI-based scoring: Priority = (KPI impact × 3) + (ease × 2) + (Japan-First fit × 1).
    • Classify as P0, P1, or P2.
  5. Step 5: Status registration + Deep Research
    • Register work in assets/research-status.json before starting.
    • Run deep research with providers (openai or google) following a structured markdown request template.
  6. Step 6: Results storage + Auto metadata
    • Save results with automatically generated Frontmatter fields (research_id, title, category, kpi_relevance, feature_domains, competitors, target_apps, target_user_levels, pain_points, learning_topics, actionability, scanner, priority, quality, etc.).
    • Auto-create Frontmatter and trigger manifest regeneration via Bash script (scripts/generate_research_manifest.py).

When to use it

Use when you want to identify critical research gaps blocking KPI achievement and automatically initiate targeted deep research for P0/P1 gaps.

What it can touch

  • Tools: claude-code (as declared)
  • Files touched: assets/research-status.json, docs/research/*.md (for new results), generated Frontmatter in new Markdown files, references/research-status-schema.json (for schema), and scripts/generate_research_manifest.py (for manifest regeneration).

Caveats

  • Frontmatter is auto-generated after deep research; human editing is not required for this step.
  • The workflow relies on predefined KPI targets and gap definitions in repository references; outcomes depend on the quality and relevance of input documents.
  • The extraction and classification logic is described conceptually; actual implementation details are defined within the skill's automation steps.
From the SKILL.md

# Research Gap Analyzer プロジェクト プロジェクトの機能文書と既存リサーチを**ランタイムスキャン**し、高収益、高LTV、低離脱率達成に必要なリサーチギャップを自動識別するスキルである。 ## 核心原則 ### SSOT (Single Source of Truth) ``` ┌─────────────────────────────────────────────────────────────┐ │ SSOT 構造 (v2.0 - Frontmatter ベース) │ ├─────────────────────────────────────────────────────────────┤ │ docs/research/*.md Frontmatter → リサーチメタデータ (SSOT) │ │ スキーマ: docs/_schemas/ │ │ research-frontmatter. │ │ schema.json │ │ docs/_manifests/research-manifest.json │ │ → Frontmatter から自動 │ │ 生成されたキャッシュ (読取専用)│ │ assets/research-status.json → リサーチ作業状態 (SSOT) │ │ references/kpi-targets.md → KPI 定義 + Feature マッピング │ │ references/critical-gaps.md → クリティカルギャップリスト │ │ docs/features/ → 動的スキャン (SPEC 読込) │ │ docs/research/README.md → 文書リスト (参照用) │ └─────────────────────────────────────────────────────────────┘ ⚠️ 禁止: 同じデータを複数ファイルにハードコーディングしない。 - Feature Tier は kpi-targets.md でのみ定義 - リサーチ状態は assets/research-status.json でのみ管理 - リサーチメタデータは各文書の Frontmatter でのみ定義 - Manifest は直接修正しない (スクリプトで自動生成) - README.md は文書リストのみ、状態管理 X ``` ### 批判的思考 5段階 1. **根本原因把握**: なぜこのギャップが発生したのか? 2. **完全性検証**: このリサーチが KPI 達成に十分か? 3. **業界標準比較**: Duolingo/Speak/ELSA はどうしているか? 4. **代替案検討**: 他のアプローチはないか? 5. **ROI

What's inside
Steps it walks through
  1. 核心原則
  2. SSOT (Single Source of Truth)
  3. 批判的思考 5段階
  4. 核心 KPI 目標
  5. 識別されたクリティカルギャップ (2026-01-19 分析基準)
  6. 🔴 P0 ギャップ (即座にリサーチ必要)
  7. 🟡 P1 ギャップ (1ヶ月以内にリサーチ必要)
  8. Workflow
  9. Step 1: ランタイムスキャン
  10. Step 2: KPI-Feature-Research マッピング
  11. Step 3: ギャップ識別 (批判的分析)
  12. Step 4: 優先順位決定
  13. Step 5: 状態登録 + ディープリサーチ実行
  14. Step 6: 結果保存 + 自動メタデータ生成
Ships with 1 file
  • metadata.json
Commands it runs
AI が自動的に実行 (人間介入不要)
Frontmatter スキーマ検証 (問題発生時のみ)
More from claude-skill-registry
All skills →
About this skill
What does the research-gap-analyzer skill do?

プロジェクト プロジェクトの機能(docs/features/)とリサーチ(docs/research/)文書を分析し、高収益/高LTV/低離脱達成のためのリサーチギャップを識別し、欠落したP0/P1リサーチを自動実行する。

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill research-gap-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going