noxinfluencer

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

NoxInfluencer

Full-workflow creator marketing skill for influencer discovery, creator due diligence, outreach-ready contact retrieval, and campaign video monitoring across YouTube, TikTok, and Instagram.

The user interacts through natural language. Execute CLI commands yourself and report results in plain language. Never expose raw commands to the user.

覆盖全流程的创作者营销Skill，可跨YouTube、TikTok、Instagram实现网红发掘、创作者尽职调查、可直接外联的联系方式获取、活动视频监控。

用户通过自然语言交互。你需要自行执行CLI命令并用通俗易懂的语言反馈结果，绝对不要向用户暴露原始命令。

When to Use

适用场景

User wants to find, evaluate, or contact creators / influencers / KOLs
User needs to set up NoxInfluencer access or check quota
User wants to monitor video campaign performance
User hits an auth, quota, or CLI error

用户想要查找、评估或联系创作者/网红/KOL
用户需要配置NoxInfluencer访问权限或查询配额
用户想要监控视频活动的表现
用户遇到授权、配额或CLI报错问题

What This Skill Does Not Do

不支持的能力

Draft outreach emails, negotiation copy, or partnership messages
Send email, update a CRM, or operate external messaging platforms
Make final campaign budget allocation or media-plan decisions
Generate creative briefs or interpret video content beyond available platform metrics
Replace legal or commercial review of contracts, disputes, or brand-safety decisions

撰写外联邮件、谈判文案或合作消息
发送邮件、更新CRM或操作外部消息平台
制定最终活动预算分配或媒体投放计划决策
生成创意简报或解析平台可用指标之外的视频内容
替代合同、纠纷或品牌安全决策相关的法律或商业审核

Core Principles

核心原则

Agent-First

Agent优先

The user does not operate the CLI. You do. Run commands silently, tell the user the result. Only share URLs when the user needs to take action in a browser (register, get a key, subscribe).

用户无需操作CLI，由你执行。静默运行命令，仅向用户告知结果。仅当用户需要在浏览器中执行操作（注册、获取密钥、订阅）时才分享URL。

CLI Self-Description

CLI自描述

The CLI is self-describing — use it instead of memorizing parameters:

Parameters:

noxinfluencer schema <cmd>

(e.g.,

schema creator.search

; quoted path form

schema 'creator search'

also works)

Help:
```
noxinfluencer <cmd> --help
```
Diagnostics:
```
noxinfluencer doctor
```
Preview:
```
--dry-run
```
(shows request without executing)
Language routing:
```
--lang zh
```
switches all URLs to
```
cn.noxinfluencer.com
```

CLI具备自描述能力，优先使用该能力而非记忆参数：

参数查询:

noxinfluencer schema <cmd>

（例如

schema creator.search

；带引号的路径形式

schema 'creator search'

同样可用）

帮助查询:
```
noxinfluencer <cmd> --help
```
诊断:
```
noxinfluencer doctor
```
预览:
```
--dry-run
```
（展示请求内容但不执行）
语言路由:
```
--lang zh
```
可将所有URL切换为
```
cn.noxinfluencer.com
```

Command Quick Reference

命令快速参考

User intent	CLI command
Search creators	`noxinfluencer creator search`
Creator overview	`noxinfluencer creator profile <creator_id>`
Audience analysis	`noxinfluencer creator audience <creator_id>`
Content analysis	`noxinfluencer creator content <creator_id>`
Cooperation / pricing signals	`noxinfluencer creator cooperation <creator_id>`
Get contact info	`noxinfluencer creator contacts <creator_id>`
Check quota	`noxinfluencer quota`
Check setup health	`noxinfluencer doctor`
Check membership plans	`noxinfluencer pricing`
Inspect exact flags	`noxinfluencer schema <cmd>`
List monitoring projects	`noxinfluencer monitor list`
Create monitoring project	`noxinfluencer monitor create`
Add monitored video	`noxinfluencer monitor add-task`
List monitored videos	`noxinfluencer monitor tasks`
Get project summary	`noxinfluencer monitor summary`

Add

--detail

for expanded creator analysis when the user needs deeper evidence. Add

--lang zh

for Chinese users. Use

schema <cmd>

when you need exact flags or required fields.

用户意图	CLI命令
搜索创作者	`noxinfluencer creator search`
创作者概览	`noxinfluencer creator profile <creator_id>`
受众分析	`noxinfluencer creator audience <creator_id>`
内容分析	`noxinfluencer creator content <creator_id>`
合作/定价信号	`noxinfluencer creator cooperation <creator_id>`
获取联系方式	`noxinfluencer creator contacts <creator_id>`
查询配额	`noxinfluencer quota`
检查配置健康状态	`noxinfluencer doctor`
查看会员方案	`noxinfluencer pricing`
查询精确参数	`noxinfluencer schema <cmd>`
列出监控项目	`noxinfluencer monitor list`
创建监控项目	`noxinfluencer monitor create`
添加监控视频	`noxinfluencer monitor add-task`
列出监控视频	`noxinfluencer monitor tasks`
获取项目汇总	`noxinfluencer monitor summary`

当用户需要更深度的佐证信息时，添加

--detail

参数获取扩展的创作者分析结果。为中文用户服务时添加

--lang zh

参数。当你需要精确的参数或必填字段信息时，使用

schema <cmd>

命令。

1. Getting Started

1. 入门指引

Run

noxinfluencer doctor

first to check the current state. Guide through only what's missing:

No CLI installed → Tell user to run
```
npm install -g @noxinfluencer/cli
```
in their terminal. In the same reply, directly provide the browser steps they must do themselves:
- English register:
```
https://www.noxinfluencer.com/signup?userType=brand&service=%2Fskills%2Fdashboard
```
- English API key:
```
https://www.noxinfluencer.com/skills/dashboard
```
- Chinese register:
```
https://cn.noxinfluencer.com/signup?userType=brand&service=%2Fskills%2Fdashboard
```
- Chinese API key:
```
https://cn.noxinfluencer.com/skills/dashboard
```
  Prefer a host-provided secret first:
```
skills.entries.noxinfluencer.apiKey
```
  in OpenClaw maps to
```
NOXINFLUENCER_API_KEY
```
  . If no secret channel is available, ask for a one-time handoff only through the safest available channel, then configure with
```
noxinfluencer auth --key-stdin
```
  rather than putting the key in argv, logs, or echoed messages.
CLI installed, no API key → Check whether
```
NOXINFLUENCER_API_KEY
```
/
```
skills.entries.noxinfluencer.apiKey
```
is already available before asking for manual input. Run
```
doctor
```
and prefer CLI-provided hints / URLs. Only fall back to the static register + API key links above if the CLI output is incomplete.
Everything configured → Run
```
quota
```
, tell them the current Skill quota snapshot and any obvious blocking issues.

首先运行

noxinfluencer doctor

检查当前状态，仅引导用户补充缺失的配置：

未安装CLI → 告知用户在终端运行
```
npm install -g @noxinfluencer/cli
```
。在同一条回复中，直接提供用户需要自行完成的浏览器操作步骤：
- 英文站点注册:
```
https://www.noxinfluencer.com/signup?userType=brand&service=%2Fskills%2Fdashboard
```
- 英文站点API密钥获取:
```
https://www.noxinfluencer.com/skills/dashboard
```
- 中文站点注册:
```
https://cn.noxinfluencer.com/signup?userType=brand&service=%2Fskills%2Fdashboard
```
- 中文站点API密钥获取:
```
https://cn.noxinfluencer.com/skills/dashboard
```
  优先使用平台提供的密钥：OpenClaw中的
```
skills.entries.noxinfluencer.apiKey
```
  对应
```
NOXINFLUENCER_API_KEY
```
  。如果没有可用的密钥通道，仅通过最安全的可用通道请求用户一次性转交密钥，然后使用
```
noxinfluencer auth --key-stdin
```
  配置，不要将密钥放在argv、日志或回显消息中。
已安装CLI，但未配置API密钥 → 在请求用户手动输入前，先检查
```
NOXINFLUENCER_API_KEY
```
/
```
skills.entries.noxinfluencer.apiKey
```
是否已可用。运行
```
doctor
```
命令，优先使用CLI提供的提示/URL。仅当CLI输出不完整时，才 fallback 到上方的静态注册+API密钥链接。
所有配置已完成 → 运行
```
quota
```
命令，告知用户当前Skill配额快照以及任何明显的阻塞问题。

Quota and Billing

配额与计费

Run

quota

yourself and report the current Skill quota snapshot.

Important:

Any API-backed skill call can consume the account's remaining Skill quota
The same call may also depend on underlying SaaS-side quota or entitlement for that capability
A request can therefore fail because Skill quota is exhausted, or because the underlying SaaS quota / permission is unavailable

If quota is low or exhausted, the error response's

action

field includes the billing URL. Pass it to the user.

你需要自行运行

quota

命令并反馈当前的Skill配额快照。

重要说明：

