agentleFS
Sign inStart free
esot321cesot321c/marketing-ops/skills/market-research/SKILL.md

market-research

Skill0 starsChanged 4 months agoMITView on GitHub

Research competitors, content patterns, SERPs, social formats, audience language, positioning gaps, and marketing opportunities. Use for competitor research, market research, SEO/AEO research, social pattern analysis, content gap analysis, and campaign research. Do not manage prospect accounts, outreach, lead lists, or sales pipeline.

115 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, everything-claude-code-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • InfopibeSkill

    investor-outreach

    Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

    Also in 22 projects that use this

  • shawnpangSkill

    competitor-monitoring

    When the user wants to set up ongoing tracking of competitor activity — pricing changes, feature launches, hiring signals, content, or public mentions. Also use when the user mentions "track competitors", "what are competitors doing", "competitor alerts", or "market watch".

    Also in 3 projects that use this

  • tpavanipradeepSkill

    nextjs-turbopack

    Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

    Also in 14 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 7 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 101 edited versions we read keep these.

  • 12

    Distinctive

    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 to produce marketing intelligence, not sales account intelligence.

    line 8
  2. Distinctive:

    Use the available context:

    line 12
  3. Distinctive:

    Create a research brief with:

    line 23
  4. Distinctive:

    Do not scrape private data.

    line 39
  5. Distinctive:

    Do not build lead lists.

    line 40
  6. Distinctive:

    Do not recommend outreach cadences.

    line 41
  7. Distinctive:

    When a source redirects to login or hides the needed data:

    line 47
  8. Distinctive:

    Do not switch sources silently when login would materially improve the research.

    line 56
  9. Distinctive:

    prefer the current visible page before running new searches,

    line 63
  10. Distinctive:

    avoid rapid multi-query loops,

    line 64
  11. Distinctive:

    stop if the platform shows checkpoint, captcha, suspicious activity, or session-warning UI,

    line 66
  12. Distinctive:

    use public/non-auth sources for broader collection when logged-in collection is not essential.

    line 67

“Common” is measured: kept by at least 6 in 10 of the 101 edited versions of this file we could read. “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

Use this skill to produce marketing intelligence, not sales account intelligence.

Inputs

Use the available context:

  • brand profile from data/brands/
  • campaign brief from data/campaigns/
  • website pages
  • competitor URLs
  • search results
  • social examples supplied by the user

Output

Create a research brief with:

  • market question
  • audience being studied
  • competitors or examples reviewed
  • messaging patterns
  • content formats that appear to work
  • SEO/AEO opportunities
  • creative opportunities
  • risks and sameness traps
  • recommended next marketing actions

Rules

  • Cite sources when browsing.
  • Distinguish observed facts from inferences.
  • Do not scrape private data.
  • Do not build lead lists.
  • Do not recommend outreach cadences.

Auth-Gated Sources

Some high-value research sources require a logged-in browser session, including LinkedIn organic search, Instagram, TikTok detail pages, Meta Ads Library details, YouTube Studio, Google Search Console, and social analytics.

When a source redirects to login or hides the needed data:

  1. Navigate to the exact source or search URL.
  2. Tell the user what source needs login and why.
  3. Pause and let the user log in manually.
  4. Continue only after the user confirms they are in.
  5. Capture only visible/public or user-authorized information.
  6. Record login limitations in the research notes.

Do not switch sources silently when login would materially improve the research.

Authenticated Source Throttling

For LinkedIn, Instagram, TikTok, Meta, YouTube, and other logged-in or rate-sensitive sources:

  • use small batches,
  • prefer the current visible page before running new searches,
  • avoid rapid multi-query loops,
  • save screenshots and notes so research can resume later,
  • stop if the platform shows checkpoint, captcha, suspicious activity, or session-warning UI,
  • use public/non-auth sources for broader collection when logged-in collection is not essential.

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.

Check your setup, free