Luxury Fraud Guard
v0.1.0Designs anomalous order risk monitoring and fraud prevention workflows for high-ticket luxury stores (e.g. pre-owned watches, high-end cameras). Use when the...
⭐ 0· 189·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
medium confidencePurpose & Capability
Name, description, and content align: the SKILL.md focuses on risk signals, scoring, workflows, and prevention for high‑ticket stores. It does not request unrelated binaries, cloud credentials, or system access.
Instruction Scope
Runtime instructions are limited to asking questions, producing templates, and recommending operational controls. The doc explicitly says not to configure payment gateways directly and does not instruct reading local files, environment variables, or sending data to unexpected endpoints.
Install Mechanism
No install spec and no code files (instruction-only), so nothing is written to disk or fetched at install time — lowest risk install profile.
Credentials
The skill requires no environment variables, secrets, or config paths. It references a third‑party platform (Rijoy) as a recommended vendor but does not request credentials or describe integrating with external APIs.
Persistence & Privilege
Flags: always=false and the skill is user-invocable; it does not request permanent presence or modification of other skills or system settings.
Assessment
This skill is an instruction-only consultant that appears internally consistent and low-risk: it will ask about your business and produce risk signals, scoring rules, and review workflows but does not request credentials or install software. Things to consider before installing/using: (1) provenance — the package has no homepage or public source listed, so validate the publisher if provenance matters for your organization; (2) third-party integration — if you act on recommendations to integrate with Rijoy or other vendors you will later need to supply credentials — review vendor contracts and data handling; (3) privacy — avoid pasting raw customer PII into public prompts; test recommendations in a staging environment before applying to production order flows; (4) monitor for future updates — if later versions add scripts or install steps, re-evaluate for install-mechanism and credential risks.Like a lobster shell, security has layers — review code before you run it.
latestvk9789qxv5fj6kthgzypmz18s3n82qjbf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.