New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Run structured B2B research prompts from the Markster OS

Research Operator

by markster · MIT license · ★ 64 on GitHub · updated May 15

Research Operator cover

Run structured B2B research prompts from the Markster OS library. CHECK what they are trying to learn and ICP context.

---
name: research
description: 'Run structured B2B research prompts from the Markster OS library. CHECK what they are trying to learn and ICP context. DO one or more of 9 prompts (competitive intelligence, buyer JTBD, buying signals, pricing perception, GTM channels, objection research, market positioning, mental category positioning, first 60 seconds). VERIFY output is documented back into Foundation.'
---

# Research Operator

---

## CHECK

Do not proceed past any failed check.

**1. What are they trying to learn?**

Ask the user one question before running anything: "What specific decision or action does this research need to inform?"

If they cannot answer: "Research without a decision to feed is noise. Tell me what you are trying to do -- write a cold email, define your positioning, prepare for a sales call -- and I will route you to the right prompt."

Overview

Ask the user one question before running anything: "What specific decision or action does this research need to inform?"

Manual install (npx, ZIP)
Claude Codenpx skills add markster/markster-os --skill research -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/markster/markster-os/tar.gz/b1da50054715 \ | tar -xz -C ~/.claude/skills --strip-components=2 markster-os-b1da50054715/skills/research
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/31b1988bac8756ba321a/research.zip" -OutFile "$env:TEMP\research.zip"; Expand-Archive "$env:TEMP\research.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md5.7 KB
Read the files here
markster/b1da5001 file
Shared references10SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text117 lines

Research Operator


CHECK

Do not proceed past any failed check.

1. What are they trying to learn?

Ask the user one question before running anything: "What specific decision or action does this research need to inform?"

If they cannot answer: "Research without a decision to feed is noise. Tell me what you are trying to do -- write a cold email, define your positioning, prepare for a sales call -- and I will route you to the right prompt."

2. ICP context

Ask: "Do you have an ICP defined, even partially? Prompts with more specific inputs produce more usable outputs."

  • Full F1 complete: proceed directly to prompt selection
  • Partial F1 (know company type + title but not buying trigger): proceed, prompt will surface buying trigger
  • No F1 at all: run the Buyer JTBD prompt first -- it will define the language and signals needed for F1

3. Existing knowledge

Ask: "What do you already know about your buyer and market? Any verbatims from clients or prospects, any competitor claims you have seen, any objections that keep coming up?"

Existing knowledge prevents duplicate work and makes prompts more specific.


DO

Present the menu and ask which the user wants to run. Multiple prompts can be run in one session if the decision being informed is broad enough.

The 9 research prompts
# Prompt When to run it
1 Competitive intelligence Before writing any cold email or content. Understand what the buyer is already seeing from competitors.
2 Buyer JTBD When building F1 or the messaging guide. Surfaces the buyer's language, functional goals, emotional goals.
3 Buying signals When defining the buying trigger for F1. What to look for when building a list.
4 Pricing perception When building F2. How your ICP thinks about price, what they compare you against.
5 GTM channels When choosing channels. Where your ICP trusts discovery and learns about vendors.
6 Objection research Before writing cold email sequences. Surface what you will encounter in replies.
7 Market positioning When defining your messaging. Find the white space.
8 Mental category positioning When differentiating from alternatives. How buyers categorize solutions like yours.
9 First 60 seconds Before events, sales calls, or any live conversation with an ICP.
Running a prompt

When the user selects a prompt:

  1. Open the corresponding file in research/prompts/
  2. Ask the user to provide the variables the prompt requires -- ICP description, company category, competitive names, whatever the prompt needs
  3. Fill in the variables with their context and run the prompt
  4. Produce specific, usable output -- not a summary, not a framework description, actual findings they can act on

Do not run a prompt with empty variables. Generic inputs produce generic outputs. Push back until the variables are specific.

