engagement-intake

Route unqualified technical engagement requests to named specialists via a rules-based matrix.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JinLee794/L.C.G --skill engagement-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: engagement-intake
Source: https://github.com/JinLee794/L.C.G/tree/main/.github/skills/engagement-intake
Command: npx skills add https://github.com/JinLee794/L.C.G --skill engagement-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Route unqualified technical engagement requests to the correct named specialists.

Core Features & Use Cases

  • Front-door SE intake to qualify engagements before routing to CSA, FDE, Engineering, ISD, or OCTO.
  • Resolve the deal team from MSX and verify customer pipeline and cost context, delivering a clear rationale and recommended next steps.
  • Supports single-account routing and portfolio-sweep workflows with a rule-based decision matrix, ensuring handoffs are timely and well-justified.

Quick Start

Provide the customer name and a concise technical engagement description to initiate the routing workflow.

Frequently Asked Questions about engagement-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route technical engagement requests to the correct specialists?

To route technical engagement requests, provide the customer name and a description. The system applies a rules-based routing matrix to resolve named specialists via CRM and deliver context-rich handoffs.

What is SE front-door qualification for engagement routing?

SE front-door qualification validates unqualified technical engagement requests before routing them to CSA, FDE, Engineering, ISD, or OCTO teams using a rules-based decision matrix.

Can I use this routing workflow for portfolio-sweep scenarios across multiple accounts?

Yes, the routing workflow supports both single-account routing and portfolio-sweep scenarios. It resolves MSX deal teams and verifies customer pipeline and cost context before generating handoffs.

How do I resolve deal teams and verify customer pipeline context during intake?

Resolve deal teams from MSX and verify customer pipeline context by performing name-resolution via CRM and optional SQL context loading to ensure handoffs are well-justified.

Does the engagement routing skill require any external dependencies or API connections?

The engagement routing skill requires no external dependencies. It operates standalone using scripts to execute the rules-based routing matrix and CRM name-resolution logic.