ban-user

Ban users by ID, username, or email with soft-deletion and audit logging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ban and deactivate problematic users by ID, username, or email, while preserving platform integrity through soft-deletion of their content and an audit trail.

Core Features & Use Cases

  • Lookup by ID (numeric), username, or email to identify the target user.
  • Deactivate the account and soft-delete their posts, with explicit confirmation required.
  • Display user details (ID, username, email, post count, active status) before action and log the operation for audit purposes.
  • Safety guardrails to prevent banning staff or superusers without explicit consent.

Quick Start

Provide the user identifier (ID, username, or email) and confirm the ban to deactivate the account and soft-delete related posts.

Frequently Asked Questions about ban-user

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

FAQPage Schema
How do I ban and deactivate a user by username or email while preserving their content?

To ban a user by username or email, the Skill looks up the account, deactivates access, and soft-deletes related posts to preserve platform integrity. It displays user details and requires explicit confirmation before applying the ban.

What happens to a user's posts when I deactivate their account for moderation?

When you deactivate an account for moderation, the Skill soft-deletes their posts rather than permanently removing them. This ensures content is hidden from the platform while maintaining an accessible record for audit logging.

Can I ban staff or superusers using automated moderation tools?

You cannot ban staff or superusers without explicit consent. The Skill enforces safety guardrails that prevent the banning of elevated accounts, requiring additional confirmation to protect administrative roles from accidental deactivation.

How do I audit user ban actions and keep a record of moderation activity?

To audit user ban actions, the Skill logs the deactivation operation via MCP tools after you confirm the ban. This creates an audit trail capturing the target user details and the moderation action taken.

Do I need to confirm before banning a user by their numeric ID?

Yes, you must provide explicit confirmation before banning a user by their numeric ID. The Skill displays the target user's ID, username, email, post count, and active status, requiring you to approve the deactivation and soft-deletion.

What's the best way to safely deactivate problematic users without losing their content history?

The best way to safely deactivate problematic users is using a soft-delete approach that blocks access while retaining content. The Skill deactivates the account, soft-deletes posts, and logs the action for a complete audit trail.