القائمة
Activate contact-level signal tracking using the Saber CLI — creates signals for contacts in a contact list.
التثبيت باستخدام 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 | create-contact-signals |
| description | Activate contact-level signal tracking using the Saber CLI — creates signals for contacts in a contact list. |
Use this skill to run contact-level signal research using the Saber CLI.
Before doing anything else, check if the Saber CLI is installed by running saber --help.
If the CLI is available: proceed with the full workflow below.
If not installed: inform the user that this skill requires the Saber CLI to execute signals (available at saber.app), then offer two options:
signal-discovery first if not)saber --help works)Before executing any saber signal or saber subscription command that will consume credits:
saber credits and show the user their current balance.Use saber signal with a LinkedIn profile URL to run a question against a specific contact:
saber signal --profile <linkedin-url> --question "<signal question>"
This is synchronous by default — it waits for the result and prints it.
# Example
saber signal --profile https://linkedin.com/in/janedoe --question "Is this person posting about employee retention challenges?"
Use --no-wait to fire multiple signals without waiting:
saber signal --profile <linkedin-url> --question "<question>" --no-wait
# Returns a signal ID; retrieve result later with:
saber signal get <signalId>
For running signals across a large contact list, use signal subscriptions in the Saber dashboard or via the API. The CLI currently supports per-contact signals only.
Ask the user which contacts they want to prioritise. You'll need LinkedIn profile URLs.
For each contact and each approved signal question:
saber signal --profile <linkedin-url> --question "<question>" --answer-type boolean
Present results to the user. Contacts where the signal fired positively should be sequenced first for outreach.
saber signal --profile <linkedin-url> --question "<question>" [--answer-type] [--no-wait]
saber signal get <signalId>