mcpField
C
chat-widget

chat-widget

github.com/sickn33Development48.7k50 installsUpdated today
Repository

About chat-widget

A skill for designing in-app real-time support chat, covering a floating user widget and an admin dashboard. Its guide is a design sketch and stresses implementing and testing authentication, authorization, and delivery safeguards before launch.

Key features

  1. 01Design a floating user chat widget
  2. 02Plan an admin dashboard for support staff
  3. 03Support real-time user-admin messaging
  4. 04Emphasize authentication and chat authorization
  5. 05Require testing delivery and message history

Use cases

  1. 01Add a live chat entry point to an app
  2. 02Build customer support chat functionality
  3. 03Enable real-time communication between users and admins
  4. 04Plan an in-app support channel

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sickn33/agentic-awesome-skills --skill chat-widget

After installing, type/chat-widgetin Claude Code to confirm it loaded.

Bundled filesreferences/detailed-guide.md

Details

From the project README

Live Support Chat Widget

Build a real-time support chat system with a floating widget for users and an admin dashboard for support staff.

Detailed Guide

Use the bundled guide as a design sketch, not a production implementation. Authentication, per-chat/tenant authorization, private channels, bounded history and acknowledged delivery must be implemented and tested before exposing support messages.

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use This Skill

Use when the user wants to:

  • Add a live chat widget to their app
  • Build customer support chat functionality
  • Create real-time messaging between users and admins
  • Add an in-app support channel

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Comments

Markdown supported