security-review

Review ChatbotX code changes for security risks before committing.

601|129|Updated Dec 9, 2024
One-click install
npx skills add https://github.com/ChatbotXIO/ChatbotX --skill security-review-chatbotxio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-review
Source: https://github.com/ChatbotXIO/ChatbotX/tree/main/.agents/skills/security-review
Command: npx skills add https://github.com/ChatbotXIO/ChatbotX --skill security-review-chatbotxio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch security-sensitive issues in ChatbotX changes before they ship, especially in multi-workspace data access, channel webhooks, AI tool usage, and local permission settings.

Core Features & Use Cases

  • Tenant Isolation Checks: Verifies that workspace-scoped data access stays properly isolated and does not leak cross-tenant records.
  • Prompt Injection Review: Flags untrusted channel content, uploaded documents, and fetched URLs if they could influence AI prompts or retrieval context unsafely.
  • Permission and Secret Safety: Reviews local Bash allowlists, credential handling, and MCP exposure to reduce the risk of accidental secret disclosure or over-broad execution.
  • Use Case: Before merging a change to webhook handlers or workspace APIs, use this Skill to produce a prioritized security findings list with concrete fixes.

Quick Start

Review the ChatbotX change set for tenant isolation, prompt injection, permission allowlist, and secret-handling issues before committing.

Frequently Asked Questions about security-review

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

FAQPage Schema
What is prompt injection and how do I prevent it in channel webhooks?

You review permission allowlists by checking local Bash execution rules and MCP exposure settings. Safe configurations restrict broad execution capabilities and verify credential handling to reduce accidental secret disclosure risks.

How do I check tenant isolation before merging workspace API changes?

You check tenant isolation by reviewing workspace-scoped data access paths in your code changes. Verify that API handlers and database queries properly restrict records to the requesting workspace, preventing cross-tenant data leakage before committing.

How do I review MCP integrations and secret handling for security risks?

You review MCP integrations by examining exposure settings and credential flows. Check that secret handling does not accidentally disclose tokens, verify local permission allowlists, and ensure MCP tools cannot access credentials beyond their intended scope.

What's the best way to find security vulnerabilities in AI tool usage?

The best way to find AI tool security vulnerabilities is reviewing code changes against multi-workspace access patterns, webhook handlers, and prompt injection vectors. Produce prioritized findings with file, line, risk severity, and concrete fixes before committing.

Does this security review catch cross-tenant data leaks in webhook handlers?

Yes, the security review catches cross-tenant data leaks by verifying workspace scoping in webhook handlers and channel content paths. It flags any code where workspace-scoped data access could expose records across tenant boundaries before changes ship.

When should I run a security review on ChatbotX code changes?

You should run a security review before committing changes to webhook handlers, workspace APIs, AI tool integrations, MCP connections, or local permission settings. Early review catches tenant isolation, prompt injection, and secret handling issues before they ship.