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

assign-unowned-contacts分配无主联系人

Agent Skill

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

总安装

190

周安装

8

GitHub Stars

14

下载量

67
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:assign-unowned-contacts(分配无主联系人)
来源仓库:https://github.com/tomgranot/hubspot-admin-skills
仓库路径:skills/assign-unowned-contacts
安装命令:
npx skills add https://github.com/tomgranot/hubspot-admin-skills --skill assign-unowned-contacts
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/tomgranot/hubspot-admin-skills --skill assign-unowned-contacts

简介

assign-unowned-contacts 用于为 HubSpot 中无主的营销联系人分配负责人,避免数据盲区和跟进断档。

  • 适用于需要清理联系人归属、完善线索流转或优化营销效果归因的场景。
  • 通过自动化脚本批量处理,可结合权限与报表需求谨慎使用。
  • 安装前需确认仓库维护状态及是否涉及敏感数据操作。
  • 建议先在小范围测试,并确保有回滚机制。

SKILL.md

Assign Unowned Marketing Contacts

Assign an owner to all marketing contacts that currently have no owner. Unowned contacts create gaps in reporting, prevent proper lead routing, and mean no one is accountable for follow-up on marketing-generated responses.

Why This Matters

Marketing contacts without an owner are a blind spot. They receive campaigns but no one sees their responses. They appear in aggregate metrics but not in individual pipeline views. In owner-based dashboards and reports, they simply do not exist. For teams using round-robin or territory-based routing, unowned contacts bypass the entire system.

Prerequisites

  • Phase 1 hygiene and earlier Phase 3 enrichment processes completed
  • Access to Contacts with permission to bulk edit owner assignments
  • Approval from team leads before bulk assignment. This is a business decision, not just a technical one. Get sign-off on the assignment strategy before proceeding.

Interview: Gather Requirements

Before executing, collect the following information from the user:

Q1: Who should unowned contacts be assigned to?

  • Examples: "Assign all to our Integration User", "Distribute across the sales team", "Assign to the Marketing Team user", "Assign to specific reps by territory"
  • Default: No default -- this is a business decision that requires team lead approval

Q2: Should we use territory-based routing, round-robin, or a single catch-all owner?

  • Examples: Territory-based (assign by geography or industry), round-robin (distribute evenly across active reps), catch-all (assign all to one user)
  • Default: Catch-all to a single integration/service user as a temporary measure, with plans to implement proper routing later

Plan

  1. Identify all marketing contacts with no owner (before state)
  2. Decide on the assignment strategy (catch-all user vs. territory rules)
  3. Execute the bulk assignment
  4. Verify all marketing contacts have owners (after state)

Before State

Create the Unowned Marketing Contacts List

  1. Go to Contacts > Lists > Create list
  2. Select Active list
  3. Name: CLEANUP: Unowned Marketing Contacts
  4. Add filters:

- Marketing contact status > is any of > Marketing contact - AND Contact owner > is unknown

  1. Save the list and note the count

Script Approach

import os
from hubspot import HubSpot
from dotenv import load_dotenv

load_dotenv()
api_client = HubSpot(access_token=os.getenv("HUBSPOT_API_TOKEN"))

# Count unowned marketing contacts
result = api_client.crm.contacts.search_api.do_search(
    public_object_search_request={
        "filterGroups": [{
            "filters": [
                {
                    "propertyName": "hs_marketable_status",
                    "operator": "EQ",
                    "value": "true"
                },
                {
                    "propertyName": "hubspot_owner_id",
                    "operator": "NOT_HAS_PROPERTY"
                }
            ]
        }],
        "limit": 0
    }
)
print(f"Unowned marketing contacts: {result.total}")

Execute

Assignment Strategy Decision

Choose one of these approaches (requires team lead approval):

Option A: Catch-All User (Simplest)

  • Assign all unowned contacts to a single integration/service user
  • Pro: Fast, ensures 100% coverage immediately
  • Con: One "owner" accumulates a large number of contacts; not meaningful for routing
  • Best when: You plan to implement proper routing later and just need coverage now

Option B: Territory/Region Rules

  • Assign based on contact geography, industry, or company size
  • Pro: More meaningful ownership, better for sales follow-up
  • Con: Requires a defined routing matrix and more complex execution
  • Best when: You have established sales territories

Option C: Round-Robin

  • Distribute evenly across active sales reps
  • Pro: Fair distribution, immediate accountability
  • Con: May assign contacts to reps who do not cover that segment
  • Best when: Small team, all reps handle all segments

Bulk Assignment via UI

  1. Open the unowned marketing contacts list
  2. Click the checkbox in the table header to select all contacts on the page
  3. Click Select all X contacts to select across all pages
  4. Click Edit in the toolbar
  5. In the property dropdown, select Contact owner
  6. Search for and select the chosen owner
  7. Click Update
  8. Confirm the bulk edit
  9. For large numbers (5,000+), HubSpot processes in batches. This may take several minutes.

Bulk Assignment via API

# Pattern for API-based assignment
# Useful for territory-based rules or when UI bulk edit times out

OWNER_ID = "your-owner-id"  # Get from Owners API

# 1. Search for unowned marketing contacts (paginate through all)
# 2. Build batch update payload with hubspot_owner_id = OWNER_ID
# 3. Submit in batches of 100 via crm.contacts.batch_api.update

# For territory-based routing:
# 1. Search for unowned marketing contacts
# 2. For each contact, determine territory based on country/state/industry
# 3. Map territory to owner ID
# 4. Batch update with the appropriate owner per contact

API notes:

  • Get owner IDs from the Owners API: api_client.crm.owners.owners_api.get_page()
  • To find a specific owner by email: iterate through owners and match on email
  • Batch update accepts up to 100 records per call
  • Rate limit: 100 requests per 10 seconds

After State

Wait 5-10 minutes for HubSpot to finish processing, then verify.

# Re-run the same search
result = api_client.crm.contacts.search_api.do_search(
    public_object_search_request={
        "filterGroups": [{
            "filters": [
                {
                    "propertyName": "hs_marketable_status",
                    "operator": "EQ",
                    "value": "true"
                },
                {
                    "propertyName": "hubspot_owner_id",
                    "operator": "NOT_HAS_PROPERTY"
                }
            ]
        }],
        "limit": 0
    }
)
print(f"Unowned marketing contacts: {result.total} (should be 0)")

Verification checklist:

  1. The unowned marketing contacts list shows 0 contacts
  2. Re-run the before-state script — count should be 0
  3. Spot-check 5-10 contacts that were previously unowned — confirm they show the assigned owner
  4. Check owner-based dashboards/reports to confirm the previously invisible contacts now appear

Key Technical Learnings

  • This is a business decision, not just a technical one. Always get approval from sales/marketing leadership on the assignment strategy before executing. Bulk-assigning contacts to the wrong people creates confusion and erodes trust.
  • A catch-all user is a temporary solution. If you assign to a single integration user, plan a follow-up process to redistribute contacts to actual sales reps when proper routing is established.
  • Pair with lead owner cleanup. Once proper routing is in place, revisit contacts under the catch-all user and reassign them to real owners.
  • HubSpot bulk edit limits. For very large batches (10,000+), the UI bulk edit may time out. Use the API approach instead, which handles pagination and batching gracefully.
  • New contacts need routing too. After this one-time cleanup, implement a workflow or lead rotation rule to automatically assign owners to new marketing contacts going forward.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

36.17%
按下载量换算24

Claude

28.37%
按下载量换算19

Cursor

18.84%
按下载量换算13

Gemini CLI

7.85%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills