Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

sales-6sense销售六感

Agent Skill

sales-6sense 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

847

周安装

36

GitHub Stars

13

下载量

297
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:sales-6sense(销售六感)
来源仓库:https://github.com/sales-skills/sales
仓库路径:skills/sales-6sense
安装命令:
npx skills add https://github.com/sales-skills/sales --skill sales-6sense
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/sales-skills/sales --skill sales-6sense

简介

sales-6sense 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。

  • 可结合来源仓库、安装命令和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • 当前顶部介绍为空,原始 SKILL.md 摘录未提供。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

6sense Platform Help

Help the user with 6sense platform questions — Signalverse Intent Data, Predictive Analytics, Sales Intelligence, AI Email Agents, Advertising & Audience Activation, Orchestration Workflows, Segments, APIs, and integrations.

Important context: 6sense is an enterprise ABM platform that combines proprietary intent data (Signalverse) with third-party signals (Bombora, G2, TrustRadius) and AI-driven predictions to identify in-market accounts and orchestrate multichannel engagement. It competes primarily with Demandbase and Bombora. Pricing is enterprise-level ($50K-$200K+/year) with custom quotes and 2-year minimum contracts.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

What area of 6sense do you need help with?

  • a) Signalverse Intent Data — understanding buying signals and topics
  • b) Predictive Analytics / 6AI Scoring — account scoring and buying stage predictions
  • c) Sales Intelligence — account prioritization, Sales Copilot, Chrome extension
  • d) AI Email Agents — automated personalized email outreach
  • e) Advertising — display ads, LinkedIn audience sync, retargeting
  • f) Orchestration / Workflows — multichannel campaign automation
  • g) Segments — dynamic audience building and activation
  • h) Company Identification — IP-to-company matching for website visitors
  • i) APIs — Company Identification, People Enrichment, Firmographics, Segments
  • j) Integrations — CRM, MAP, ad platforms
  • k) Something else

What's your role?

  • a) Marketing (demand gen, ABM, campaigns)
  • b) Sales (AE, SDR, sales ops)
  • c) Revenue operations / GTM ops
  • d) Technical (API integration, data engineering)
  • e) Leadership (CMO, CRO, VP)

What's your goal?

  • a) Identify in-market accounts to prioritize
  • b) Launch account-based advertising campaigns
  • c) Set up AI email agents for automated outreach
  • d) Build predictive scoring models
  • e) Integrate 6sense data into CRM/MAP
  • f) Compare 6sense to alternatives (Demandbase, Bombora)
  • g) Optimize existing 6sense setup

Step 2 — Route or answer directly

If the question is about intent signal strategy across tools (not 6sense-specific) — hand off: "This is an intent signal strategy question — run: /sales-intent {user's original question}" If the question is about lead scoring strategy across tools — hand off: "This is a lead scoring strategy question — run: /sales-lead-score {user's original question}" If the question is about enrichment strategy across tools — hand off: "This is an enrichment strategy question — run: /sales-enrich {user's original question}" If the question is about B2B advertising strategy across tools — hand off: "This is a B2B advertising strategy question — run: /sales-b2b-advertising {user's original question}" If the question is about outbound cadence/sequence strategy — hand off: "This is a cadence/sequence design question — run: /sales-cadence {user's original question}" If the question is about building prospect lists across tools — hand off: "This is a prospect list building question — run: /sales-prospect-list {user's original question}" If the question is about connecting 6sense to other tools — hand off: "This is a tool integration question — run: /sales-integration {user's original question}"

Otherwise, answer directly using the reference below.

Step 3 — 6sense platform reference

Read references/platform-guide.md for detailed module documentation, pricing, integrations, and data model.

*You no longer need the platform guide details — focus on the user's specific situation.*

Step 4 — Actionable guidance

Gotchas

*Best-effort from research — review these, especially items about plan-gated features and pricing that may be outdated.*

  • Enterprise pricing only: 6sense has no self-serve paid plan. The Free plan (50 credits/mo) is very limited. Paid plans start around $50K/year with 2-year minimum contracts and custom quotes. Don't recommend 6sense to SMBs or teams without enterprise budgets — suggest Bombora (standalone intent data, ~$25K/year) or Apollo.io (intent included in lower-cost plans) instead.
  • Free plan is a teaser, not a tool: The Free tier (50 credits/mo) gives access to basic search and Chrome extension but NOT intent data, predictive scoring, advertising, AI email, or workflows. Don't assume free users can access core 6sense features.
  • Intent data requires tuning: Out-of-the-box intent topics are broad and noisy. You must configure relevant topics and regularly refine them based on conversion data. Untuned intent data generates false positives that waste sales time.
  • API docs behind auth wall: 6sense's support documentation (support.6sense.com) requires authentication to view actual content. The API endpoints and schemas documented here are best-effort from public sources — verify against your org's API portal for exact specifications.
  • AI Email Agents are a separate add-on: Conversational Email / AI Email Agents are not included in all paid plans. They're a distinct product with separate pricing. Don't assume they're available to all 6sense customers.
  • Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.

