agentleFS
spiralcrew-ouspiralcrew-ou/profilespider-agent-skills/research-gap-analysis/SKILL.md

research-gap-analysis

Skill9 starsChanged 5 months agoMITView on GitHub

Identifies missing information required to complete qualification, segmentation, or outreach preparation. Use when the user provides records and a goal and wants prioritized research gaps with sources.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Research Gap Analysis

Purpose

Identify missing information required to complete qualification, segmentation, or outreach prep.

When to use this skill

  • Finding what blocks qualification or segmentation
  • Prioritizing enrichment work
  • Scoping research before outreach
  • Turning "incomplete data" into a task list

When not to use this skill

  • You have no goal to assess gaps against
  • The dataset is already complete
  • You want the gaps filled, not identified

Required inputs

  • Records
  • The goal (qualify, segment, or prep outreach)

Optional inputs

  • Required fields for the goal
  • Approved research sources

Rules

  1. Assess gaps against the stated goal.
  2. Explain why each gap matters and its impact.
  3. Suggest a realistic research source per gap.
  4. Prioritize gaps by impact.
  5. List assumptions to verify.

Process

  1. Parse the goal and required fields.
  2. Compare records to requirements.
  3. List missing fields and their impact.
  4. Suggest sources and assign priority.
  5. Record unresolved assumptions.

Output format

Return one record per identified gap with the following fields:

  • missing_field
  • why_it_matters
  • impact_on_decision
  • suggested_research_source
  • priority
  • unresolved_assumptions

Validation

  • Confirm gaps map to the goal.
  • Confirm priorities reflect impact.
  • Confirm assumptions are flagged.

Limitations

  • It identifies gaps; it does not fill them.
  • Source suggestions may vary in availability.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.