Prompt files
Prompt File
Competitive intelligence research/prompts/competitive-intelligence-prompt.md
Buyer JTBD research/prompts/buyer-jobs-to-be-done-prompt.md
Buying signals research/prompts/buying-signals-trigger-events-prompt.md
Pricing perception research/prompts/pricing-value-perception-prompt.md
GTM channels research/prompts/gtm-channel-effectiveness-prompt.md
Objection research research/prompts/ai-agency-objections-prompt.md
Market positioning research/prompts/market-positioning.md
Mental category positioning research/prompts/mental-category-positioning-prompt.md
First 60 seconds research/prompts/first-60-seconds-messaging-prompt.md

VERIFY

Before this session ends:

1. Output is documented in the correct file?

Route findings to the right destination -- do not leave research in the chat only.

Finding type Where it goes
Buyer verbatims (exact phrases buyers use) methodology/foundation/messaging-guide.md -- problem statement section
Buying signals and trigger events company-context/audience.md -- situational layer in F1
Objections playbooks/biz-dev/sales/templates/objections.md
Competitor claims and positioning company-context/messaging.md -- differentiation section
Pricing perception patterns company-context/offer.md -- pricing rationale in F2
White space / positioning gaps methodology/foundation/messaging-guide.md -- mechanism section

2. Buyer verbatims captured?

If the prompt surfaces exact phrases buyers use to describe their problem -- capture them verbatim. These are the highest-value output from any research session. They belong in the messaging guide and should feed directly into cold email and content.

3. Decision informed?

Confirm the research answers the decision from CHECK step 1. If not, identify which prompt would close the gap and either run it now or schedule it.

4. Next prompt recommended?

Each research output typically reveals a second question. Name it: "Based on what we found, the next most useful research would be [prompt] because [reason]."


Reference files

  • Research library: research/README.md
  • Messaging guide: methodology/foundation/messaging-guide.md
  • F1 Positioning: methodology/foundation/F1-positioning.md
  • Objection scripts: playbooks/biz-dev/sales/templates/objections.md
