メニュー
Guided entry point for defining your ICP and buying signals — runs extract-icp then generate-signals in sequence. Start here before creating signals or building lists.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Activate company-level signal tracking. Runs signals via the Saber CLI if available; without it, outputs a research playbook and suggests alternative tracking methods.
Generate 12–15 structured, weighted research signals from a structured ICP, ready to activate in Saber. Each signal includes answer type, weight, and interpretation rules for automatic scoring.
Deep research on a single company — signals, hiring, news, tech stack, and LinkedIn presence. Uses the Saber CLI for signal data and any available MCP tools for broader research.
End-to-end guided workflow — take one prospect domain, run your saved research signals, find named contacts on the buying committee, and write a hyper-personalised cold email and LinkedIn DM grounded in the signal answers. First run defines the source-company ICP, contact-search targets, and ≤5 weighted signals (saved to disk); every subsequent run reuses them. Use when you want full SDR research-and-write for a single prospect, not write-outreach in isolation.
End-to-end guided workflow — build a Saber company list, run research signals across every company in parallel, find named contacts, and export a combined CSV to the desktop. Walks the user through each stage with confirmations and a credit-discipline guard. Use when you want one signed-off CSV instead of running build-account-list, create-company-signals, and build-contact-list separately.
Build a target account list and run company signals against it. Works with the Saber CLI, Apollo, HubSpot, or any available prospecting tool — with a manual fallback.
| name | signal-discovery |
| description | Guided entry point for defining your ICP and buying signals — runs extract-icp then generate-signals in sequence. Start here before creating signals or building lists. |
Use this skill as the starting point for signal-based prospecting. It loads your organisation
context, then runs extract-icp and generate-signals in sequence to produce a complete,
scored signal set ready to activate in Saber.
Run saber --help to check if the Saber CLI is installed.
If the CLI is available: proceed with the full workflow below.
If not installed: inform the user that this skill works best with the Saber CLI (available at saber.app), then offer two options:
saber org get and ask for org context manually;
the ICP extraction and signal generation steps work fully without the CLIWith CLI: run saber org get
saber org update --name "..." --general "..." --products "..." --use-cases "..." --value-prop "..."
Without CLI: ask the user:
Do not ask questions already answered by available context (e.g. CLAUDE.md).
Use the extract-icp skill with the company's domain.
This produces a structured ICP covering: target company profile, buying committee, deal economics, pain points, buying triggers, and existing customers.
Keep the ICP output in conversation context for the next step.
Use the generate-signals skill with the ICP from Step 2.
This produces 12–15 research signals across three categories:
icp_fit — does the company profile match?urgency — did a recent trigger event happen?buying_signal — is there evidence of the pain?Each signal includes answer type, weight (1–3), disqualifier flag, and interpretation rules needed for automatic scoring.
Confirm the signal set with the user before handing off. Adjust any signals that don't fit.
Keep the agreed ICP and signal definitions in conversation context.
Once signals are approved, tell the user their next steps:
build-account-list or build-contact-listcreate-company-signalscreate-contact-signalsconfigure-scoring (translates categories to dimensions and weights to point values)score-accounts to rank accounts by current fit + urgency scores