agentleFS
iblaiiblai/financial-services-agents/skills/nice-actimize/SKILL.md

nice-actimize

Skill15 starsChanged 5 months agoMITView on GitHub

NICE Actimize financial crime platform; lets an agent retrieve fraud and AML transaction monitoring alerts, update dispositions, and route SAR candidates to the BSA Officer.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Update alert disposition (true positive, false positive, escalated) and log investigation notes

    line 15
  2. Distinctive:

    All disposition updates are audit-logged and immutable.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

NICE Actimize

What it is

NICE Actimize is the leading financial crime, risk, and compliance platform deployed across retail banks, broker-dealers, and wealth management firms. It encompasses the Suspicious Activity Monitoring (SAM) module for AML transaction monitoring and the Fraud suite for real-time behavioral fraud detection. Firms use it to triage alerts, document investigations, and manage SAR filing pipelines.

When to use this skill

  • Retrieve open fraud or AML alerts from the alert queue, sorted by risk score or typology
  • Pull transaction detail, device fingerprint, and behavioral analytics for a specific alert
  • Update alert disposition (true positive, false positive, escalated) and log investigation notes
  • Route SAR-eligible cases to the BSA Officer review queue
  • Access customer risk profiles and peer group deviation scores for investigation context
  • Pull aged alert and SLA compliance reports for operations management

Credentials

This skill authenticates using env vars declared in metadata above. Set them in ~/.openclaw/.env (see .env.example at the config root). Required variables:

  • ACTIMIZE_BASE_URL - Base URL of the Actimize REST API (e.g. https://actimize.yourfirm.com/api)
  • ACTIMIZE_API_KEY - Service account API key or OAuth2 client credential
  • ACTIMIZE_CLIENT_ID - OAuth2 client ID (if using OAuth flow)
  • ACTIMIZE_CLIENT_SECRET - OAuth2 client secret (if using OAuth flow)

Key operations

  • GET /alerts — list alerts with filters for status, risk score, typology, date range, and analyst assignment
  • GET /alerts/{alertId} — retrieve full alert detail including transaction data and contributing features
  • PATCH /alerts/{alertId}/disposition — update disposition and add investigation notes
  • POST /alerts/{alertId}/escalate — escalate alert to SAR review queue
  • GET /cases/{caseId} — retrieve full case file with linked alerts and investigation history
  • GET /customers/{customerId}/risk-profile — retrieve customer entity risk score and activity profile

Notes

  • Actimize REST API availability depends on the deployment version (ActOne platform vs. legacy); confirm endpoint schema with your Actimize instance version
  • All disposition updates are audit-logged and immutable; corrections require a supervisor override workflow
  • SAR routing triggers downstream BSA workflow — test in the staging environment before enabling in production
  • Access to PII fields (customer name, SSN) may require an elevated role separate from standard analyst access

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.