1---
2name: research
3description: 'Run structured B2B research prompts from the Markster OS library. CHECK what they are trying to learn and ICP context. DO one or more of 9 prompts (competitive intelligence, buyer JTBD, buying signals, pricing perception, GTM channels, objection research, market positioning, mental category positioning, first 60 seconds). VERIFY output is documented back into Foundation.'
4---
5 
6# Research Operator
7 
8---
9 
10## CHECK
11 
12Do not proceed past any failed check.
13 
14**1. What are they trying to learn?**
15 
16Ask the user one question before running anything: "What specific decision or action does this research need to inform?"
17 
18If they cannot answer: "Research without a decision to feed is noise. Tell me what you are trying to do -- write a cold email, define your positioning, prepare for a sales call -- and I will route you to the right prompt."
19 
20**2. ICP context**
21 
22Ask: "Do you have an ICP defined, even partially? Prompts with more specific inputs produce more usable outputs."
23 
24- Full F1 complete: proceed directly to prompt selection
25- Partial F1 (know company type + title but not buying trigger): proceed, prompt will surface buying trigger
26- No F1 at all: run the Buyer JTBD prompt first -- it will define the language and signals needed for F1
27 
28**3. Existing knowledge**
29 
30Ask: "What do you already know about your buyer and market? Any verbatims from clients or prospects, any competitor claims you have seen, any objections that keep coming up?"
31 
32Existing knowledge prevents duplicate work and makes prompts more specific.
33 
34---
35 
36## DO
37 
38Present the menu and ask which the user wants to run. Multiple prompts can be run in one session if the decision being informed is broad enough.
39 
40### The 9 research prompts
41 
42| # | Prompt | When to run it |
43|---|--------|----------------|
44| 1 | **Competitive intelligence** | Before writing any cold email or content. Understand what the buyer is already seeing from competitors. |
45| 2 | **Buyer JTBD** | When building F1 or the messaging guide. Surfaces the buyer's language, functional goals, emotional goals. |
46| 3 | **Buying signals** | When defining the buying trigger for F1. What to look for when building a list. |
47| 4 | **Pricing perception** | When building F2. How your ICP thinks about price, what they compare you against. |
48| 5 | **GTM channels** | When choosing channels. Where your ICP trusts discovery and learns about vendors. |
49| 6 | **Objection research** | Before writing cold email sequences. Surface what you will encounter in replies. |
50| 7 | **Market positioning** | When defining your messaging. Find the white space. |
51| 8 | **Mental category positioning** | When differentiating from alternatives. How buyers categorize solutions like yours. |
52| 9 | **First 60 seconds** | Before events, sales calls, or any live conversation with an ICP. |
53 
54### Running a prompt
55 
56When the user selects a prompt:
571. Open the corresponding file in `research/prompts/`
582. Ask the user to provide the variables the prompt requires -- ICP description, company category, competitive names, whatever the prompt needs
593. Fill in the variables with their context and run the prompt
604. Produce specific, usable output -- not a summary, not a framework description, actual findings they can act on
61 
62Do not run a prompt with empty variables. Generic inputs produce generic outputs. Push back until the variables are specific.
63 
64### Prompt files
65 
66| Prompt | File |
67|--------|------|
68| Competitive intelligence | `research/prompts/competitive-intelligence-prompt.md` |
69| Buyer JTBD | `research/prompts/buyer-jobs-to-be-done-prompt.md` |
70| Buying signals | `research/prompts/buying-signals-trigger-events-prompt.md` |
71| Pricing perception | `research/prompts/pricing-value-perception-prompt.md` |
72| GTM channels | `research/prompts/gtm-channel-effectiveness-prompt.md` |
73| Objection research | `research/prompts/ai-agency-objections-prompt.md` |
74| Market positioning | `research/prompts/market-positioning.md` |
75| Mental category positioning | `research/prompts/mental-category-positioning-prompt.md` |
76| First 60 seconds | `research/prompts/first-60-seconds-messaging-prompt.md` |
77 
78---
79 
80## VERIFY
81 
82Before this session ends:
83 
84**1. Output is documented in the correct file?**
85 
86Route findings to the right destination -- do not leave research in the chat only.
87 
88| Finding type | Where it goes |
89|-------------|--------------|
90| Buyer verbatims (exact phrases buyers use) | `methodology/foundation/messaging-guide.md` -- problem statement section |
91| Buying signals and trigger events | `company-context/audience.md` -- situational layer in F1 |
92| Objections | `playbooks/biz-dev/sales/templates/objections.md` |
93| Competitor claims and positioning | `company-context/messaging.md` -- differentiation section |
94| Pricing perception patterns | `company-context/offer.md` -- pricing rationale in F2 |
95| White space / positioning gaps | `methodology/foundation/messaging-guide.md` -- mechanism section |
96 
97**2. Buyer verbatims captured?**
98 
99If the prompt surfaces exact phrases buyers use to describe their problem -- capture them verbatim. These are the highest-value output from any research session. They belong in the messaging guide and should feed directly into cold email and content.
100 
101**3. Decision informed?**
102 
103Confirm the research answers the decision from CHECK step 1. If not, identify which prompt would close the gap and either run it now or schedule it.
104 
105**4. Next prompt recommended?**
106 
107Each research output typically reveals a second question. Name it: "Based on what we found, the next most useful research would be [prompt] because [reason]."
108 
109---
110 
111## Reference files
112 
113- Research library: `research/README.md`
114- Messaging guide: `methodology/foundation/messaging-guide.md`
115- F1 Positioning: `methodology/foundation/F1-positioning.md`
116- Objection scripts: `playbooks/biz-dev/sales/templates/objections.md`
117 
View all files on GitHub →

Details

Updated
May 15, 2026
License
MIT
Stars on the repo
★ 64
Checked
Source
markster/markster-os ↗
Creator
markster · 7 listings
View creator

Similar skills