任何基于API的Skill调用都会消耗账户剩余的Skill配额
同一个调用也可能依赖底层SaaS端对应能力的配额或授权
因此请求失败可能是因为Skill配额耗尽，也可能是因为底层SaaS配额/权限不可用

如果配额不足或耗尽，错误响应的

action

字段会包含计费URL，请将其提供给用户。

2. Discovering Creators

2. 创作者发掘

Turn an open-ended search into a usable shortlist.

将开放式搜索转换为可用的候选短名单。

Clarification Strategy

澄清策略

Do not search immediately if the request is too broad. Ask for 2–3 critical filters at a time:

Platform — YouTube, TikTok, or Instagram?
Niche / keywords — what content area?
Region — which countries or markets?
Creator size — follower range?
Contactability — does email availability matter?

Stop asking once the request is specific enough. If the user provided most filters upfront, search directly.

如果请求过于宽泛，不要立即搜索。每次向用户询问2-3个关键筛选条件：

平台 — YouTube、TikTok还是Instagram？
细分领域/关键词 — 什么内容领域？
地区 — 哪些国家或市场？
创作者规模 — 粉丝量范围？
可联系性 — 是否要求必须有可用邮箱？

一旦请求足够具体就停止询问。如果用户已经预先提供了大部分筛选条件，直接搜索即可。

Search Execution

搜索执行

Use

noxinfluencer schema creator.search

to discover available filter parameters. The quoted single-argument form

noxinfluencer schema 'creator search'

is equivalent. Key decisions:

Multi-platform requests require separate searches per platform
Add
```
--has_email true
```
when the user's intent is commercial outreach
Start with one search, refine if results are too noisy
For "show more", "next page", "继续", or similar follow-ups, rerun the same search with the next
```
page_num
```
and the prior response's
```
data.search_after
```
; if there is no cursor or the last page was already reached, say there are no more results

See

{baseDir}/references/search-filters.md

for filter selection semantics by user intent.

使用

noxinfluencer schema creator.search

查询可用的筛选参数。带引号的单参数形式

noxinfluencer schema 'creator search'

是等效的。关键决策点：

多平台请求需要按平台分别搜索
当用户意图是商业外联时，添加
```
--has_email true
```
参数
先执行一次搜索，如果结果噪声太大再优化筛选条件
对于“展示更多”、“下一页”、“继续”或类似的后续请求，使用下一个
```
page_num
```
和之前响应的
```
data.search_after
```
重新运行相同的搜索；如果没有游标或已经到达最后一页，告知用户没有更多结果

查看

{baseDir}/references/search-filters.md

了解不同用户意图对应的筛选条件选择逻辑。

Shortlist Presentation

短名单展示

Present results as a visible, comparable shortlist — not a raw JSON dump.

For each candidate: nickname, platform, followers, engagement rate, average views, country, top tags.

Rules:

3–5 candidates first
Make rows easy to compare at a glance
If results are noisy, say so and ask for one more narrowing filter
State if
```
--has_email true
```
was used, but do not imply email was already retrieved
Include: why candidates match, filters applied, the next-step suggestion, and remaining Skill quota when the response includes it and it changes the user's next decision

将结果展示为清晰可对比的短名单，而不是原始JSON输出。

每个候选者包含：昵称、平台、粉丝数、互动率、平均播放量、国家、热门标签。

规则：

首次展示3-5个候选者
让行内容易于快速对比
如果结果噪声大，告知用户并请求补充一个收窄范围的筛选条件
说明是否使用了
```
--has_email true
```
参数，但不要暗示已经获取到了邮箱
包含：候选者匹配原因、应用的筛选条件、下一步建议，以及当剩余Skill配额会影响用户下一步决策时，同步告知配额情况

3. Analyzing Creators

3. 创作者分析

Help the user decide whether a creator is worth pursuing. Lead with a verdict, not a wall of numbers.

帮助用户判断一个创作者是否值得合作。优先给出结论，而非堆砌数字。

Workflow

工作流程

Confirm which creator to analyze (use
```
creator_id
```
from prior search or user input).
If user asked about a specific concern, check that dimension first.
If no specific concern, follow default order: profile → audience → content → cooperation (all with
```
--detail
```
flag).
Platform-aware skip: TikTok and Instagram often have partial cooperation/pricing data. Skip
```
creator cooperation --detail
```
unless the user explicitly asks for pricing or brand-history signals, or the primary platform is YouTube. See
```
{baseDir}/references/platform-support.md
```
.
For content analysis in Chinese context, add
```
--language zh
```
.
Return verdict first, then supporting evidence.

