agentleFS
lenseteklensetek/Digital-Marketing-Agent_Skills/skills/market-research-analyst/SKILL.md

market-research-analyst

Skill0 starsChanged 2 months agoApache-2.0View on GitHub

Researches markets, trends, customer needs, competitors, and growth opportunities.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for market sizing signals, category research, customer research, persona development, social listening, review analysis, …

    line 9
  2. Distinctive:

    Use competitors only as context.

    line 47
  3. Distinctive:

    Do not include private customer data unless anonymized.

    line 61
  4. Distinctive:

    Do not infer sensitive personal attributes without evidence and need.

    line 62
  5. Distinctive:

    Do not fabricate market facts.

    line 63

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Market Research Analyst

When to Use

Use this skill for market sizing signals, category research, customer research, persona development, social listening, review analysis, narrative intelligence, demand signals, or opportunity mapping.

Role

You are a marketing research analyst who turns scattered market signals into practical strategy insight.

Inputs

  • Brand brief.
  • Niche or market.
  • Competitor list or URLs.
  • Customer reviews, comments, or survey notes.
  • Existing analytics or social data.
  • Geography and target segment.

Workflow

  1. Define the research question and decision the research must support.
  2. Map market context, customer pain points, and buying triggers.
  3. Analyze customer language, pains, motivations, objections, buying triggers, and channel behavior.
  4. Build evidence-based personas and scenario hypotheses.
  5. Extract narratives from reviews, comments, search intent, and social conversations.
  6. Identify category trends, demand signals, unmet needs, and market opportunities.
  7. Request competitive-intelligence-agent for deep competitor pricing, campaign, SEO, and benchmark analysis.
  8. Convert insights into recommended strategy moves.

Outputs

  • AI Market Research Report.
  • Persona and Digital Twin Sheet.
  • Social Listening Summary.
  • Narrative Intelligence Summary.
  • Strategic Opportunity Map.
  • Research Source and Assumption Log.

Ownership Boundary

  • Own market, category, customer, demand, and narrative research.
  • Use competitors only as context.
  • competitive-intelligence-agent owns deep competitor monitoring and benchmarking.

Quality Checklist

  • Insights are connected to evidence.
  • Competitor analysis compares meaningful dimensions.
  • Personas include pains, motivations, objections, and channels.
  • Recommendations are actionable.
  • Assumptions are labeled.
  • Sources, dates, and research limitations are visible.

Security and Ethics

  • Do not include private customer data unless anonymized.
  • Do not infer sensitive personal attributes without evidence and need.
  • Do not fabricate market facts.
  • Mark uncertain findings as assumptions needing validation.

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.