--- name: signals description: Use for SignalSurf one-off public research, Company/People discovery and retained results. Existing saved-field completion uses Records/Sheets; continuing monitors use Listening. --- # Signalsurf Signals Before every request using this Skill, follow [version check and automatic update](../signalsurf/references/freshness.md), then use the current guidance. Read the [shared operating contract](../signalsurf/references/operating-contract.md) unless already loaded; a focused Skill uses the same context, actor, confirmation and result rules. Signals produce observed evidence. They do not automatically become CRM truth, a Listening, or a Campaign. For one-off keyword post research, including LinkedIn, or continuing a temporary search result, read [search and retained results](references/search-and-results.md). Stay in this research procedure when a returned reader belongs to the Tables tool family; saving into a Sheet is a separate requested outcome. 1. Start with `find_capabilities` when the source is ambiguous. Use search capabilities for net-new discovery. For research-only questions about known profiles/recent posts, follow [research and capture](../signalsurf/references/research-capture.md) using native `social_get`; `people_enrich` is for supported identity/Email enrichment, not a substitute for profile/posts research. 2. For Company/People discovery, provider choice, switching sources or TAM mapping, follow [lead sourcing](../signalsurf/references/lead-sourcing.md). Choose a named provider from customer requirements and the live schema's supported filters and dated limitations; each search uses that source only. Discover the live schema before choosing parameters: prefer native Company/People Lists when company_search/people_search expose listId/sourceListId. If the connected version lacks them, report that capability gap instead of silently duplicating Company Records into a Sheet. Reuse existing Records and retained results before spending on rediscovery. Distinguish observed evidence from inference and preserve source/time fields. 3. For requested lookup-based completion of existing List, Record or Sheet fields, follow [native Enrich](../signalsurf/references/enrichment.md) with the owning [Records](../records/SKILL.md) or [Sheets](../sheets/SKILL.md) procedure. Keep research-only work in this procedure. Reconcile ambiguous paid attempts before another route. 4. For standalone technology research, use `lookup_company_technologies` with one companyDomain. For standalone hiring research, use `search_hiring_signals` with companyDomains and/or jobTitles plus the requested age window and result limit. These two research tools retain their own confirmation and credit scope. To fill saved fields, use native Enrich: its internal AI chooses the relevant company, person, technology, hiring, job-change, social, web or authorized Knowledge research and owns persistence. Do not select a separate batch/writeback technology tool. Inspect the live schema, preserve attributed evidence, and report unsupported capabilities; the retired combined business_signal_search entry is compatibility-only. Existing saved-field completion still follows native Enrich above. 5. Save requested verified durable identities through [Records](../records/SKILL.md). Use [Listening](../listening/SKILL.md) only for requested continuing monitoring or existing collected Engagers, not one-off research. 6. Promote findings to a Project Thread when they validate/reject a hypothesis or change the next action. Routine search output stays in its resource/result history.