Research Agent

Research Competitor

Build a competitor sheet of their facts only, every item sourced, dated and confidence-rated. It covers the feature inventory with depth, case studies in their customers' words, named customers, who they attack on their vs and alternatives pages, evidence of switching, and integrations, time-to-value and support. It reads the workspace first, their own site second, and pays for web search last. Use when the user needs a competitor sheet, competitor research, "what does X actually have", their case studies or customers, or who switched to or from them. Do not use when the need is a deal-ready battlecard or talk tracks (use @file:competitive-battlecard), their published prices side by side (use @file:competitor-price-gap), the whole market (use @file:landscape-map), an internal SWOT (use @file:swot-analysis), or pre-call prospect prep (use @file:research-prospect).

Research Prospect

Pre-call prospect brief built on a point of view, with one thing the buyer does not know about their own customers, rivals or standing in AI answers, sourced pain hypotheses, and the real people in the room with their LinkedIn links. Use when prepping a discovery call, first meeting or outbound play on a net-new account, or when asked to research a prospect company. Do not use when researching an existing customer (use @file:research-customer), a competitor dossier (use @file:research-competitor) or market sizing (use @file:market-sizing).

Research Person

A profile of one person for any relationship (prospect, customer, partner, influencer, speaker), pinned to the right person first, built from what Loop already holds and their own public words, and ending in how to approach them for why we are meeting. Use when researching a contact, a meeting guest, a speaker or a buyer before a conversation, or when asked "who is this person". Do not use when researching their company (use @file:research-prospect or @file:research-customer), a competitor (use @file:research-competitor) or a partner company's fit (use @file:research-partner).

Research Customer

Customer intelligence brief for an existing account — history, expansion signals, stakeholder map, and the business context that changes your value to them. Use when prepping a QBR, renewal, or expansion conversation. Do not use when the need is pre-call research on a net-new prospect (use @file:research-prospect) or competitor intelligence (use @file:research-competitor).

Research Partner

Partnership evaluation that separates strategic narrative from operational reality — scored fit, revenue model, integration burden, and a go/no-go. Use when the user is evaluating an alliance, integration, or channel partner. Do not use when the deal involves equity (use @file:due-diligence) or the target is a competitor with no partnership intent (use @file:research-competitor).

Due Diligence

Investment or acquisition due diligence that inverts the thesis — hunts for reasons NOT to do the deal first, then lands a go/no-go with named red flags, severity, and conditions. Use when the user is evaluating an acquisition or investment target. Do not use when the need is a partnership fit assessment (use @file:research-partner) or competitor intelligence with no deal attached (use @file:research-competitor).

Dress App For Prospect

Turn a researched company into a document whose live Loop panels show THAT company's name and mark instead of the built-in demo names. Use when a deliverable should look like it was built for one named account — a pre-call leave-behind, a tailored one-pager, a personalized proposal appendix. Do not use to gather the intelligence itself (use @file:research-prospect first) or to write outbound copy (route to /sales).

Vendor Watch

Ongoing tracking of ONE named vendor or competitor across every channel — launches, pricing, positioning shifts, hiring signals, social and analyst chatter — reported as deltas since the last check with a running timeline. Use when the user wants to monitor a specific competitor or vendor over time, asks "what has X done lately," or maintains a watchlist. Do not use when the need is a full competitor dossier (use @file:research-competitor), a battlecard (route to /pmm), or a one-time impact read on a single development (use @file:gtm-impact-brief).

Market Requirements

Derive the market requirements a buyer holds before anyone decides what to build. Each one is a numbered need stated in the buyer's terms, cited to the evidence that the market demands it, with our honest status against it (built, partial, not built, or CONFIRM). Use when the user needs market requirements, buyer requirements for a market or segment, "what does this market need from a product like ours", or the requirements section of a Market Requirements Document. Do not use when the need is a product requirements doc or feature spec for a build (use prd-writing), a feature-by-feature comparison with competitors (use competitive-feature-analysis), a buyer persona (use customer-persona), or a market size (use market-sizing).

Competitor Price Gap

Lay competitors' published prices side by side on one unit, for the buyers who actually exist, and name the price range nobody serves. Every price is dated and sourced, "contact sales" stays a value rather than a guess, and each pricing page is kept current by a person following it in Loop. Use when the user needs competitor pricing, a price comparison, price points across a market, the pricing gap, or the price section of a Market Requirements Document. Do not use when the need is setting our own price or packaging (use pricing-packaging), announcing a price change (use pricing-communication), or a full profile of one competitor (use research-competitor).

Market Analysis & Requirements

Assemble a cited Market Requirements Document (MRD), the research a team reads before it writes PRDs or a go-to-market plan, by pulling each section from the skill that owns it rather than writing it again. It researches and reports; pricing, targets and strategy stay questions for a person. Use when the user needs an MRD, a market requirements document, "research this market before we plan", or the whole market picture (size, buyers, competitors, requirements, prices) in one cited document. Do not use when only one piece is wanted: the requirements alone (use market-requirements), a market size (use market-sizing), one competitor (use research-competitor), a persona (use customer-persona), or the go-to-market plan itself (use gtm-strategy).

Citation Report

Produce a source-backed research report where every load-bearing claim carries a numbered citation, a source-quality tier, and a calibrated confidence level. Use when the user needs a defensible, externally shareable report or evidence-graded analysis. Do not use when a fast two-page synthesis is the need (use @file:executive-summary) or when the ask is internal strategic assessment with no sourcing bar (use @file:swot-analysis).

Market Signal Sweep

Multi-source scan of the market — news, social platforms, influencers, and analyst/data signals — filtered for what a GTM team can act on, each item dated, sourced, and confidence-labeled. Use when the user asks what's happening in their market/space/category, wants a scan since a date, or needs raw findings before a digest or impact brief. Do not use when the need is a recurring formatted briefing (use @file:market-signal-digest), one development analyzed in depth (use @file:gtm-impact-brief), a durable-vs-hype verdict or market sizing (route to /strategy).

Market Signal Digest

Recurring, scannable market-signal digest for GTM teams — a fixed format the reader learns to trust, built to re-run on a cadence with only genuine deltas since the last edition, drawn from news, social, and influencer signal. Use when the user wants a weekly or periodic market briefing, a team newsletter section, or a standing "keep us posted" deliverable. Do not use when the need is a one-off deep scan (use @file:market-signal-sweep), analysis of a single development (use @file:gtm-impact-brief), or one vendor's history (use @file:vendor-watch).