Menú
Company knowledge base with product portfolio, competitive positioning, case studies, and key metrics
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Fires on any operation that reads or writes deal, company, contact, call note, or task data. Provides: file schemas, write protocol (entity + index + cross-references + ops.log), account name resolution (fuzzy matching), read-time validation, duplicate detection rules. Output contract: every data write follows the standard protocol and produces a FILES UPDATED block.
Fires when a user asks about deal strategy, how to approach a stalled deal, or needs a business case. Produces: Five-Lens Prism analysis (stakeholder psychology, political capital, competitive dynamics, hidden leverage, temporal dynamics), Three Paths recommendation (velocity/diagnostic/protective), 5-Component POV model. Output contract: three distinct strategic options with evidence grading, never a single recommendation.
Fires on meeting prep, outreach, research, deck creation, and business case building. Provides: company overview, product portfolio, market position, differentiators, pricing context, case studies by vertical, key selling metrics, voice & language patterns, pain signal mapping, and prism insights. Output contract: company-specific context that makes outputs relevant to the prospect's actual situation. When a Platform Document exists (from /research), loads enriched voice, pain, and strategic intelligence.
Fires when a competitor is mentioned, a competitive situation arises, or the user asks how to beat/displace/win against a specific vendor. Produces: per-competitor displacement playbook with strengths, weaknesses, talk tracks, proof points, trap questions, and landmine responses. Triggers on: handle-competition, think-about-deal (competitive lens), battle analysis.
Fires on any written output — emails, outreach, LinkedIn posts, business cases, follow-ups. Provides: voice rules, email formatting, vocabulary substitutions, banned phrases, sign-off, and 7-point voice check. Output contract: all written content matches the user's calibrated tone and style.
Fires when a call transcript is pasted or the user says they finished a call. Produces: 6 structured outputs — MEDDPICC scoring with evidence, task extraction with owners and dates, coaching feedback on 5 dimensions, follow-up email in 3 tones, risk signals with mitigation actions, competitive intel. Output contract: every output is actionable, not just analytical.
| name | company-intel |
| description | Company knowledge base with product portfolio, competitive positioning, case studies, and key metrics |
| tier | 3 (regenerated) |
| auto-fire | /prep, /strategy, /outreach, /research, /deck, /pov |
| user-invocable | false |
Tier 3 — This entire file is regenerated during /setup Phase 2 (Company Intel) via web research on {{COMPANY}}.
Contains the AE's company overview, product portfolio, competitive positioning, pricing context, case studies by vertical, and key metrics. This is the company knowledge base that informs all outbound communication, deal strategy, and presentation content.
Company: {{COMPANY}} Website: {{COMPANY_URL}} Industry: [Populated during /setup via web research] Founded: [Populated during /setup] HQ: [Populated during /setup] Size: [Populated during /setup — employees, revenue if public]
Mission/positioning: [1-2 sentences from company website — populated during /setup]
Primary Product: {{PRIMARY_PRODUCT}} Additional Products: {{SECONDARY_PRODUCTS}} Description: {{PRODUCT_DESCRIPTION}}
Product overview (populated during /setup):
Top Competitors:
Our positioning vs. each competitor (populated during /setup via web research):
Competitor 1: {{TOP_COMPETITOR_1}}
Competitor 2: {{TOP_COMPETITOR_2}}
Competitor 3: {{TOP_COMPETITOR_3}}
Not detailed pricing — just enough context for strategic conversations.
Populated during /setup via web research on {{COMPANY}}'s published case studies.
Format per case study:
| Field | Content |
|---|---|
| Customer | [Company name or anonymized description] |
| Vertical | [Industry] |
| Size | [Enterprise/Mid-Market/SMB] |
| Challenge | [What they were facing] |
| Solution | [How they used our product] |
| Results | [Quantified outcomes — evidence-graded] |
| Quote | [Customer quote if available] |
Default (pre-/setup): No case studies available. Run /setup Phase 2 to populate from {{COMPANY}}'s published materials.
Usage rules:
Company-level metrics for use in proposals, POVs, and presentations.
Evidence grading for metrics:
Three angles for positioning (Commandment 9: Don't Pitch Features, Pitch Angles):
Financial Angle:
"[Prospect] is spending $[X] on [current approach]. Based on what we've seen with [similar company], switching to {{PRIMARY_PRODUCT}} could [reduce/save/generate] [Y] within [timeframe]."
Technical Angle:
"[Prospect]'s current stack includes [known tools]. {{PRIMARY_PRODUCT}} integrates with [relevant integrations] to [solve technical gap]. Companies like [reference] saw [technical outcome]."
Strategic Angle:
"[Prospect] is facing [market pressure/competitive threat/growth challenge]. Organizations in [their industry] are moving toward [trend]. {{PRIMARY_PRODUCT}} positions them to [strategic advantage]."