methos237

Dealer Portal AI Assistant — AI skill for Claude Code

AI community

RV dealer portal with an embedded Claude assistant: Next.js and ASP.NET Core portal, Python RAG and tool-using agent with an eval suite gating CI, MCP servers for the portal and Microsoft 365, Fabric.

How to install Dealer Portal AI Assistant

This entry records only its repository, not the path inside it, so there is no exact command to give. Open methos237/dealer-portal-ai-assistant and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Dealer Portal AI Assistant does

RV dealer portal with an embedded Claude assistant: Next.js and ASP.NET Core portal, Python RAG and tool-using agent with an eval suite gating CI, MCP servers for the portal and Microsoft 365, Fabric reporting, Azure via Bicep

Alternatives in AI

  • Artifacts Builder — Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web tech 97.5k ★
  • Pixel Agents — Compressed Reference — VS Code extension with embedded React webview: pixel art office where AI agents (Claude Code terminals) are an 6.5k ★
  • J Space Cognition Suite V3.7 — J-Space Cognition Suite V3.7 - AI cognitive-enhancement Skills based on Anthropic's J-space global workspace r 3k ★

README

Dealer Portal with an Embedded AI Assistant

A B2B dealer portal for an RV manufacturer, with a Claude-powered assistant built into the product rather than bolted on the side.

Dealers manage units, warranty claims, and parts orders in a Next.js front end backed by an ASP.NET Core API. The assistant answers questions from owner manuals and service bulletins with real citations (hybrid retrieval over pgvector), drafts claims and orders through tool calls that the user confirms before anything is written, and is held to an evaluation suite that fails CI when retrieval, faithfulness, tool accuracy, or injection resistance regress. The same portal tools are served over the Model Context Protocol, so Claude Desktop and Claude Code can use them too. A second MCP server connects SharePoint document libraries and a Microsoft Fabric semantic model. Everything deploys to Azure from Bicep.

Built in phases, each tracked as a GitHub issue. See the issues list for progress.

Components

Directory Stack Role
web/ Next.js, TypeScript, Auth.js, PWA Portal UI and assistant panel
api/ ASP.NET Core, EF Core, PostgreSQL Portal API and MCP endpoint (/mcp)
assistant/ Python, FastAPI, Anthropic SDK, pgvector Retrieval, agent loop, evaluation runner
mcp-m365/ TypeScript, MCP SDK, Microsoft Graph SharePoint and Fabric connector
functions/ Azure Functions (Python) Document ingestion from SharePoint
infra/ Bicep Azure resources

Architecture

Browser (Next.js, PWA)
  │ Entra ID sign-in (Auth.js)          user bearer token on every call
  ├──────────────► api  (ASP.NET Core)  /dealers /units /claims /parts-orders /documents
  │                 └── /mcp  (MCP streamable HTTP, same JWT, tools filtered by role)
  │                        ▲                           ▲
  └──────────────► assistant (FastAPI)                 │  Claude Desktop / Claude Code
        SSE stream   │  hybrid retrieval (pgvector