Build Fraud Detection and Risk Controls
Fraud teams need practical methods to identify abuse, test controls, and monitor drift. This skill guides risk analysis, rules, models, backtesting, and real-time system design.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "risk-control-engineer" from https://skillstore.io/skills/zl2023github-risk-control-engineer.md and its manifest at https://skillstore.io/api/skills/zl2023github-risk-control-engineer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "risk-control-engineer". Assess coupon abuse during a new-user promotion.
Expected outcome:
Using "risk-control-engineer". Plan a backtest for account-takeover rules.
Expected outcome:
Using "risk-control-engineer". Design monitoring for a production fraud model.
Expected outcome:
Monitor score distribution, PSI, approval rate, rejection rate, review rate, delayed fraud labels, latency, and feature freshness with defined owners.
The Python rule-engine example performs dynamic evaluation of rule text and is a confirmed code-execution risk. The 21 command alerts, two reconnaissance alerts, and entropy alert are false positives caused by Markdown fences, graph variables, and multilingual text. Two additional control-quality defects could hide rule failures or misstate backtest performance.
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/zl2023github-risk-control-engineer/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/zl2023github-risk-control-engineer?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/zl2023github-risk-control-engineer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/zl2023github-risk-control-engineer/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/zl2023github-risk-control-engineer.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>zl2023github. (2026). risk-control-engineer security audit report (audit version 4) [Author version unspecified]. Skillstore. https://skillstore.io/skills/zl2023github-risk-control-engineer/audits/4@techreport{zl2023github-zl2023github-risk-control-engineer-2026,
author = {zl2023github},
title = {risk-control-engineer security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/zl2023github-risk-control-engineer/audits/4},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "risk-control-engineer security audit report (audit version 4)"
version: "unspecified"
type: report
authors:
- name: "zl2023github"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/zl2023github-risk-control-engineer/audits/4"
identifiers:
- type: other
value: "skillstore:zl2023github-risk-control-engineer:audit:4"
description: "Skillstore immutable audit report identifier"
Map likely attacks, affected workflows, evidence, control gaps, and prioritized defenses for a new product flow.
Define features, temporal validation, evaluation metrics, thresholds, and cost assumptions for candidate controls.
Create a scalable architecture for streaming features, rule evaluation, model inference, case review, monitoring, and rollout.
Analyze fraud risks for [business flow]. List attack paths, affected users, existing control gaps, and prioritized defenses.
Design rules for [scenario] using [available fields]. Include rule IDs, conditions, actions, priorities, conflicts, and measurable review criteria.
Create a backtest plan for [dataset] and [rules]. Define temporal splits, metrics, cost assumptions, leakage checks, and threshold selection.
Design a real-time fraud platform for [QPS] and [latency target]. Cover data flows, feature storage, decisioning, monitoring, resilience, and rollout.
Author
zl2023githubLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
2 downloads · 1 views
File structure
📄 SKILL.md
Diagnose and Improve Full-Stack Performance
Full-stack teams often lack a repeatable way to measure performance and locate bottlenecks. This skill provides testing workflows, diagnostic commands, optimization guidance, and report structures.
Build and Optimize Search Systems
Search teams need reliable guidance across indexing, ranking, semantic retrieval, and evaluation. This skill provides practical workflows and examples for building and improving search systems.
Design Reliable Payment Systems
Payment teams need consistent designs for transactions, channels, reconciliation, security, and failure handling. This skill provides structured guidance, examples, and review checklists.
Build Reliable Business Intelligence Analysis
Business teams often lack consistent metrics and repeatable analysis workflows. This skill guides SQL, Python, dashboards, experiments, and automated reporting from requirements to delivery.
Evaluate Technology Choices with Clear Tradeoffs
Technology choices often hide tradeoffs across performance, cost, reliability, operations, and team readiness. This skill compares candidates, recommends an option, and defines proof-of-concept checks.
Generate Clear Software Architecture Documents
Architecture decisions often remain scattered across requirements, discussions, and diagrams. This skill organizes them into consistent Markdown documents for implementation and review.
Detect Code and Data Patterns
by supercent-io
Teams miss recurring defects, risky patterns, and data anomalies when reviews rely only on manual inspection. This skill guides read-only pattern searches, regex checks, and concise reports for Claude, Codex, and Claude Code.
Build Java Anomaly Detection with Azure AI
by sickn33
Time-series monitoring requires reliable patterns for detecting unusual behavior. This skill provides Java examples for Azure AI client setup, analysis, training, inference, and model management.
Clean Data for Reliable Analysis
by zhangchenlai-dev
Messy datasets slow analysis and create unreliable results. This skill guides Claude, Codex, and Claude Code through practical cleaning steps.
Monitor Business Health Across 13 Domains
by CleanExpo
Teams miss early warning signs when metrics live across finance, product, customers, and team systems. This skill structures health checks, anomaly reviews, digests, alerts, and decision simulations for AI-assisted business monitoring.
Analyze Time Series with Aeon
by davila7
General machine-learning methods often miss temporal structure and specialized evaluation needs. This skill guides Aeon model selection, preprocessing, training, and benchmarking for time series tasks.
Build and Evaluate Quantitative Strategies
by longbridge
Quantitative research requires consistent data, statistical methods, and validation. This skill structures Longbridge workflows for analysis, screening, optimization, execution, and hedging.