agentleFS
thiefdroppersthiefdroppers/cyber-investigator-skills/skills/market-research/SKILL.md

market-research

Skill2 starsChanged 47 days agoMITView on GitHub

Research markets, audiences, competitors, category language, user pain points, trust signals, and current positioning before writing or revising public-facing product or website content. Use for ThiefDroppers, ELARA, RAI, website strategy, landing pages, product positioning, category creation, competitive comparisons, and any copy decision that should be grounded in current market evidence rather than intuition.

118 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-materials

    Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets.

    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

  • 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

  • CodeWithBehnamSkill

    dmux-workflows

    Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

    Also in 15 projects that use this

  • +1 more from Infopibe

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 104 edited versions we read keep these.

  • 7

    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:

    Search current market language, competing products, public-sector guidance, user questions, and relevant community discussions.

    line 13
  2. Distinctive:

    Treat ThiefDroppers as global from day one.

    line 24
  3. Distinctive:

    Use jurisdiction-specific material only as a local layer, never as the platform identity.

    line 25
  4. Distinctive:

    Prefer primary sources, regulators, major platforms, credible research, and recent public data.

    line 26
  5. Distinctive:

    Never invent market size, adoption, loss figures, partnerships, user counts, or product capabilities.

    line 28
  6. Distinctive:

    Do not frame the product as antivirus, surveillance, a public suspect database, or an accusation engine.

    line 29
  7. Distinctive:

    Keep evidence and interpretation separate.

    line 42

“Common” is measured: kept by at least 6 in 10 of the 104 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

Research before recommending copy.

Workflow

  1. Define the user decision the page or product must help with.
  2. Search current market language, competing products, public-sector guidance, user questions, and relevant community discussions.
  3. Separate:
    • verified market facts,
    • competitor claims,
    • user language,
    • hypotheses.
  4. Identify the audience's real problem, not the category's marketing vocabulary.
  5. Produce concise implications for positioning, content, trust, and conversion.

ThiefDroppers rules

  • Treat ThiefDroppers as global from day one.
  • Use jurisdiction-specific material only as a local layer, never as the platform identity.
  • Prefer primary sources, regulators, major platforms, credible research, and recent public data.
  • For community sentiment, use original Reddit discussions when useful and label anecdotal evidence accordingly.
  • Never invent market size, adoption, loss figures, partnerships, user counts, or product capabilities.
  • Do not frame the product as antivirus, surveillance, a public suspect database, or an accusation engine.
  • Investigate user intent around jobs, recruiters, businesses, messages, websites, payments, coercion, identity misuse, and recovery.

Output

Return:

  • audience/problem,
  • market language,
  • competitors/alternatives,
  • trust gaps,
  • SEO/content implications,
  • recommended positioning.

Keep evidence and interpretation separate.

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.