technical-poc-brieflisted

# Skill · technical-poc-brief ## What this does Traditional account research = "company size, funding, recent news." Useless to a technical buyer. This skill produces what an *engineer* at the prospect would actually use: their tech stack, their AI maturity, their public commit / launch history, their compliance posture, their existing-tool fatigue points. Output ready for a 15-minute first call. ## How to invoke ``` run technical-poc-brief on https://prospect.com ``` ## Steps Claude takes 1. **Read** `context/profile.md`, `context/icp-definition.md`, `context/positioning.md` for our identity. 2. **Profile the prospect across 6 axes**: - **Stack inference**: - GitHub org public repos (languages, dependencies, recent commits) - npm / pip / DockerHub publishings - Frontend tech (BuiltWith / Wappalyzer-style inference from headers) - LLM provider hints (job postings mentioning Anthropic / OpenAI / specific model names) - **LLM Maturity Stage estimate** (from `icp-definition.md` Section 1.1): - Stage 0-2 → Education-phase, deprioritize unless our wedge is education - Stage 3-4 → Primary target if our ICP matches - Stage 5 → Either premium customer or sophisticated competitor - **Data Residency / Deployment posture**: - Industry signals (FinTech / Healthcare / Defense → likely VPC+) - Public security page (SOC2, HIPAA, FedRAMP badges) - Geographic constraints (EU operations → GDPR data residency) - **Current