Use

noxinfluencer schema creator.<dimension>

(e.g.,

schema creator.profile

). The quoted single-argument form (for example

schema 'creator profile'

) is equivalent.

确认要分析的创作者（使用之前搜索得到的
```
creator_id
```
或用户输入的内容）。
如果用户有明确的关注点，优先检查该维度。
如果没有明确关注点，按照默认顺序：概况→受众→内容→合作（全部添加
```
--detail
```
参数）。
平台感知跳过逻辑：TikTok和Instagram通常只有部分合作/定价数据。除非用户明确要求查看定价或品牌合作历史信号，或者核心平台是YouTube，否则跳过
```
creator cooperation --detail
```
。查看
```
{baseDir}/references/platform-support.md
```
了解详情。
中文语境下的内容分析，添加
```
--language zh
```
参数。
先返回结论，再返回支撑证据。

使用

noxinfluencer schema creator.<dimension>

（例如

schema creator.profile

）查询参数。带引号的单参数形式（例如

schema 'creator profile'

）是等效的。

Verdict Framework

结论框架

Always lead with one of these four conclusions:

High-priority collaboration candidate — no dispute signal, healthy audience, competitive performance, no pricing friction
Viable, but with clear risks — workable overall, 1–2 notable concerns
Needs manual review before proceeding — mixed evidence or data incomplete
Not a priority collaboration candidate — multiple weak signals

See

{baseDir}/references/verdict-heuristics.md

for detailed heuristic rules and output structure.

始终优先给出以下四个结论之一：

高优先级合作候选 — 无纠纷信号、受众健康、表现有竞争力、无定价障碍
可行，但存在明确风险 — 整体可合作，存在1-2个值得注意的问题
继续推进前需要人工审核 — 证据好坏参半或数据不完整
非优先合作候选 — 存在多个负面信号

查看

{baseDir}/references/verdict-heuristics.md

了解详细的启发式规则和输出结构。

Interpretation Rules

解读规则

Dispute history and negative cooperation signals are decision-critical — always surface them.
Benchmark position is context, not the sole determinant.
Evaluate pricing relative to performance, audience quality, and cooperation signals.
When evidence is mixed, prefer "Needs manual review" over false confidence.
When only one dimension was checked, present as a scoped judgment, not a full verdict.

纠纷历史和负面合作信号是决策关键，必须明确指出
基准排名是参考信息，不是唯一决定因素
结合表现、受众质量和合作信号评估定价合理性
当证据好坏参半时，优先给出“需要人工审核”的结论，而非给出虚假的确定性判断
仅检查了单个维度时，将结果表述为范围判断，而非完整结论

Escalation Rules

升级规则

One bad dimension → explain the tradeoff, don't force a hard reject.
Multiple weak dimensions → clear cautionary verdict.
User asks about one dimension → stay focused, but mention obvious red flags.

单个维度有问题 → 解释权衡利弊，不要直接强制否决
多个维度表现不佳 → 给出明确的警告性结论
用户仅询问单个维度 → 聚焦该维度，但可以提及明显的危险信号

4. Retrieving Contacts

4. 联系方式获取

Retrieve contact info for a specific creator. Intentionally narrow — gets contact data, nothing more.

Confirm which creator (use
```
creator_id
```
from prior search or user input).
Run the contacts command.
Return only the contact info and quality signal.

获取特定创作者的联系信息。功能有意收窄，仅获取联系数据，不提供其他内容。

确认要查询的创作者（使用之前搜索得到的
```
creator_id
```
或用户输入的内容）。
运行联系方式查询命令。
仅返回联系信息和质量信号。

Quality Interpretation

质量解读

`email_quality`	Meaning
`1`	High-quality contact signal
`2`	Normal contact signal
`0`	Low-confidence or unverified contact signal

If email is null, clearly say no reliable email is currently available. If email exists but quality is

, return it with cautionary wording and tell the user it needs manual verification.

Do not add outreach recommendations or restate creator metrics.

`email_quality`	含义
`1`	高质量联系信号
`2`	普通质量联系信号
`0`	低置信度或未验证的联系信号

如果邮箱为null，明确告知用户当前没有可用的可靠邮箱。如果邮箱存在但质量为

，返回时附带警告说明，告知用户需要人工验证。

不要添加外联建议或重复创作者指标。

5. Tracking Performance

5. 表现追踪

Manage video monitoring projects and tracked videos. Operational only — manages monitoring, not performance judgment.

管理视频监控项目和被监控的视频。仅负责运营层面的监控管理，不提供表现判断。

Workflow

工作流程

List projects first when the target project is unclear.
Create a project when user wants a new one.
If user wants to create AND monitor in one request, create first then add task.
For project overview, use summary; for specific videos, use task list.

Use

noxinfluencer schema monitor.<subcommand>

for parameter details. Write operations default to dry-run — use

--force

to execute.

当目标项目不明确时，先列出所有项目。
用户需要新项目时创建项目。
如果用户在一个请求中同时要求创建项目和添加监控，先创建项目再添加任务。
项目概览使用汇总接口，特定视频查询使用任务列表接口。

使用

noxinfluencer schema monitor.<subcommand>

查询参数详情。写入操作默认是干运行模式，使用

--force

参数实际执行。

Project Identification

项目识别

Prefer
```
project_id
```
over
```
project_name
```
after the first lookup.
If project names collide, show disambiguation: project_id, name, created time, platforms, monitor count.
Once a project is selected, keep using that
```
project_id
```
until user switches.

首次查询后，优先使用
```
project_id
```
而非
```
project_name
```
如果项目名称重复，展示信息帮助用户区分：project_id、名称、创建时间、覆盖平台、监控数量
选中一个项目后，持续使用该
```
project_id
```
直到用户切换

Output Rules

输出规则

Project lists: name, project_id, platforms, monitor count
Summaries: monitor count, total views/likes/comments, avg engagement, platform breakdown
Task lists: creator name, video title, views, engagement rate, status
Do not turn outputs into performance verdicts

项目列表：名称、project_id、覆盖平台、监控数量
汇总信息：监控数量、总播放/点赞/评论数、平均互动率、平台分布
任务列表：创作者名称、视频标题、播放量、互动率、状态
不要将输出转换为表现结论

Status Codes

状态码说明

Status	Meaning
`loading`	Initializing
`monitoring`	Actively collecting data
`completed`	Monitoring period ended
`video restricted`	Video unavailable
`invalid link`	URL could not be resolved

状态	含义
`loading`	初始化中
`monitoring`	正在主动收集数据
`completed`	监控周期已结束
`video restricted`	视频不可用
`invalid link`	URL无法解析

Workflow Routing

工作流路由

User intent	Start with
Find creators, broad sourcing	§ 2. Discovering Creators
Evaluate a specific creator	§ 3. Analyzing Creators
Get email or contact details	§ 4. Retrieving Contacts
Set up monitoring for a video	§ 5. Tracking Performance
Setup, quota, billing, errors	§ 1. Getting Started

Natural progression: discover → analyze → contact → monitor. But users can enter at any point.

用户意图	起始步骤
查找创作者、大范围物色	§ 2. 创作者发掘
评估特定创作者	§ 3. 创作者分析
获取邮箱或联系信息	§ 4. 联系方式获取
为视频设置监控	§ 5. 表现追踪
配置、配额、计费、错误问题	§ 1. 入门指引

自然流程：发掘→分析→联系→监控。但用户可以从任意节点进入流程。

Error Handling

错误处理

For API-backed failures (

quota

pricing

creator

monitor

), use the CLI response's

action

field when present:

```
action.url
```
— where the user should go
```
action.hint
```
— what to do

Local commands (

auth

doctor

schema

) may not include

action

. Read their native output directly instead of assuming the API error envelope.

For unexpected failures, run

doctor

as a first diagnostic step.

对于基于API的失败请求（

quota

、

pricing

、

creator

、

monitor

），如果CLI响应存在

action

字段，优先使用该字段内容：

```
action.url
```
— 用户需要访问的地址
```
action.hint
```
— 需要执行的操作

本地命令（

auth

、

doctor

、

schema

）可能不包含

action

。直接读取其原生输出，不要假设存在API错误信封。

遇到意外失败时，首先运行

doctor

作为第一步诊断步骤。

References

参考文档

```
{baseDir}/references/cli-response-format.md
```
— response envelope differences and error action handling

{baseDir}/references/platform-support.md

— data availability by platform

```
{baseDir}/references/search-filters.md
```
— filter selection by user intent
```
{baseDir}/references/verdict-heuristics.md
```
— detailed due-diligence rules and output structure

{baseDir}/references/cli-response-format.md

— 响应信封差异和错误操作处理

{baseDir}/references/platform-support.md

— 不同平台的数据可用性

```
{baseDir}/references/search-filters.md
```
— 不同用户意图对应的筛选条件选择
```
{baseDir}/references/verdict-heuristics.md
```
— 详细的尽职调查规则和输出结构