一键导入
referral-abuse-detection-v2
Detects and investigates referral abuse violations to determine risk severity and appropriate enforcement actions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Detects and investigates referral abuse violations to determine risk severity and appropriate enforcement actions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
A structured offline process for diagnosing and resolving customer-reported service issues using internal data and automated tools.
Systematically identifies and classifies dangerous goods hazard classes using multi-source data and quantitative severity assessment.
Detects and investigates traffic spoofing violations in affiliate marketing to determine enforcement actions.
Establishes a multi-tiered review system for classifying, escalating, and moderating user-generated video content.
Conducts pre-flight airworthiness verification through multi-layered inspection of mechanical components, electrical systems, and maintenance records.
Detects referral abuse violations by investigating accounts, analyzing traffic patterns, and scoring violation indicators to determine enforcement action.
| name | referral-abuse-detection-v2 |
| description | Detects and investigates referral abuse violations to determine risk severity and appropriate enforcement actions. |
| required_tools | ["investigate_account","analyze_temporal_patterns","analyze_traffic_patterns","get_violation_history","get_financial_impact","determine_enforcement_action"] |
| output_fields | ["final_decision"] |
Call the investigate_account tool using the account_id parameter to retrieve account investigation data. Review the user's account, promotional websites, address validity, email authenticity, business description, account status, and account age.
Call the analyze_temporal_patterns tool using the account_id parameter to retrieve temporal activity data. Analyze registration timing for coordinated creation, review off-hours activity percentage, detect unusual traffic surges, and cross-reference registration timestamps with connected accounts.
Call the analyze_traffic_patterns tool using the account_id parameter to retrieve traffic and transaction data. Review key metrics (revenue patterns, click-through rates, page views, device distribution), conduct URL analysis, and perform relationship analysis (connected accounts, shared payment methods).
Call the get_violation_history tool using the account_id parameter to retrieve detailed violation history. Review the previous violations count, last violation date, warning status, and rehabilitation status.
Call the get_financial_impact tool using the account_id parameter to retrieve financial metrics. Assess the total lifetime revenue, refund rate percentage, and customer complaint count.
[OPTIONAL] Gather evidence such as screenshots, screen recordings, URLs, and any other relevant information to support the findings. Make a ticket if the total earnings on the account meet thresholds or if the enforcement action may attract Legal, PR, or Brand Safety concerns.
Calculate scores based on the gathered data by counting TRUE indicators (ensure boolean values are compared as true/false):
Determine violation type based on HIGHEST score. If tied, use priority: Temporal Fraud > Abusive Account Creation > Misleading Ad Copy > Personal Orders. If no score meets its threshold, the result is INCONCLUSIVE.
Calculate Risk Severity for violations (not applicable for "No Violation" or "Inconclusive"):
CRITICAL Risk if ANY of:
HIGH Risk if ANY of:
MEDIUM Risk if ANY of:
LOW Risk:
Call the determine_enforcement_action tool using the account_id parameter, then apply the following enforcement matrix based on the violation type and risk severity:
For Abusive Account Creation or Misleading Ad Copy or Temporal Fraud:
For Personal Orders (Related):
For No Violation:
For INCONCLUSIVE:
[APPROVAL REQUIRED]
Output the final enforcement decision using the exact value determined in the previous step. Include the final_decision value in the complete_step summary using XML tags.
Example: <final_decision>Permanent Account Closure</final_decision>