Menu

Individual skill

crestapps-core-chat-interactions

Skill for Chat Interactions and the shared chat hubs and chat UI in CrestApps.Core 2.0. Covers AddChatInteractions with AddEntityCoreStores or AddYesSqlStores, ConfigureVisitorIdentity, ConfigureChatRateLimiting and ConfigureChatHubOptions, subclassing ChatInteractionHubBase and AIChatHubCore with AuthorizeAsync, AuthorizeProfileAsync and the other override hooks, the ChatInteraction model with chat, utility and conversation deployment names, IChatInteractionSettingsHandler, SaveSettings filter validation, send-time tool access checks through IAIToolAccessEvaluator, input-boundary delimiters, document upload endpoints, the IChatInteractionHubClient contract, the @crestapps/ai-chat-ui scripts with chat-markers, the stacked image carousel, assistant name and avatar, and upgrading from 1.x. Use it to stand up the fastest chat playground for a provider, build a chat page or widget, extend interaction settings, or troubleshoot chat hubs and chat UI.

src/CrestApps.AgentSkills/crestapps-core/crestapps-core-chat-interactions/SKILL.md

Read pinned source

Source commit d86d04f234b1b2bd8145368a2544490f9d557596

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 6, 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)
13
Repository last updated
Oct 21, 2026
License
MIT

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

# CrestApps.Core Chat Interactions

A **Chat Interaction** is an operator-controlled conversation that needs no AI Profile: the interaction itself stores its deployments, system message, sampling, tools, agents, MCP connections, data source and documents. It is the fastest way to validate a provider and deployment. **AI Chat sessions** (`AIChatSession`) are the profile-based equivalent used by end-user chat pages and widgets. Both ship in `CrestApps.Core.AI.Chat` and share the same chat UI scripts.

## Guidelines

- Start with Chat Interactions to validate a connection and deployment, then move reusable behavior into an AI Profile (`crestapps-core-ai-profiles`).
- Register stores for `ChatInteraction` and `IChatInteractionPromptStore` on the chat interactions builder.
- The framework does not ship a mapped hub. Subclass `ChatInteractionHubBase` (and `AIChatHubCore<TClient>` for sessions), map it, and call `ConfigureChatHubOptions<THub>()` for each concrete hub.
- The hubs' authorization hooks return `true` by default. Override them or put `[Authorize]` on the hub.
- Chat Interactions do not get the AI Profile prompt-security preamble or injection blocking (the operator controls the prompt), but they do get input-boundary delimiters and a per-user tool access check at send time.
- Use `crestapps-core-chat` for server-side completion code, `crestapps-core-signalr` for hub routes and authentication, and `crestapps-core-realtime-voice` for voice sessions.

## Registration