Affiliate Kol Roi Monitor
v0.1.0Automate affiliate and KOL reconciliation, attribution, true ROAS, commission math, and renewal strategy. Use when the user has more than ~5 KOL or affiliate...
⭐ 0· 183·0 current·0 all-time
byRIJOY-AI@rijoyai
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the skill describes attribution, refund-adjusted revenue, CAC/ROAS calculations, fraud heuristics, and renewal proposals and only requires order/payout/attribution data the merchant would reasonably provide. There are no unrelated credential or binary requests.
Instruction Scope
SKILL.md stays on-topic: it asks the agent to extract attribution from orders/sessions, exclude refunds, compute economics, and propose renewals. It recommends reading the included playbook for heuristics. It does not instruct the agent to read arbitrary system files, access unrelated environment variables, or send data to external endpoints.
Install Mechanism
Instruction-only skill with no install spec and no code files to execute. There is a scripts/README noting optional automation, but no actual scripts or download/install steps are present.
Credentials
No environment variables, credentials, or config paths are requested. The workflow expects user-provided data exports (orders, refunds, codes) which is appropriate for the task; there are no disproportionate secret requests.
Persistence & Privilege
Skill is not forced-always and does not request persistent system-wide changes. It is user-invocable and can be invoked autonomously per platform defaults, which is expected for a skill of this type.
Assessment
This skill is an instruction-only workflow that will ask you to provide order exports, refund records, and attribution mapping (discount codes, UTMs, or affiliate IDs). Before using it: (1) provide only the minimum data needed (sanitized CSVs or samples) rather than full production credentials or admin API keys, (2) remove or anonymize any customer PII if you don't want it processed, (3) confirm margin/COGS or accept that the skill will use payout-as-CAC proxies if you don't provide them, and (4) if you plan to add automation scripts later, review any code for networking or credential usage—currently no install or external endpoints are present. If you need legal contract language, treat the skill's output as advisory and have counsel review final terms.Like a lobster shell, security has layers — review code before you run it.
latestvk974pq45fhn8f65hs53knqzets82wdce
License
MIT-0
Free to use, modify, and redistribute. No attribution required.