spam-scanner

Audit the Webmatrices database to detect and remove spam posts.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Bishwas-py/webmatrices-skills --skill spam-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spam-scanner
Source: https://github.com/Bishwas-py/webmatrices-skills/tree/main/skills/spam-scanner
Command: npx skills add https://github.com/Bishwas-py/webmatrices-skills --skill spam-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spam is a persistent moderation burden. This Skill detects and removes spam posts in the Webmatrices production environment and bans offending accounts to keep communities healthy.

Core Features & Use Cases

  • Detects spam patterns in posts and comments using predefined keywords
  • Soft-deletes spam posts and bans offending user accounts
  • Provides a moderation workflow with confirmation before actions

Quick Start

Run targeted searches for spam patterns, review matches, and execute deletions and bans after confirmation.

Frequently Asked Questions about spam-scanner

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

FAQPage Schema
How do I automate spam detection in a production database?

Automate spam detection by auditing the production database with predefined keywords to identify spam patterns in posts and comments. The workflow searches for matches, flags offending content, and prepares records for batch moderation actions.

Can I automatically ban spammer accounts and delete their posts?

You can ban spammer accounts and delete posts through batch moderation actions. The workflow applies soft-deletes to flagged spam posts and executes account bans after you review the detected matches and provide confirmation.

How does keyword-based spam moderation work for user comments?

Keyword-based spam moderation scans user comments against predefined spam keywords to identify malicious patterns. It matches text content across the production database, isolates offending entries, and queues them for deletion with confirmation guardrails.

Do I need MCP tooling and access control to run post cleanup workflows?

MCP tooling and access control are required to run post cleanup workflows. These prerequisites ensure secure connections to the production database for executing keyword searches, soft-deleting spam posts, and banning offending user accounts.

What is the best way to safely remove spam posts without false positives?

The best way to avoid false positives when removing spam posts is using a confirmation-based moderation workflow. The system detects spam via keywords and requires explicit confirmation before executing any soft-deletions or account bans.

What are the limitations of keyword-based spam detection for community moderation?

Keyword-based spam detection is limited to matching predefined terms and may miss contextually nuanced spam. It requires manual confirmation before executing deletions or bans to prevent false positives from inadvertently removing legitimate community posts.