Step 5 — Related skills

  • /sales-intent — Buying signals and account prioritization strategy across tools (6sense Signalverse is one option)
  • /sales-lead-score — Lead scoring model design using intent + fit signals
  • /sales-enrich — Enrichment strategy across tools (6sense People/Company APIs are one source)
  • /sales-b2b-advertising — Account-based B2B advertising strategy (6sense Ads is one platform)
  • /sales-cadence — Outbound sequence design (6sense AI Email Agents is one option)
  • /sales-prospect-list — Build prospect lists (6sense Company Discovery is one source)
  • /sales-integration — Connect 6sense to CRM, MAP, and other tools
  • /sales-zoominfo — ZoomInfo platform help (primary competitor for enrichment + intent)
  • /sales-clearbit — Clearbit platform help (enrichment + Reveal visitor ID)
  • /sales-rb2b — RB2B platform help (person-level visitor ID — complements 6sense company-level ID)
  • /sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do

Examples

Example 1: Set up 6sense for ABM

User says: "We just bought 6sense and need to set it up for account-based marketing. Where do we start?" Skill does: Walks through WebTag installation, intent topic configuration, ICP definition, initial segment creation, CRM integration (Salesforce/HubSpot), Sales Intelligence deployment (Chrome extension + Sales Copilot), and first advertising campaign launch. Recommends starting with a small target account list to validate signal quality before scaling. Result: Phased 6sense implementation plan with quick wins in the first 30 days

Example 2: 6sense vs Demandbase comparison

User says: "We're evaluating 6sense and Demandbase for our ABM program. What are the key differences?" Skill does: Compares intent data (6sense proprietary Signalverse vs Demandbase's Bombora-dependent approach), advertising (Demandbase's deeper ad roots vs 6sense's improving ads), predictive scoring (6sense's buying stage predictions vs Demandbase's account scoring), AI email (6sense has AI Email Agents, Demandbase does not), pricing (both $50K-200K+ range, custom quotes, multi-year contracts), and CRM integrations. Recommends 6sense if predictive scoring and AI email are priorities, Demandbase if advertising is the primary use case. Result: Clear comparison with recommendation based on the user's primary use case

Example 3: Integrate 6sense API for custom enrichment

User says: "I want to use the 6sense API to enrich our inbound leads with intent data and buying stage before they hit our CRM." Skill does: Explains the People Enrichment API endpoint (scribe.6sense.com/v2/people/Enrichment), authentication with org-level API tokens, how to pass email/company to get contact + firmographic data, the Segments API for buying stage data, and how to chain Company Identification + Enrichment for a complete picture. Notes that API credits are consumed per call and should be budgeted. Result: Working API integration plan for real-time lead enrichment with 6sense data

Troubleshooting

Intent data shows too many accounts

Symptom: Hundreds of accounts flagged as "in-market" but sales can't follow up on all of them Cause: Intent topics are too broad, or 6QA thresholds are too permissive Solution: Narrow intent topics to your specific category keywords (not broad industry terms). Raise the 6QA threshold by requiring higher intent scores or later buying stages (Consideration+). Layer ICP firmographic filters on top of intent to reduce noise. Focus on signal trends (increasing) rather than absolute scores.

Sales team ignoring 6sense alerts

Symptom: Sales Intelligence is deployed but reps aren't acting on recommendations Cause: Too many low-quality alerts, alerts not actionable, or reps don't understand the data Solution: Reduce alert volume by raising thresholds (only alert on Decision+ stage or strong intent spikes). Include specific talk tracks and account context in alerts (not just "intent detected"). Train reps on what buying stages mean and how to use insights in outreach. Start with top performers as champions, then expand.

LinkedIn audience sync has low match rates

Symptom: 6sense segments synced to LinkedIn Campaign Manager show small audience sizes Cause: Segments are too narrow, or LinkedIn can't match all accounts/contacts in the segment Solution: Broaden segment criteria slightly (e.g., add adjacent industries or expand company size range). Ensure contact-level data is populated in 6sense (LinkedIn matches on people, not just accounts). Use 6sense's "lookalike" audience expansion if available. Check that segments have enough volume — LinkedIn typically requires 300+ contacts minimum for campaign delivery.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.87%
按下载量换算104

Claude

32.77%
按下载量换算97

Cursor

17.7%
按下载量换算53

Gemini CLI

10.06%
按下载量换算30

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills