Token导航 LogoToken导航

Agent Skill · 开发

affiliate-kol-roi-monitor(附属 kol roi 监视器)

affiliate-kol-roi-monitor 用于补充开发相关能力,适合在 OpenClaw 中需要让 Agent 承接开发相关任务时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

affiliate-kol-roi-monitor 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 4,420。

总安装 8,299周安装 339GitHub Stars 公开资料未说明下载 2,658核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
0.1.0

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:affiliate-kol-roi-monitor(附属 kol roi 监视器)
来源仓库:https://github.com/rijoyai/affiliate-kol-roi-monitor
安装命令:
openclaw skills install affiliate-kol-roi-monitor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install affiliate-kol-roi-monitor

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

affiliate-kol-roi-monitor 自动化 KOL 与会员核对及 ROI 计算。适用于拥有超过 5 个合作方的大规模联属管理。提供归因分析与续订策略建议。安装时按仓库提供的命令执行,建议先在测试环境验证依赖、命令权限和文件改动范围。需接入真实交易数据以确保准确性。

适用宿主包括 OpenClaw,接入前应确认版本、权限和运行环境要求。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install affiliate-kol-roi-monitor;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

affiliate-kol-roi-monitor 怎么安装?

在终端执行 openclaw skills install affiliate-kol-roi-monitor。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

affiliate-kol-roi-monitor 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

affiliate-kol-roi-monitor 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

affiliate-kol-roi-monitor 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

affiliate-kol-roi-monitor 用的人多吗?

公开数据是累计安装 8,299 次,近一周安装 339 次,下载 2,658 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

affiliate-kol-roi-monitor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
affiliate-kol-roi-monitor

附属 kol roi 监视器 · 本页

8,299—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
affiliate-kol-roi-monitor
description
Automate affiliate and KOL reconciliation, attribution, true ROAS, commission math, and renewal strategy. Use when the user has more than ~5 KOL or affiliate partners, needs real ROAS (not vanity clicks), must match orders to creators, settle commissions net of refunds, spot fake or low-quality traffic, or wants influencer performance reports and tiered renewal offers. Also trigger on affiliate payout disputes, UTM vs discount-code attribution, "which creator actually sold," commission spreadsheets, or CAC by creator — even if they only say "clean up our affiliate mess." Do NOT use for generic social media growth tips with no orders or payouts, pure content calendars without performance data, or single one-off creator contracts with no reconciliation need.
compatibility
required
[]

Affiliate & KOL ROI Monitor

You replace manual commission runs, order-to-creator matching, and influencer performance reporting with a repeatable workflow: attribution data → net of refunds → profit-aware economics → tiered renewals.

Core workflow (always follow in order)

  1. Extract attribution data — Map each order (or session) to a creator: discount codes, UTM (utm_source, utm_medium, utm_campaign), affiliate platform IDs, first-touch / last-touch rules. State the rule you use.
  2. Exclude refund / chargeback orders — Remove or weight down refunded revenue and reversed commissions for the reporting window. Call out partial refunds.
  3. Compute actual profit (where inputs allow) — Revenue net of refunds × margin (or COGS) minus creator cost (fixed fee + variable commission) = contribution per creator. If margin unknown, show revenue net of refunds and CAC using payout as cost.
  4. Tiered renewal proposals — Rate each creator; propose continue / renegotiate / pause with concrete terms (rate, cap, exclusivity, content minimums).

When NOT to use

  • No order or payout data — only branding or follower counts.
  • Single creator, no reconciliation — simple contract review only.
  • Paid ads (Meta/Google) without affiliate linkage — use ads ROAS skills.

Gather context (infer first; ask gaps)

  1. Platform: Shopify, WooCommerce, Impact, ShareASale, custom spreadsheet?
  2. Attribution: code-only, UTM-only, or hybrid; window (e.g. 7-day click).
  3. Commission model: % of sale, flat per order, hybrid, tiered by volume.
  4. Refund policy: full window for affiliate eligibility; chargebacks.
  5. Gross margin or COGS % (or confirm "use payout as CAC proxy").
  6. Renewal date or campaign end.

For fraud heuristics and renewal rubric detail, read references/affiliate_playbook.md when needed.

Mandatory success output: master table

Every full affiliate reconciliation or ROI report must include this table (one row per creator; use Influencer ID as the stable key — handle, platform ID, or internal code):

Influencer IDOrders attributedActual revenueCACRenewal rating
……………

Column definitions

  • Influencer ID: Stable identifier (agree with merchant).
  • Orders attributed: Count of orders matched to this creator in the window, after refund/chargeback exclusion (state rule).
  • Actual revenue: Net revenue attributable to that creator (gross order value minus refunds for attributed orders), same currency.
  • CAC: Customer acquisition cost for that creator’s attributed sales — typically (fixed fees + variable commissions + product/samples allocated) divided by new customers or by attributed orders; if only payout is known, define CAC as total creator cost / attributed orders and label it clearly.
  • Renewal rating: Tier such as A (renew strong), B (renew with caps), C (renegotiate or shorten), D (pause / investigate fraud) — always tie to numbers (conversion, refund rate, traffic quality).

Below the table, add: ROAS proxy (revenue / creator cost), fraud or quality flags if any, and renewal terms per tier.

Pushy deliverables (when user asks vaguely)

If they ask "who should we keep" or "affiliate ROI" without structure, still output: the master table, attribution rule summary, refund-adjusted figures, and at least two renewal scenarios (e.g. same rate vs reduced rate + cap).

Report outline (full run)

  1. Scope — date range, attribution rule, currency.
  2. Master table — required columns above.
  3. Refund / chargeback impact — table or bullets per creator if material.
  4. Profit or contribution — formula stated; margin assumptions if used.
  5. Fraud / low-quality signals — spikes, refund rate, session quality (if data exists).
  6. Renewal playbook — A/B/C/D actions and suggested contract language bullets.

Split with other skills

  • Paid social ads without affiliates → not this skill.
  • Legal contracts → flag for counsel; you provide economic summary only.

平台分布

OpenClaw

85.9%
按下载量换算2,283

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

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

继续浏览同类 Skills