mcpField
A
abuse-fraud-risk-review

abuse-fraud-risk-review

github.com/sylphxaiSecurity153 installsUpdated today
Repository

About abuse-fraud-risk-review

A skill for product teams reviewing abuse and fraud risks while accounting for harm to legitimate users. It structures the work into a risk matrix and control plan, with review and appeal paths.

Key features

  1. 01Identify assets, incentives, and abuse surfaces
  2. 02Assess harm to legitimate users
  3. 03Map signals, controls, and review paths
  4. 04Separate prevention, detection, response, and learning
  5. 05Produce a risk matrix and control plan

Use cases

  1. 01Review abuse risks in a product
  2. 02Plan fraud controls and escalation paths
  3. 03Assess false positives and recovery options

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill abuse-fraud-risk-review

After installing, type/abuse-fraud-risk-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/abuse-fraud-risk-patterns.md

Details

From the project README

Abuse Fraud Risk Review

Use this skill to protect product integrity without punishing legitimate users unfairly.

Workflow

  1. Identify assets at risk, attacker incentives, abuse surfaces, and legitimate-user harm.
  2. Read references/abuse-fraud-risk-patterns.md.
  3. Map signals, controls, review ladder, support route, and recovery/appeal.
  4. Separate prevention, detection, response, and learning.
  5. Produce risk matrix and control plan.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not recommend silent irreversible punishment without evidence and appeal path.
  • Do not collect excessive data for vague fraud goals.
  • Balance false positives against abuse damage.

Output format

Abuse surface:
Assets at risk:

Risk matrix:
- <scenario> -> likelihood, impact, controls, review path

Controls:
- Prevent:
- Detect:
- Respond:
- Recover:

Events/signals:
- <signal>

Comments

Markdown supported