champion-identifier
Analyze LinkedIn profiles in target accounts to identify potential internal champions. Evaluates role, career path, mutual connections, interests, and suggests personalization approach. Use when you need to find who will champion your solution internally.
What this skill does
# Champion Identifier Find the internal champion most likely to advocate for the solution at a target account, using structured LinkedIn and account analysis. ## Contents - references/scoring-framework.md - champion profile, six scoring dimensions, total-score bands, warning signs - references/output-template.md - the full Markdown report structure to produce - references/outreach-templates.md - warm-intro, forwardable, direct, and opening-line messages - references/meeting-prep.md - discovery and qualification questions, red flags - references/multi-threading.md - sequence, coverage map, DMU table, org-chart format - references/champion-development-plan.md - five-phase plan with success metrics - references/playbook.md - tips, best practices, trigger phrases, worked example ## Workflow 1. Gather inputs: the company, the solution being sold, and any known contacts or mutual connections. Ask for whatever is missing. 2. Research the company and the department the solution touches: stage, recent news, likely pain points, decision-making style, and hiring signals. 3. Identify 5-10 candidate individuals on LinkedIn within the relevant department and leadership chain. 4. Score each candidate across the six dimensions (0-10 each, 0-60 total) per references/scoring-framework.md, citing concrete evidence for every score. 5. Rank candidates best to worst, and flag anyone who is a blocker or coach rather than a champion using the warning signs. 6. For the top candidates, choose an outreach path (warm intro vs. direct) and draft the message from references/outreach-templates.md, plus personalization hooks and meeting prep from references/meeting-prep.md. 7. Build the multi-threading plan and account map (DMU table, org chart) per references/multi-threading.md. 8. Assemble the full report following references/output-template.md, filling every field with researched specifics and no placeholders. 9. Recommend next steps using the phased plan in references/champion-development-plan.md.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.