usecase-transaction-scan

Extract card transaction details from messages and emails to flag suspicious charges.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/silva2kand/silva-ide --skill usecase-transaction-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: usecase-transaction-scan
Source: https://github.com/silva2kand/silva-ide/tree/main/_cowork_os_pack/package/resources/skills/usecase-transaction-scan
Command: npx skills add https://github.com/silva2kand/silva-ide --skill usecase-transaction-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables users to scan recent messages and emails to detect card transactions and flag any suspicious charges automatically.

Core Features & Use Cases

  • Transaction Detection: Identify and extract transaction details from messages or emails.
  • Fraud Prevention: Flag suspicious charges based on user-defined thresholds and merchant keywords.
  • Use Case: If a user receives numerous banking alerts or emails, use this Skill to automatically pinpoint potentially fraudulent transactions and receive an actionable report.

Quick Start

Use the usecase-transaction-scan to analyze recent messages from the specified channel for transactions over $1000 and identify suspicious charges.

Frequently Asked Questions about usecase-transaction-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan emails and messages to detect suspicious financial transactions?

To scan emails and messages for suspicious financial transactions, you need to extract transaction data and flag charges based on defined thresholds. This process automatically pinpoints potentially fraudulent banking alerts by filtering merchant keywords and amount parameters.

How does automatic fraud detection work for transaction alerts?

Automatic fraud detection for transaction alerts works by extracting transaction details from messages and applying user-defined amount thresholds. It identifies suspicious charges by matching merchant keywords against recent banking alerts to generate an actionable fraud prevention report.

What parameters do I need to identify suspicious charges from banking alerts?

Identifying suspicious charges from banking alerts requires parameters like channel, merchant keywords, recent time window, message count, and amount thresholds. These inputs filter extracted transaction data to accurately flag potentially fraudulent financial activity.

Can I flag fraudulent transactions over a specific amount threshold?

Yes, you can flag fraudulent transactions over a specific amount threshold by setting the amount limit parameter. The scan analyzes recent messages and emails, automatically pinpointing and extracting any transaction details that exceed your defined financial limit.

What is the best way to monitor customer alert systems for fraud prevention?

The best way to monitor customer alert systems for fraud prevention is to automatically scan recent messages and emails for transaction data. By applying specific merchant keywords and amount thresholds, you can quickly identify suspicious charges within your finance workflows.

Are there limitations when extracting transaction data from messages?

A limitation when extracting transaction data is the requirement for specific input parameters, including channel, time window, and amount thresholds. Without accurately defined merchant keywords and message count limits, the fraud detection scan may not effectively identify suspicious charges.