Masheev react sdk
Official Agent Skills for integrating Masheev into your applications
npx -y skills add masheev/skills --skill masheev-react-sdkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when building custom chat UIs with the Masheev React SDK instead of the default widget. Covers the useMasheev hook, MasheevProvider for headless mode, useWidgetSession, useWidgetChat, useWidgetSocket, useReadAloud, custom message rendering, event handling, and building chat interfaces from scratch. Use this skill when someone wants a "custom chat UI", "headless integration", "build their own chat component", or references @masheev/embed-sdk/react or @masheev/embed-sdk/headless.
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.9 KB, as published. Nobody here has run it
Masheev React SDK
Build fully custom chat UIs using React hooks. Two approaches:
@masheev/embed-sdk/react— Widget in an iframe, controlled via hooks@masheev/embed-sdk/headless— No iframe, direct WebSocket connection, full UI control
When to Use Which
| Need | Use |
|---|---|
| Default chat bubble with some customization | useMasheev from /react |
| Embed widget in a specific area of the page | useMasheev with mode: "embedded" |
| Fully custom chat UI (own message bubbles, layout) | MasheevProvider + hooks from /headless |
| Chat on React Native | /headless (no iframe available) |
Widget Hook (/react)
import { useMasheev } from "@masheev/embed-sdk/react";
function App() {
const {
open, close, toggle,
hide, show,
sendMessage,
setInputValue,
updateContext,
updateContact,
updateTools,
updateWorkflow,
setQuestions,
setListening,
resetConversation,
on, off,
containerRef, // For embedded mode — attach to a DOM element
isReady,
} = useMasheev({
inboxId: "YOUR_INBOX_ID",
mode: "chat-widget",
user: { name: "Jane", email: "[email protected]" },
});
return (
<div>
<button onClick={open} disabled={!isReady}>Open Chat</button>
</div>
);
}
Singleton pattern: Multiple useMasheev() calls with the same inboxId share a single SDK instance and iframe. The iframe is destroyed only when the last consumer unmounts.
Headless Mode (/headless)
import {
MasheevProvider,
useWidgetSession,
useWidgetChat,
useWidgetSocket,
useReadAloud,
} from "@masheev/embed-sdk/headless";
function App() {
return (
<MasheevProvider config={{
inboxId: "YOUR_INBOX_ID",
apiBase: "https://api.masheev.com",
customerInfo: { name: "Jane", email: "[email protected]" },
}}>
<CustomChat />
</MasheevProvider>
);
}
function CustomChat() {
const { conversationId, greeting, workflowRunState } = useWidgetSession();
const { messages, sendMessage, isStreaming } = useWidgetChat();
const { status: connectionStatus } = useWidgetSocket();
return (
<div>
<div className="messages">
{messages.map((msg) => (
<div key={msg.id} className={msg.role}>
{msg.content}
</div>
))}
{isStreaming && <div className="typing">AI is typing...</div>}
</div>
<input
onKeyDown={(e) => {
if (e.key === "Enter") {
sendMessage(e.currentTarget.value);
e.currentTarget.value = "";
}
}}
/>
</div>
);
}
Provider Config
interface MasheevProviderConfig {
inboxId: string; // Required
apiBase?: string; // Default: "https://api.masheev.com"
turnstileSiteKey?: string; // Cloudflare Turnstile (anti-bot)
customerInfo?: {
name?: string;
email?: string;
phone?: string;
};
tools?: readonly ClientToolDefinition[]; // Client-side tools
instructions?: string; // Tool usage instructions for AI
workflow?: WorkflowConfig; // Conversational workflow
onStepComplete?: (payload: WorkflowStepCompletePayload) => void;
onWorkflowComplete?: (payload: WorkflowCompletePayload) => void;
}
Headless Hooks Reference
| Hook | Returns | Purpose |
|---|---|---|
useWidgetSession() | { conversationId, contactId, greeting, workflowRunState, status } | Session lifecycle |
useWidgetChat() | { messages, sendMessage, resolve, isStreaming, history } | Message operations |
useWidgetSocket() | { status, subscribe, unsubscribe } | WebSocket connection state |
useReadAloud() | { play, pause, stop, isPlaying, currentMessageId } | Text-to-speech controls |
Defining Tools with Zod
import { clientTool } from "@masheev/embed-sdk/headless";
import { z } from "zod";
const bookingTool = clientTool({
name: "check_availability",
description: "Check appointment availability for a given date",
parameters: z.object({
date: z.string().describe("ISO date string"),
service: z.string().describe("Service type"),
}),
execute: async (args, { onProgress }) => {
onProgress("Checking calendar...");
const slots = await fetchSlots(args.date, args.service);
return { success: true, data: { slots } };
},
});
// Pass to provider
<MasheevProvider config={{ inboxId: "...", tools: [bookingTool] }}>
Workflow Helpers
import { defineWorkflow, validateWorkflowConfig } from "@masheev/embed-sdk/headless";
const onboardingFlow = defineWorkflow({
id: "user_onboarding",
name: "New User Onboarding",
steps: [
{ id: "greeting", name: "Welcome", instructions: "Greet the user by name: {{context.name}}" },
{ id: "collect_info", name: "Collect Details", tools: ["check_availability"] },
{ id: "confirm", name: "Confirm Booking", instructions: "Summarize and confirm" },
],
context: { name: "Jane" },
});
// Validate before passing to provider
const result = validateWorkflowConfig(onboardingFlow);
if (!result.valid) console.error(result.errors);
See references/headless.md for advanced patterns (custom message components, streaming, reconnection).