See all →
SkillBrand voice, visual identity, messaging frameworksnextlevelbuilder/ui-ux-pro-max-skill · by nextlevelbuilderBrand voice, visual identity, messaging frameworks, asset management, brand consistency. Activate for branded content, tone of voice, marketing assets, brand compliance, style guides.★ 130k GitHub starsSkillMap what our buyers believeAudience belief mapperaaron-he-zhu/aaron-marketing-skills · by aaron-he-zhuUse when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言★ 2.9k GitHub starsSkillPaste in your website and marketing copyBrand Voice Analysis and Guidelines Generationzubair-trabzada/ai-marketing-claude · by zubair-trabzadaPaste in your website and marketing copy, and get back a clear guide anyone on your team can follow to sound like your brand every time.★ 2.7k GitHub starsSkillYour brand designerFounder brandJakeschincariol/founder-skill · by JakeschincariolYour brand designer. Names the business (with the trademark, domain and handle checks to run before falling in love with a name), writes the voice, a one-line promise and a tagline, and briefs the look: colours, type, logo and the first things a customer sees, so they match the positioning the marketing director chose. Use when the user says "name my business", "brand this", "logo", "brand identity", "what should it look like", "tagline", or "brand voice".★ 322 GitHub starsSkillAnalyze and rewrite content to strict brand voice guidelinesBrand voice enforcerwriter/skills · by writerAnalyze and rewrite content to strict brand voice guidelines, scoring adherence across tone, vocabulary, syntax patterns, and persona alignment for CPG and retail brands.★ 7 GitHub starsSkillAdapt one core brand voice coherently across every adBrand voice ad adaptationgmmh1/claude-paid-media-skills · by gmmh1Adapt one core brand voice coherently across every ad platform's native register — professional on LinkedIn, native/casual on TikTok, conversational on Meta, direct on Google Search. Triggers on 'does this still sound like us', 'adapt our brand voice for TikTok', 'keep our voice consistent across ad platforms', or 'this ad doesn't sound on-brand'. Cross-platform consistency layer feeding every platform's copywriting skill.New listing

More from markster

SkillRun the Markster OS cold email playbookCold Email Operatormarkster/markster-os · by marksterRun the Markster OS cold email playbook. CHECK prerequisites, DO the sequence build, VERIFY before sending. Routes through ScaleOS G3 Book with context from F1/F2.★ 64 GitHub starsSkillRun the Markster OS content playbookContent Operatormarkster/markster-os · by marksterRun the Markster OS content playbook. CHECK prerequisites (ICP, messaging guide, platform, time), DO theme definition + 30-day calendar + writing + distribution, VERIFY output before declaring done. Routes through ScaleOS G2 Warm.★ 64 GitHub starsSkillRun the Markster OS events playbookEvents Operatormarkster/markster-os · by marksterRun the Markster OS events playbook. CHECK prerequisites (ICP, offer, specific event), DO pre-event targeting + during-event conversation system + post-event follow-up, VERIFY before leaving the event pipeline empty. Routes through ScaleOS G2 Warm.★ 64 GitHub starsSkillRun the Markster OS fundraising playbookFundraising Operatormarkster/markster-os · by marksterRun the Markster OS fundraising playbook. CHECK stage, traction, and funding path before building anything. DO investor ICP + list + outreach + pitch + close. VERIFY investor pipeline is real before claiming readiness. Routes through ScaleOS Biz Dev.★ 64 GitHub starsSkillDiagnostic operator for Markster OSMarkster OS Operatormarkster/markster-os · by marksterDiagnostic operator for Markster OS. Identifies the constraint brick, runs the Hormozi diagnostic, and routes to the right playbook with context pre-filled. Run this before any other skill.★ 64 GitHub starsSkillRun the Markster OS sales playbookSales Operatormarkster/markster-os · by marksterRun the Markster OS sales playbook. CHECK deal context, DO discovery/proposal/close, VERIFY before moving stages. Includes 9 Kill Skills audit for conversion problems.★ 64 GitHub stars