القائمة
Use when users ask to create, preview, inspect, enrich, import, refresh, monitor, export, or reuse persistent Exa Websets for GTM sourcing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when users need a first GTM plan, lack an approved GTM plan, need connector readiness, sender voice, demo CTA, send ramp, autopilot policy, or approval gates.
Use when users ask for Exa-backed company, market, competitor, news, account, public-proof, or buyer-context research for GTM decisions.
Use when users ask to generate, batch, score, dedupe, schema, export, or shortlist Exa/Websets account or lead lists from a confirmed ICP.
Use when users ask to find, verify, dedupe, score, or map Exa-backed buyers, experts, team members, public profiles, LinkedIn identities, or work-email candidates.
Use when users ask to plan, start, monitor, repair, scale, or learn from GTM, outbound, sales, sourcing, signal-card, Gmail followup, or campaign autopilot work.
Use when starting Memory Store-backed work, orienting an agent to company memory, using briefs or living docs, deciding whether to record a learning, or deciding whether a new brief is warranted. Requires Memory Store MCP.
| name | websets-sourcing |
| description | Use when users ask to create, preview, inspect, enrich, import, refresh, monitor, export, or reuse persistent Exa Websets for GTM sourcing. |
Use Exa Websets as the persistent sourcing and enrichment layer for GTM Agent. Production Websets sourcing requires a configured Exa API key; if auth is missing, stop and output setup steps plus the Webset spec.
checkin; use selected canonical brief context if provided by the main GTM agent, otherwise call list-briefs and select 0-3 relevant briefs; then recall campaign, ICP, exclusions, seed accounts, suppressions, and prior Webset IDs.company, person, article, research_paper, or custom.Websets MCP is separate from Exa Monitors. For monitors, use ../gtm-agent/references/monitors.md and record returned monitor IDs after approval.
Return: webset read, spec, status, quality notes, Memory Store mapping, and next action.
Do not create broad reusable Websets without approval. Do not commit secrets. Do not delete Websets unless explicitly asked. Do not mark rows draft-ready without complete planner fields or high-intent signal evidence. Do not create briefs for Webset rows, previews, enrichments, or async events; use Webset IDs, campaign artifacts, records, and a main-agent brief delta only when repeated results change future operating policy.