Menu

Individual skill

tawk-support

This skill should be used when the user asks to "add Tawk support chat", "identify chat visitors", "theme a support widget", or "set up a Tawk knowledge base". Reuse signed account identification, product-specific knowledge and website styling without sharing credentials or private app content.

plugins/reusable-app-components/skills/tawk-support/SKILL.md

Read pinned source

Source commit 4f2b4bc9a74024397b4688cbafd1ae538a83a5fb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,200
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Tawk support

Inspect the product’s existing support widget, account/session owner, locales, theme and real user journeys. Reuse its verified account lookup and delivery process. Keep each product’s Tawk property and signing keys separate.

Read [integration](references/integration.md) before adapting [TawkSupport.tsx](assets/TawkSupport.tsx). The React 19.2+ asset owns SDK identity refresh, account switching, signed guests, cancellation and visibility. The host owns loading Tawk once, widget/language switching, the verified server endpoint and observable auth changes. Other stacks should implement the same contract.

Read [knowledge and theme](references/knowledge-and-theme.md) when configuring the property. Ground answers in current product source and live flows, maintain a tracked source, and test actual bot answers and links. Product facts from one app are not defaults for another.

Verify the app build and applicable account, locale, guest/logout, visibility and browser journeys before release. Keep fixture, real SDK and deployed evidence distinct. Never treat passing extraction tests or this recipe as authorization to publish another app. Record the app revision and evidence in existing tracked guidance.